4 ms·
Arcade video game programmers of that age have told me warstories of themselves. BitBlits? That stuff is still handled by the BIOS / OS. The real arcade program
by dragontamer 13y ago
Arcade video game programmers of that age have told me warstories of themselves. BitBlits? That stuff is still handled by the BIOS / OS. The real arcade programmers would code at the level of scan-lines manually. (IIRC, Pacman was programmed at this level).
Every 30th of a second, the screen would have to be refreshed. Arcade programmers would perfectly tweak the loops of their assembly programs such that the screen refresh would happen at the right timing. As the CRT scanline would enter "blanks", they would use the borrowed time to process heavier elements of the game. (ie: AIs in Pacman). The heaviest processing would occur on a full-VSync, because you are given more time... as the CRT laser recalibrates from the bottom right corner to the top left corner.
Of course, other games would control the laser perfectly. Asteroids IIRC had extremely sharp graphics because the entire program was not written with "scanlines" as a concept, but instead manually drew every line on the screen by manipulating the CRT laser manually.
Good times... good times...
- joezydeco 13y agoActually Pac-Man was part of the second generation of videogame hardware where everything was "tile" based. The hardware generator was given a small RAM map of the playfield and then it would pull shapes from ROM and put them on-screen in a grid pattern. Less reliance on scanline timing and more logic could be done asychronously from the beam. The Nintendo NES would follow this design architecture later. The Pac-Man Dossier is a great reference for this kind of stuff: http://home.comcast.net/~jpittman2/pacman/pacmandossier.html http://home.comcast.net/~jpittman2/pacman/pacmandossier.html
- dragontamer 13y agoThanks for the correction. I must be thinking of games older than Pacman then... IIRC, Kangaroo used the old scanlines system, but its release date is after Pacman. I guess everyone was still trying to figure out how to do scanlines correctly at that time... so it must be different from arcade-game to arcade game.
- joezydeco 13y agoEvery manufacturer brewed their own hardware in-house. Remember this was cutting edge stuff in the early 80s. Things like RAM-based frame buffers were also insanely expensive, so you got tricks like this instead. Some went tile-based, others used custom ASICs or PLCCs to accelerate graphics.
- gorhill 13y agoExactly. This article brought back memories. Actually I realized, why not just put this stuff old time onto Github. There is no real use if only to remind people how different it was back then when you wanted to make a game... Some people will relate. Here https://github.com/gorhill/rayoid https://github.com/gorhill/rayoid So much time spent on counting CPU cycles... Atari ST's pixels layout was really tricky. There were better games out there, I will always remember Llamatron, my favortie (I wonder if the sources are available somewhere.)
- joezydeco 13y agoThe Atari "vector display" games actually had a second processor that did the work of driving the electron beam. The primary game processor would compute and send a list of coordinates to the vector generator, and it would do the hard work of moving the beam around. This lead to some neat hacks, like the guys that swapped the vector generator stuff for a laser projector: http://www.pangolin.com/images/SIGGRAPH_Tempest.jpg http://www.pangolin.com/images/SIGGRAPH_Tempest.jpg