14 ms·
Yes, Atari used these on: Battle Zone, Red Barron, Tempest, Star Wars, Empire Strikes Back, and I, Robot. That last one has a custom rasterizer chip and AFAICT
by phkahler 7y ago
Yes, Atari used these on: Battle Zone, Red Barron, Tempest, Star Wars, Empire Strikes Back, and I, Robot. That last one has a custom rasterizer chip and AFAICT was the only system to pair what was effectively a GPU with an 8-bit processor (MC 6809). The thing is, by the time the last 3 were produced it probably would have been technically better/simpler to use a 68K for the 3D transforms.
- kens 7y agoI took a look at the Star Wars arcade video game schematics, and I don't see any Am2901 chips (unless they obfuscated it really well). The schematic is interesting if you're into that sort of thing. They use two 6809 processors (one for sound effects). There's also a complex matrix processor built out of TTL chips. It does serial multiplication and division using latches and shift registers and adders and so forth. Then there's a bunch more circuitry to generate the analog signals to produce vectors on the screen. It's like a whole different world compared to how this would be implemented now. http://arcarc.xmission.com/PDF_Arcade_Atari_Kee/Star_Wars/Star_Wars_SP-225_2nd_Printing.pdf http://arcarc.xmission.com/PDF_Arcade_Atari_Kee/Star_Wars/St...
- phkahler 7y ago>> I don't see any Am2901 chips TFA said it was used on BattleZone. I assumed all 6 Atari games with a "Mathbox" used it but that may be a mistake on my part.
- MrBuddyCasino 7y agoI, Robot was seriously impressive for its time: https://www.youtube.com/watch?v=EHkwdvfXHJc https://www.youtube.com/watch?v=EHkwdvfXHJc It clearly inspired SNES's Star Fox.
- phkahler 7y ago>> I, Robot was seriously impressive for its time I was wondering why they didn't use that hardware for more 3D games. Looking at some of the emulator documentation, it seems the playfield was drawn by a function running on the Mathbox (co-processor) which would be really hard for most people to program. It was 4-5 years before they produced another 3D game with rasterized polygons using completely different hardware.
- tasty_freeze 7y agoI used to work with the guy who designed the hardware, Dave Sherman. Man, he had a lot of insider stories about the glory days of Atari! Anyway, there was no depth buffer. As I recall, the geometry was all pre-split in a way such that occlusion could be handled by sorting at the polygon level instead of the pixel level. I also seem to recall the native screen resolution was 256x240, but they used one extra bit per pixel that could be used to stretch a given pixel by 1/2 a pixel resolution, effectively giving 512x240. There were situations where the trick didn't work, but 98% of the time it worked well.
- phkahler 7y ago>> they used one extra bit per pixel that could be used to stretch a given pixel by 1/2 a pixel resolution, effectively giving 512x240 While reading about the reverse engineering by emulator authors. There was an extra bit in the frame buffer that no one seemed to find the use for. That should be reasonably easy to verify from schematics given a heads up. That may also explain why some of the YouTube videos look so bad around the edges compared to the real thing. They are probably recorded from MAME and dont account for that bit if that's really what it does. It also seems like that could only effect the right edges of polygons. There are 2 frame buffers and I believe one is used for scan out and the other is only written to, then they swap roles. So no z-buffer and no reading back pixels.
- MrBuddyCasino 7y agoHuh. Seems MAME is using just 265 pixel: https://github.com/mamedev/mame/blob/master/src/mame/drivers/irobot.cpp#L301 https://github.com/mamedev/mame/blob/master/src/mame/drivers...
- MrBuddyCasino 7y agoMade an issue on the MAME tracker: https://github.com/mamedev/mame/issues/6571 https://github.com/mamedev/mame/issues/6571
- 7y ago