I have not been able to set aside some time to see if the audio glitch is reproduced on that Pentium 3 laptop. One day I hope to get to your level of expertise. I have to embarrassingly admit that despite me studying CS, I would not know how to trace the game like you did to discover the cause of the memory problem. I am not entirely sure but I may have re-tested the game (and still had the problem) in 1998 when I got a better computer, this time with an AWE64 Value ISA card. It could have been maybe an old version of the shareware demo with the bug? Maybe there was something specifically wrong with my machine back in 1995? I do recall that I did have an ISA Sound Blaster 16 card. I wanted to record a video showing the issue so maybe we can try to trace what was causing the audio problem. I am not convinced that giving the value of "dma" is what caused the audio glitch. I have an old Pentium 3 laptop lying around that I have been meaning to try to use to simulate the audio issue. A source code port is above the binary but some ways into the code. A hybrid approach pushes it some ways into the game. An emulation puts that layer at the hardware. I view these techniques along a continuum where you're essentially changing the porting layer. Replaced all that with 3D models rendered at the same spot in space. We found that the game internally used polar coordinates and had a fair bit of code that converted those 2D and chose the right sized sprites. My favorite was Gyruss which is somewhat like Space Invaders of Galaxian but with a 3rd person view from behind the player's ship so you see enemies come toward you in pseudo-3D. For instance, some exhaust smoke on the cars in Frogger. Mostly it was applying higher-resolution tiles and sprites but some had particle effects added. I think we referred to it as "reskinning". Frogger, Gauntlet, Joust, Gyruss and a bunch of others. This hybrid approach was used for a series of arcade games on XArcade for the Xbox 360.
0 kommentar(er)
