Aus der ersten Antwort von ihm:
I mean in 320x200 true color, copying a picture on a dest screen takes 6 VBLs (yes, 6) with an algo like this
movem.l (a5)+,d0-a4
movem.l d0-a4,(a6)
So just to copy a static picture is 6 VBLs, but displaying a whole frame in Racer 2 includes :
- refresh of all the graphics
- get the player movements
- recompute all the sprites pos
- detect collisions (with road borders, with other drivers, with offroad sprites and between drivers)
- bonuses / race management
- sounds management, special effects (whosh sounds, ...)
Everything is done in 3 VBLs (so 3 VBLs better than just copying a picture on screen)
So, the greatest coding challenge is on the 68030 optims (always keep the code into the instr cache), reuse as much as possible the registers and trick a little where nobody can see it
The second most important "coding challenge" was the memory management to keep the game for 4 Megs machines like mine.
Keeping all the sprites, textures, sounds, in memory + the game itself was a real challenge.
I had to be very careful, a little change in the memory management or in a routine could break many circuits that were "short" in memory