Unreal Engine 5.8, Meta Quest (mobile renderer). Updated November 2026. Written by the Algosyntax team.
Quick answer: Quest projects usually run with Mobile HDR off (r.MobileHDR=False). In that mode Unreal has no exposure at all: it’s fixed at 1.0, and every exposure setting in your Post Process Volume is ignored. A scene lit with real-world values, such as a 100,000 lux sun, goes almost straight to the screen and clips to white. Either light the scene with small values made for an exposure of 1.0, or turn Mobile HDR on and pay for the extra full-screen pass.
The symptom
Our outdoor level looked right on PC. With the Quest renderer it was almost entirely white. Changing Min and Max EV, Exposure Compensation or Manual exposure in the Post Process Volume did nothing.
You don’t need to package to see this. Switch the editor to the Android Vulkan preview, as described in Preview what Quest will show in the editor.
Why it happens
On PC, Unreal’s exposure divides the scene’s brightness down to a displayable range. That’s what lets you use physical light units: a midday sun of about 100,000 lux, a lamp of a few hundred candela.
With r.MobileHDR=False, the mobile renderer skips tonemapping and eye adaptation entirely. The engine then uses an exposure of 1.0, and nothing in a Post Process Volume can change it. A light value that the desktop renderer would divide by about 20,000 now reaches the screen unchanged.
The sky light makes it worse. If it captures the sky once at the start, it stores that over-bright sky and keeps the ground white, even after you fix the sun.
How we confirmed it
Exposure theories cost us two wrong fixes. What worked was removing things one at a time:
- A plain template level looked fine, so the renderer itself was OK.
- Hiding the sun fixed the characters and UI, but the ground stayed white.
- Hiding the fog changed nothing.
- Setting the sun to 3 lux and recapturing the sky light gave a correct image.
Fix 1: light the mobile scene for an exposure of 1.0
If the scene’s lighting doesn’t change, lower the directional light and sky intensities until the image looks right with the preview on, then recapture the sky light. Values end up in single digits, not thousands.
If you have a day and night cycle, a single scale factor won’t work for both, because the PC renderer uses a different exposure at noon and at night. We did it in code: on the mobile renderer with Mobile HDR off, the sun’s intensity is multiplied every frame by the exposure the PC renderer would have used:
MobileIntensity = PhysicalIntensity / (1.2 * 2^EV100)
EV100 is the scene exposure for that time of day, from a curve (for us about 14 at noon, 10.6 at sunrise, -2.3 at night). At noon that turns 120,000 lux into about 6 lux, or 3 lux with 1 EV of compensation. After a large change, the sky light has to be recaptured. We do it on the first frame and every 2 degrees of sun movement. This fixed our daytime scene. Night still needs work, because the sky’s own emissive glow isn’t scaled yet.
Fix 2: turn Mobile HDR on
With r.MobileHDR=True you get the tonemapper, bloom and eye adaptation back, and physical light units work like on PC. The cost is an extra full-screen pass on a standalone headset, where every millisecond counts. We didn’t take this route, so measure it on your headset before you decide.
The same cause on PC: black UI panels
Physical light values with a fixed, high exposure have the opposite effect on unlit content. Our world-space UMG panels were completely black next to a 120,000 lux sun, even with a solid green background. Widget pixels are values from 0 to 1, and the exposure made them about 30,000 times too dark.
Fix: duplicate the engine’s widget material (Widget3DPassThrough), multiply its emissive by the EyeAdaptationInverse material node, and use the copy as the widget component’s material. The panel then ignores exposure and shows its real colours. For the same reason, next to a physical sun a fill light needs thousands of candela before you see it.
FAQ
Why is Mobile HDR off in Quest projects? Unreal’s VR Template turns it off, because the extra full-screen pass costs GPU time on a standalone headset. Projects started from that template inherit the setting.
Will a Post Process Volume fix it? No. With Mobile HDR off, the mobile renderer ignores exposure settings completely.
Does this affect indoor scenes? Only if the lights use large physical values. Indoor scenes lit with modest intensities usually look fine.