cancel
Showing results for 
Search instead for 
Did you mean: 

Bug Reports for Meta's fork of Unreal Engine 5.4 (+ Requests)

iBrews
Explorer
 
**Problems with the current MetaXR fork of Unreal Engine that make it a nightmare to work with:**
*(none of these problems appear when using a non-forked version of Unreal Engine)*

- Logging for all platforms seems to be completely stripped out. Doesn't matter if we're making a development or shipping build, we get no logs and no crash reports which makes debugging a major challenge.
- Dynamic lights don't appear at all on standalone Quest. Not just shadows or something like that, the lights completely disable and don't produce any light. They look fine on PCVR and fine on Quest if we don't use the Meta fork of Unreal.
- Lighting channels are broken. Some lighting channels will flash light on and off and sometimes will disable all lights on that lighting channel.
- If a scene needs lighting to be rebaked it causes a crash until the lighting is rebaked.
- Also noting that using the latest Meta XR plugin (NOT the fork) a packaged project will show up standalone on Meta Quest Pro and Meta Quest 2 with working audio but a completely black screen. Changing from using the plugin to using the fork fixes this.
Screenshot 2025-01-06 at 11.51.18 PM.png
 
**Major Requests:**
- Feature parity with Unity-- Many SDKs like Meta's Interaction SDK are lagging far far behind Unity and plenty of features still don't exist at all, such as multi-modal input (which I guess might never come to Unreal??)
- ASW working with the Meta XR plugin instead of requiring the Meta fork of Unreal Engine.
- Unreal Engine shines with PCVR. Better general support for PCVR would be excellent, though I know that's not a Meta priority.
- Allow Quest devices to utilize OpenXR extensions (such as hand tracking) without requiring the MetaXR plugin or fork
- Don't break SteamVR. Out of the box right now, including the MetaXR plugin (or using the fork) makes it so non-Meta headsets crash a packaged PCVR build. To get around this we end up making different builds for SteamVR users, which is a pain.
0 REPLIES 0