Klang Games tackles SEED rendering and mobile memory limits
Unity’s SEED case study shows how player-built worlds expose different rendering and memory constraints across PC and mobile.
Unity details how Klang Games optimizes SEED, its early-access persistent MMO sandbox, for player-built worlds. The simulation runs on Klang’s servers, while a Unity client renders streamed state across PC and mobile.
According to Unity’s account, Klang reuses disaster-recovery server snapshots as performance tests once player societies grow large enough. For developers, that offers a way to test against actual player-created complexity rather than synthetic scenes alone.
Graphics engineer Artem Dyadichkin says SEED is primarily CPU-bottlenecked. Disabling animated LOD cross-fading while retaining manually set transitions restored instanced draw calls through GPU Resident Drawer and reduced render-thread pressure, he says.
Mobile presents a different constraint: senior game engineer Nikita Fetisov describes it as memory-bound and calls Mesh LOD crucial to rendering the world on those devices. Unity’s account also identifies triplicated textures, duplicated Addressables materials and oversized C# collections as memory problems.
- rendering
- mobile development
- performance optimization
- unity
