know.2nth.ai tech game-engines
tech/game-engines · Sub-domain hub

Real-time 3D.
Now an agent surface.

Game engines are runtimes for interactive, real-time 3D — the technology behind games, but also virtual production, architectural visualisation, digital twins and simulation. This sub-hub covers the engines that matter: Unreal (the fidelity-and-scale leader), Unity (the broad, mobile-strong default) and Godot (the open-source challenger). It launches with Unreal — anchored on the shift that put it on this tree: 3D engines are becoming agent-driveable surfaces via the Model Context Protocol.

3
Engines mapped
3
Live leaves
MCP
The new angle
01 · Engines

The real-time-3D runtimes.

Each leaf follows the standard shape: what it is, how it works, what it's used for, pricing reality, decision guide, SA context, connections, resources. Unreal is the first — the others land as the band grows.

Real-time engines · 3 Live
02 · Why it's on the tree

Engines crossed into agent territory.

Real-time 3D used to sit apart from the rest of the stack. Three things pulled it onto this tree — and each connects to a branch that's already here.

Engines are agent surfaces now

Unreal 5.8's embedded MCP server means an AI agent can drive the editor — spawn actors, set lighting, build materials. The same agent-driveable-surface idea from the agents domain, reaching 3D. The supervisor-not-author pattern applies.

Digital twins join IoT & construction

A live 3D mirror of a building or factory, fed by sensor data, is a real-time engine on top of an openBIM model and an IoT feed. Game engines are where the built environment and operational data become visible and explorable.

Virtual production meets media

LED-volume film sets render their backgrounds live in Unreal. Real-time 3D is now part of the generative-media pipeline, sitting alongside the voice, image and video work in the media domain.

03 · Related branches

Where game engines connect

Real-time 3D is a crossroads. These are the branches it pulls on most.