Make the boundary visible.
One authority owns gameplay simulation. Clients interpolate state and build presentation. Simple components remain owned by their entities.
A C++23 engine from OmixLab
Small parts.
Living worlds.
A reusable foundation for games, immersive experiences, and the tools behind them. Built around clear ownership, explicit budgets, and room for different devices.
MODULAR C++23NATIVE BACKENDSAUTHORITATIVE WORLDS
A game engine.
Kept in its own lane.
The engine provides reusable systems. Games keep their rules, worlds, assets, and identity. The boundary is part of the design.
Choose the work that fits.
A shared rendering contract selects paths from authored intent, shader availability, and device capability. Quality choices remain deliberate.
Compose, then specialize.
Scene, scripting, physics, networking, rendering, and tools form separate libraries. Independent games link the pieces they need.
A map of the engine
Connected systems.
Distinct responsibilities.
Independent gameRules · world · content · product identity
AuthorityValidate input → game rules → physics → snapshots
Client presentationInterpolation → view → rendering, UI & sound
Reusable engine librariesScene & RTTR · Luau · assets · networking · physics · rendering · environment · audio · UI · XR
Native platform pathsVulkan · Metal · Direct3D 12 · WebGPU
The renderer is part of the world
Light. Water.
A sense of place.
Environment inputs, material choices, and geometry budgets meet in the final frame. These are real development captures from games using the engine.
Captured work in progress. These clips illustrate appearance and behavior, rather than comparative performance.
Go a layer deeper