Real-time versus offline rendering
Offline renderers such as V-Ray, Corona or Arnold compute each frame individually at high accuracy. Output quality is very high, but a frame can take minutes or hours, and any change means re-rendering.
Real-time rendering produces dozens of frames per second. Before UE5 that largely meant trading away quality; Lumen and Nanite closed much of that gap.
For architecture the real gain is interaction rather than speed: in a real-time scene you can walk a client through, change the time of day, and switch a material instantly. Offline rendering cannot, because every change is a new render.
Lumen: dynamic global illumination
Lumen computes light bouncing off surfaces and illuminating the space indirectly, in real time. That matters for architecture because most of the perception of an interior comes from indirect light.
The practical result: changing the sun position recomputes the whole interior lighting accordingly. You can show the difference between morning and evening light without preparing two separate baked scenes.
In a sales context this answers one of the most frequently asked buyer questions directly: “how much light does this unit get?”
Nanite: high-detail geometry
Nanite allows very high-polygon models into a scene without the usual performance cost. Traditionally, simplifying models and preparing levels of detail was a significant work item.
For architectural projects this means CAD and BIM models can be brought across with less simplification. Façade detail, balustrades, joinery profiles and landscape elements can keep their detail in the scene.
There is still a preparation stage: BIM models carry data irrelevant to visualisation — internal service detail, layer metadata — which has to be stripped out.
Hardware and delivery format
Real-time quality depends on hardware, and that directly shapes the delivery decision.
- Sales office installation: highest quality, fixed hardware
- Laptop: representative use in the field, medium-to-high quality
- Browser version: widest reach, optimised quality
- Cloud streaming: high quality plus wide reach, with server cost
How MPANDO uses it
MPANDO uses Unreal Engine 5 in MTWIN. The reason for the choice is that it makes photoreal quality interactive while also binding to external data.
In MTWIN, UE5 is the visual layer only; unit data, pricing and state are supplied by MPANDO Sales OS. The commercial value of the engine choice comes precisely from those two layers combining.