Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Fix xr_v2 OpenXR Android
See original GitHub issueThe xr_v2 branch has a broken Android build. Notes on fixing.
The build appears to compile and link without error. It can be installed on a device but there appears to be no launch activity, so it it just hangs on the loading screen. The expected activity is com.unity3d.player.UnityPlayerActivity .
Issue Analytics
- State:
- Created 2 years ago
- Comments:16 (6 by maintainers)
Top Results From Across the Web
Fix xr_v2 OpenXR Android · Issue #222
The xr_v2 branch has a broken Android build. Notes on fixing. The build appears to compile and link without error.
Read more >VR devs, just how universal is OpenXR anyways?
Hi, a question for VR developers. If someone develops a VR game for android and OpenXR, does this mean the APK can be...
Read more >Unity OpenXR support for Android runtimes other than ...
I am trying to use Monado's android OpenXR runtime with installable broker on a regular device instead of Oculus. Please find the android...
Read more >Getting Started with OpenXR for Mobile
You will learn how to setup a project using the VIVE OpenXR Plugin to create immersive content that runs on Android devices such...
Read more >How To Build Hello_Xr sample with Android Version
Hi, I want to try how to write a VR APP with OpenXR SDK. I found Oculus had published OpenXR Mobile SDK: Actually,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@billyquith Do you feel this is in a good place to close out w.r.t compatibility on quest 2? I feel other android headsets deserve their own issues to track, but this should be fairly stable on quest now.
ExportFbx relies on the vendor name being present in App.cs, which was changed in 234624f794a3d1816ffb66ed2ed6b798b62d2e6e. This will only be caught in editor if the
FBX_SUPPORTEDFBXSDK_RUNTIMEdefines are enabled.