With UNITY 6 being released last month, we've gone in and logged some critical bugs that are preventing smooth Quest development on the new engine. If you find any bugs or, especially, find solutions let us know and leave them here!
-----------------------------------------------------------------------------------------------
BUGS:
#1: Disabled HeadTracking on play leading to stuttering and extremely low refresh rate
Notes:
- When playing preview with Questlink, it appeared that head tracking wasn't working and as a result the scene was refreshing in the headset and in the preview game view at extremely slow rates. Unplayable bug.
SOLUTION: (Credit to LuffyYu )
- Uninstall OculusXR plugin and enable MetaXR within OpenXR plugin & enable "HandPoses" within MetaXR options.
Solution notes:
- Solution seems to have fixed refreshrate on start UNLESS hand tracking is enabled -- results in same drop in refresh rate.
- Minor stuttering still present so potentially refresh rate isn't running entirely optimally.
#2 No visible controllers on preview play (i.e. controller tracking isn't functioning in this environment atm)
Notes:
- When playing preview with Questlink, there are no visible controllers with no controller inputs registering (controllers are paired with full battery).
SOLUTION:
- No solution found yet.
#3 Enabling hand tracking results in lost head tracking and extremely low frame rate (see bug #1 solution notes)
Notes:
- When playing preview with Questlink, after enabling hand tracking -- hands appear and have full tracking functionality, but we lose 360 stereoscopic view and revert to extremely low frame rates in headset and in game preview.
SOLUTION:
- No solution found yet.
#4 Non-functional builds (APKs)
Notes:
- After building an APK to correct specs and sideloading to Quest 3, the APK cannot launch and when launched by the user. we're prompted with "CANNOT OPEN" "CONTINUOUSLY STARTING". Suggesting some kind of error with the apk build/compile process (maybe some discrepancy in the DLL/SO files? -- total speculation)
SOLUTION:
- No solution found yet.
-- We've been finding some serious instability in some key parts of the dev experience with Meta XR on Unity 6 (preview, interaction SDKs, tracking, building etc.) all of which suggest a mismatch in potentially some of the lower-level infrastructure in Meta's plugins & Unity's updated engine (NOTE: we haven't observed any console logged errors during any of our testing -- on the surface things seem to be running fine, but we just have some inconsistent behaviors in engine typical of a new upgrade). We'll keep looking but if anyone finds anything let us know!