Make perception part of play
Moving the lens reveals objects in the playfield; clicking or pressing Space sends a pulse. I built the rendering and interaction around this mechanic, then developed pacing and progression systems around it. The challenge is keeping the transformed view, the player’s input and the underlying game state in agreement.
Keep the lens and the game in agreement
Coordinate two views
Simulation state and the final WebGL lens output are separated but kept in the same coordinate system. Pointer input, scene content and interface overlays need to agree about what the player is acting on.
Bound the rendering work
The game limits how many pixels its visual effects render and reduces effect quality under sustained load. The scene and lens share that pixel budget, while text and input coordinates stay in their normal browser space. This bounds GPU work without moving the player’s targets when rendering quality changes.
Keep the growing system understandable
Rendering, game direction, spawning, progression and interface responsibilities live in focused modules. The core mechanic can be worked on without making every surrounding feature part of the render loop.
What this work demonstrates
Coordinating a distinctive visual interaction with state and performance constraints. This is relevant to custom visualisations and simulations that need more than a static chart or a standard form.

