Here’s another new build:
Changes:
- Added a cockpit dashboard overlay by popular request.
- Asteroids now rotate!
- Moved the laser heat gauge to the dashboard, it’s now an energy meter that drops as you fire.
- Various updates to internals to save memory and fix renderer issues.
Please let me know in case you see any performance regressions, especially on hardware devices.
Would you be willing to check if it’s still crashing on Meowbit in this version? I’ve tried to reduce memory consumption.
There are some smallish reallocations after each level. I’m using an array with reusable triangle data (trapezoids) to reduce the per-frame garbage collector churn. That array grows a bit for each new level, but it only has ~150 elements and generally doesn’t need to reallocate during levels. I’ve switched the data representation for the underlying trapezoids from numbers to bytes in a buffer which reduced the data size from 48 bytes to 8 bytes.
The overall memory usage seems to be holding steady around 40kB, but I’m not sure if that’s representative of what it looks like in hardware.
Out of curiosity, is there a way to force a RAM limit, for example making a PyGamer pretend it only has 96 kB? That would make it easier to verify that games still work on low-memory devices.
That is very cool, I clearly need to read up on advanced TypeScript. I wasn’t aware that it’s possible to make no-overhead abstractions like this. Thank you again for the feedback!