ALGOSYNTAX BLOG

Porting a Desktop Unreal Engine App to Meta Quest: What We Learned Building VR Musician

November 18, 2026

Unreal Engine 5.8, Meta Quest 3, OpenXR. Updated November 2026. Written by the Algosyntax team.

Short answer: the code ported easily. The time went into five other things:

  • Performance: desktop rendering features that cost double in stereo.
  • The mobile renderer: no post processing, no exposure, no strand hair, and some materials that don’t compile.
  • The Android toolchain: a Java version mismatch broke the build.
  • Meta’s store rules: orientation, signing and manifest settings that Unreal doesn’t set for you.
  • Hands instead of a mouse: sliders, scroll lists and ray aiming all needed changes.

Each one has its own step-by-step article, linked below.

Unreal Musician is our free Windows app that turns MIDI files into 3D piano performances. VR Musician puts you at that piano on Meta Quest 3: songs fall towards the keys, a MetaHuman pianist plays beside you, and you use the panels and keys with your bare hands. It’s built on the same plugins we sell, MIDI Engine for playback and the note highway, and AnyWeather for the outdoor sky. It’s also our entry to Meta’s VR Start Developer Competition 2026.

We built it in a few days. Most of that time went into the problems below, and most of them will hit any Unreal project heading to Quest.

1. Test without a headset, but know what that tells you

The Meta XR Simulator lets you run VR Preview with a mouse and keyboard, hands included. The catch: the editor only finds it if it’s enabled before the editor starts. It also renders with the desktop renderer, so it says nothing about how Quest looks.

→ Test your Quest VR game without a headset (with the Lumen and MetaHuman hair crash, and a scene capture bug that only happens in stereo)

2. Performance: VR punishes desktop defaults

We started at 18-24 fps. Unreal Insights showed the cost was in renderer features we didn’t need: ray tracing still updating for the MetaHuman, virtual shadow maps per eye, software VRS that the engine turns on for every Windows project, and a faint light redrawing a six-sided shadow every frame. Turning those off, and drawing 8 bars of notes instead of 64, took us to 68 fps.

→ VR performance in Unreal Engine 5: how we went from 20 to 68 fps

→ Moving hundreds of objects with instanced static meshes

3. See the Quest look before you cook

An Android cook takes a long time. The editor’s mobile preview shows the same result in seconds: our MetaHuman turned into a stretched monster (mobile uses LOD 3 by default), beards and eyelashes vanished, and the wet-ground decals failed to compile.

→ Preview what Quest will show in the Unreal editor

4. Why the outdoor scene turned white

This was the hardest one. With Mobile HDR off, Unreal applies no exposure, so a physically correct 120,000 lux sun turns the screen white, and no Post Process setting changes it. The same cause made our UI panels black on PC.

→ Quest build washed out white?

5. Hands are not a mouse

Our UMG panels worked with hand poke and pinch straight away, because the Widget Interaction Component simulates clicks. Then the slider wouldn’t respond, the lists couldn’t scroll, and the ray jumped off buttons as you pinched.

→ Hand-tracked VR menus in Unreal Engine

6. Packaging: the Android toolchain

Unreal 5.8 builds Android with Gradle 8.13, and recent Android Studio bundles Java 25, which Gradle can’t run on. The error only says Unsupported class file major version 69.

→ Set up Android packaging for Meta Quest in UE 5.8

7. Packaging: crashes the editor never showed

The packaged build closed two seconds after launch. A constructor created a material instance, and packaged games build level actors on a loading thread.

→ Works in the editor, crashes when packaged

8. Getting past Meta’s upload checks

Our first upload was rejected because Unreal writes sensorLandscape and Meta wants landscape. We also needed a release keystore, a cleaner manifest and one APK instead of an APK plus OBB.

→ Meta Quest upload rejected? Fix orientation, signing and manifest errors

What we’d do differently

  • Turn the mobile preview on from day one, and tune lights and materials under it.
  • Put every performance fix in config or Blueprint defaults, so a new level doesn’t bring the old costs back.
  • Start from a lean renderer setup: no Lumen, ray tracing, virtual shadow maps or volumetrics in a Quest project.
  • Set up signing and store settings before the first build, and keep keystores and passwords out of Git.

FAQ

Did you need the Meta XR plugin? No. Hand tracking, VR Preview and the Quest build all use Unreal’s built-in OpenXR plugins.

Can a MetaHuman run on Quest? With mobile LODs, card-based hair instead of strands and a modest scene, yes. Expect to remove strand-only grooms and lower the detail level.

Do your plugins work in VR? MIDI Engine and AnyWeather are both part of VR Musician’s Quest build. We made changes for the mobile renderer along the way; ask us if you plan a mobile or VR project and want to know where they stand.

Related articles

← All blog posts