Forum Discussion
Oculus fork still necessary?
Hi, I'm coming back to Quest development with Unreal, tinkering around again with my pet-project. When we started that a few years ago, 4.27 was the version one would use, and if you wanted to us...
Sorry I don't no much about the Linux situation.
When it comes to Meta vs Vanilla, it’d be nice if Meta XR weren’t needed, but there are features you only get through Meta’s OpenXR path: Passthrough (XR_FB_passthrough), Scene/Plane understanding (XR_FB_scene), Spatial Anchors with persistence/query/sharing (XR_FB_spatial_entity/_storage/_query), foveation controls (XR_FB_foveation), Application SpaceWarp, color space selection (XR_FB_color_space), display refresh control (XR_FB_display_refresh_rate), enhanced hand-tracking aim/mesh (XR_FB_hand_tracking_aim), and tracked keyboard (XR_FB_keyboard_tracking). Vanilla UE 5.5/OpenXR covers core VR; if you need those features, you’ll want Meta XR or your own extension bindings.
Also consider Meta Platform integrations (friends list, presence, achievements, matchmaking).
Lately the downside of Meta XR is that support seems to be lagging; the team appears more focused elsewhere. Hopefully the core plugins get an update now that Meta Connect is over -or with UE 5.7 in developments.
Personally, I’m leaning toward going all-vanilla for now. Things feel unstable, and I’m still in asset-creation/design, so there’s no rush to target Meta-specific features yet.