3 ms·
I've been involved in some ports recently, from really old systems into modern ones(like, PS1 games into current/next gen) - it's basically 1) import the whole
by gambiting 6y ago
I've been involved in some ports recently, from really old systems into modern ones(like, PS1 games into current/next gen) - it's basically
1) import the whole thing into Visual Studio solution
2) Add the desired target platform
3) hit build
4) keep resolving compilation errors until the game builds.
5) keep resolving linking errors until the game links
6) try running the game until it starts on the target system and doesn't crash immediately.
7) congrats, now you have something that most likely runs without any video, sound or input
8) spend X amount of time re-writing the renderer for the target system, add input support, add sound. This step can take any amount of time
9) congrats, now you have a game that "runs". It probably runs like absolute garbage right now. Now spend time understanding how all subsystems work - how is the data loaded? If it was a PS1 game, it was probably optimized for loading from the disc - can we now change it to have a more straightforward loading sequence. Can we just load the whole thing into ram on startup and be done with it?
9) do as many tweaks and optimizations as the time and budget allow - make sure it renders in 4K, supports 3D audio, rumble for controllers etc etc etc etc.
Again, step 9 can take any amount of time, depends what your production allows.
We were lucky in that the original programmers who worked on these games 20+ years ago still work at the same company - so it was quite fun for them to revisit that old code. But yeah, don't expect people to remember the code they wrote 20 years ago, you end up ripping out entire sections still marked as "fixme before launch(date: 12/1998)".
As for porting between current platforms(like a game simultaneously launching on Xbox and Playstation) - it's usually built for both from the start. In the rare cases where a platform gets added later, it's basically the same process as above - add the target, try building and running until it does. People who have experience doing it can progress much faster than people who don't - same as everything.
- brazzy 6y agoFrom my (very limited) understanding of how really old systems often had very unique hardware features and games that were full of intricate hacks to use these to improve performance, it seems to me that steps 4 and 5 could already take "any amount of time".
- gambiting 6y agoWell, yes, but in most cases it was like "oh, it's using some exotic library(and hardware) to do physics? cut this whole segment out then". Then once you have something that builds you can figure out how to reproduce the functionality in some other way.
- gambiting 6y agoOh, one other thing - for instance, one game we worked on that was done for PS1 was made in C, but with a lot of maths methods written in hand-crafted assembly. Things like matrix operations, vector maths etc. None of that code can even build on x64, so it was just removed and replaced with STD calls when possible, or local platform equivalent. The only places which were giving us a headache were methods written in assembly that had no clear purpose(like "ProcessData" with no comment what the "process" part actually did). We had to sit down and actually try to understand what the assembly code did before rewriting it in C++.