Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Memory hasn't really been a problem, since the Playdate has 16 MB of RAM, which is more than enough. I render internally at 200x120 and upscale to 400x240, so the 16-bit Z-buffer only takes about 48 KB.

I'm not using a Quake-like span renderer either. I use a triangle rasterizer that processes horizontal scanlines. In the Playdate the real challenge isn't RAM capacity, but the CPU's tiny cache. Keeping memory accesses efficient and avoiding cache misses is key to the performance.

(+1)

Thanks for the correction on the memory side — 16 MB with a Z-buffer around 48 KB really does make RAM the wrong villain. Scanline triangles plus a cache-bound tight loop makes a lot more sense on a handheld. When the cache is the wall, have you been shrinking the working set (shorter strips, fewer live tris), or is it more about access order?

Reducing unnecessary work is always the key. Also, as a solo dev making an original game, it's really important to keep the renderer code easy to understand and to iterate. I'm sure I'm close to feature complete, but I may still make some changes, so being able to make changes easily is as important as the code being fast.

Once I'm close to release I can then focus on extreme optimizations, even if they make the code a bit more complex to follow.