Unreal Engine 5.8, Meta Quest. Updated November 2026. Written by the Algosyntax team.
Quick answer: switch the editor’s Preview Platform to Android Vulkan with the Android Generic XR device profile. The viewport, Play in Editor and VR Preview then use the mobile renderer with your Quest settings. You’ll see what the Quest build drops, such as post processing, strand hair and desktop-only materials, before you wait 30 minutes for a cook. In UE 5.8 the menu is in the viewport toolbar under the speedometer icon (Performance & Scalability) > Preview Platform.
Step 1: Turn on the Quest preview
- In the level viewport toolbar, click the speedometer icon (Performance & Scalability).
- Open Preview Platform and choose Android Vulkan > Android Generic XR. That’s the
Android_OpenXRdevice profile, which every Meta Quest device profile is based on. - Use the toggle button to the left of Play to switch the preview on and off.
The first switch compiles mobile shaders, so give it time. The viewport label then reads Preview Platform: Android Generic XR.
Make it the default for the whole team
The editor saves your choice per user. To make the preview the project default, add this to Config/DefaultEditorPerProjectUserSettings.ini:
[/Script/UnrealEd.EditorPerProjectUserSettings]
PreviewFeatureLevel=1
PreviewPlatformName=Android
PreviewShaderFormatName=SF_VULKAN_ES31_ANDROID
PreviewShaderPlatformName=VULKAN_ES3_1_ANDROID_Preview
PreviewDeviceProfileName=Android_OpenXR
bPreviewShaderPlatformActive=True
bPreviewFeatureLevelWasDefault=False
Keep bPreviewFeatureLevelWasDefault=False. With True, the editor throws the preview away at startup. A choice someone makes in the menu is saved to their own Saved/Config/WindowsEditor/EditorPerProjectUserSettings.ini and overrides this default.
Step 2: Check what changed
With the preview on, these are the differences we found, and every one also happens in the Quest build.
The MetaHuman turns into a stretched monster
Our MetaHuman pianist had a stretched neck and merged fingers. MetaHuman meshes ship with Min LOD > Mobile = 3, so on mobile they show only their lowest detail level. The Android cook strips the better levels, and the body’s LOD 3 has under 1,000 vertices.
Fix: lower Mobile Min LOD (we used 1 for the body and 2 for the face, about 16,000 vertices in total). Set it on the shared LOD settings assets too, not only on the meshes:
/Game/MetaHumans/Common/Body/IdentityTemplate/Body_LODSettings/Game/MetaHumans/Common/Face/Face_LODSettings
When the mesh loads, it copies Min LOD from its LOD settings asset, so a value set only on the mesh goes back to 3 the next time you open the editor. Our first fix looked done and came back after a restart. Always restart the editor to check, and repeat this after regenerating a MetaHuman.
Hair, beards and eyelashes disappear
The mobile renderer has no strand hair. Grooms that have card LODs still render on Quest. Strand-only grooms, such as stubble, short beards, eyelashes and peach fuzz, simply vanish. To keep them, generate hair cards in the Groom editor.
Some materials turn grey, or the cook warns they failed
Materials that read Scene Texture nodes such as WorldNormal, or desktop-only passes such as Substrate’s DBuffer pass, can’t compile for mobile. Our wet-ground decals did both and fell back to the default grey material. Skip such effects on mobile instead of shipping grey surfaces. To check a material, open it and use Window > Platform Stats with Android Vulkan selected.
“SkyAtmosphere needs a mesh with a material tagged as IsSky”
On mobile, a Sky Atmosphere draws only through a sky mesh whose material has Is Sky ticked. In an indoor level that never shows the sky, delete the Sky Atmosphere instead of adding a sky mesh.
No post processing
With r.MobileHDR=False, the usual Quest setting, there’s no tonemapper, bloom, exposure or post-process material. Outdoor scenes lit with physical units then turn white; see Quest build washed out white?. You also get MSAA instead of TAA, no screen-space reflections and no point light shadows. Tune lights and materials with the preview on.
Step 3: Don’t misread the first run
After switching the preview on, one of our levels dropped to 22 fps and looked slower than the other. It wasn’t. It was the first one to run, so it was compiling shaders and pipeline states while we measured. On a second run both levels were equal. Always measure a warmed-up second run.
A Quest build can stutter the same way on its first launch, especially with r.PSOPrecaching=0, the VR Template’s Android setting.
A mobile-only performance trap: one movable light
On the mobile renderer, a mesh’s shader depends on whether a movable local light touches it. When a moving mesh enters a movable point or rect light’s range, Unreal rebuilds that mesh’s cached draw commands. Our falling notes all passed through one large rect light, which cost several milliseconds of render thread per frame while they moved. Hiding that light helped a lot. The engine setting r.Mobile.Forward.LocalLightsSinglePermutation=1 is an alternative that keeps the light and adds GPU cost per pixel instead.
FAQ
Is the preview exactly what Quest shows? It uses the same renderer path and settings, so missing features and broken materials match. Frame rates on your PC don’t tell you Quest frame rates. For those, test on the headset.
Can I launch a standalone game with the mobile renderer? Yes: UnrealEditor.exe YourGame.uproject -game -featureleveles31 OVERRIDESP=VULKAN_ES3_1_ANDROID_Preview dp.Override=Android_OpenXR, with -vr for VR.