rusty_shackleford
Arcane
- Joined
- Jan 14, 2018
- Messages
- 50,754
linux port when
-
Welcome to rpgcodex.net, a site dedicated to discussing computer based role-playing games in a free and open fashion. We're less strict than other forums, but please refer to the rules.
"This message is awaiting moderator approval": All new users must pass through our moderation queue before they will be able to post normally. Until your account has "passed" your posts will only be visible to yourself (and moderators) until they are approved. Give us a week to get around to approving / deleting / ignoring your mundane opinion on crap before hassling us about it. Once you have passed the moderation period (think of it as a test), you will be able to post normally, just like all the other retards.
Probably not even necessary.
Older games tend to run vastly better under Wine/Proton than modern Windows anyway.
That said, I'd say it depends on how catastrophic the code is, e.g. if graphical code is mixed wildly with gameplay code, etc.
Good separation of layers makes porting much easier.
Crashes (especially in that labirynth), widescreen support, crappy default camera (and it resets very often), and probably more.
AdolfSatan
Arcane
- Joined
- Dec 27, 2017
- Messages
- 2,094
Deadman's fix should get rid of most camera-related crashes, like the ones in the sewers/labyrinth, but it'd be nice to fix as much as possible from the source code.
We could also update the fonts, get an open source serif to replace that cancerous papyrus.
No idea how the adaptation to widescreen it may work from a technical standpoint, but I can make some time to extend and adapt the UI where needed.
Oh, and of course, a 25Gb retexture pack.
We could also update the fonts, get an open source serif to replace that cancerous papyrus.
No idea how the adaptation to widescreen it may work from a technical standpoint, but I can make some time to extend and adapt the UI where needed.
Oh, and of course, a 25Gb retexture pack.
- Joined
- Oct 12, 2010
- Messages
- 1,871,884
Lord_Potato
Arcane
Rinslin Merwind
Erudite
Fucking incline, I hope one day I will be able to play this game without constant infuriating crashes.
Great news, game looks very interesting but it never worked stable enough for me. When I saw this thread i was certain that another pointless necro was to blame. A nice surprise.
Fowyr
Arcane
- Joined
- Mar 29, 2009
- Messages
- 7,671
Have you tried the wrapper?
Rinslin Merwind
Erudite
I think I tried it (it was long ago, I don't remember), yet game definitely fucking crashes on me if I move camera in "wrong way" in caves. Also, I think I have encountered some bugs, but I can't recall now what it was exactly.
Fowyr
Arcane
- Joined
- Mar 29, 2009
- Messages
- 7,671
Zoom camera and move it with the numpad.
Rinslin Merwind
Erudite
I remember trying different methods to move camera, yet haven't figure out reliable workaround. But thanks for suggestion anyway.
- Joined
- Oct 12, 2010
- Messages
- 1,871,884
The source code will be useful to have in general. It should be possible (with some work) to port the rendering system to something more modern which would allow higher resolutions and hopefully fix a lot of the instability.
The main issues I foresee:
1. Judging by the issues, the code is likely going to be poor quality spaghetti code.
2. It's likely not going to include any commercial/proprietary middleware they used which would mean these would all to be ported/replaced to get something that can be compiled.
3. Assuming the code can be compiled in the first place, actually fixing the issues is likely going to be a big piece of work in itself.
That said, we've probably got enough expertise around the codex to work something out assuming we get interested parties. I'll be happy to assist also, though my C skills are a little rusty (I'm assuming that's what the game will be written in).
The main issues I foresee:
1. Judging by the issues, the code is likely going to be poor quality spaghetti code.
2. It's likely not going to include any commercial/proprietary middleware they used which would mean these would all to be ported/replaced to get something that can be compiled.
3. Assuming the code can be compiled in the first place, actually fixing the issues is likely going to be a big piece of work in itself.
That said, we've probably got enough expertise around the codex to work something out assuming we get interested parties. I'll be happy to assist also, though my C skills are a little rusty (I'm assuming that's what the game will be written in).
It's a crime that you can only give one brofist to a post.
- Joined
- Oct 12, 2010
- Messages
- 1,871,884
If he delivers he should get a prestigious tag.
- Joined
- Sep 25, 2012
- Messages
- 30,318
I'm in.
Barbarians should not be as sceptic. Crom is clearly with the Codex on this one.
- Joined
- Sep 25, 2012
- Messages
- 30,318
No one tells Barbarians how to behave.
Let's see the source code first but the path will probably be (assuming the plausible way it's coded WIN MSVC DirectX) :
* Attempt to recompile it for Windows with legacy toolchains
* Modernize the build systems by porting to CMake
* Make everything compile with multiple modern compilers on Windows
* Update legacy dependencies that we want to keep
* Port it to Linux through WineLib
* Evaluate and replace legacy/unwanted dependencies (DirectX or whatever will be in our way for instance, simple SDL+OpenGL should be the first step)
* Ditch WineLib
* Volunteer QA should start now
* Clean the code, fix the bugs
* Improve whatever shiny people will like (the nice to have, pleasant to code, but the easy part)
Some people in a hurry will probably provide shortcuts for gamers' enjoyment but IMO this is the solid path with the best quality result.
* Attempt to recompile it for Windows with legacy toolchains
* Modernize the build systems by porting to CMake
* Make everything compile with multiple modern compilers on Windows
* Update legacy dependencies that we want to keep
* Port it to Linux through WineLib
* Evaluate and replace legacy/unwanted dependencies (DirectX or whatever will be in our way for instance, simple SDL+OpenGL should be the first step)
* Ditch WineLib
* Volunteer QA should start now
* Clean the code, fix the bugs
* Improve whatever shiny people will like (the nice to have, pleasant to code, but the easy part)
Some people in a hurry will probably provide shortcuts for gamers' enjoyment but IMO this is the solid path with the best quality result.
rusty_shackleford
Arcane
- Joined
- Jan 14, 2018
- Messages
- 50,754
where the code
Well, personally I hope for the weekend, but I dunno, I'm awaiting any response from Mat to my e-mail.
As an Amazon Associate, rpgcodex.net earns from qualifying purchases.