3 ms·
You're way too pessimistic about doing image recognition on NES tiles. NES games don't update the tileset very often during gameplay. They can't--the NES has no
by pcwalton 11y ago
You're way too pessimistic about doing image recognition on NES tiles. NES games don't update the tileset very often during gameplay. They can't--the NES has no framebuffer and a very underpowered CPU, so the VBLANK time is a mad dash to push all per-frame data to the GPU (PPU in NES-speak) by the time the video signal is going to begin. Most games barely slide under this window. Lots of games didn't even try to do dynamic tileset updates and stored tileset data in ROM.
Because of this, you can do a lot of graphics processing up front and cache it on a per-tile basis. The hit rates on that cache are going to be massive.
- khedoros 11y agoAgreed. The hardware itself does palette and tile lookups for each pixel, then shoves the data out the wire. Building an emulator that way is more literally how the hardware works, but it's slow. It's easier (and usually just as accurate) to cache the tiles for the current palette settings and blit them to the playfield as needed. There's no reason that the same wouldn't be true for 3D representations of those same sprites. Updating the sprites in CRAM is fairly rare (and impossible in any game that uses CROM).