1
\$\begingroup\$

I am developing a Meta Quest 3 (v74 for my OS with SDKs version being the lates the time of writing - v72) application in Unity 6 41f1 (and 29f1), where I currently struggle to get the application working past the loading screen (the 3 dots) in on the apk, while in the editor it just works, hovewer I would like to access functions that are not available in the player and even then my target platform in the Meta Quest 3 standalone platform. While running adb logcat -s Unity the result I get this log additional lines:

W OpenXR : xrGetVulkanGraphicsDevice2KHR: Called twice. OpenXR : PostSessionStateChange:[pid: 18824] XR_SESSION_STATE_FOCUSED -> XR_SESSION_STATE_VISIBLE OpenXR : PostSessionStateChange:[pid: 18824] XR_SESSION_STATE_VISIBLE -> XR_SESSION_STATE_SYNCHRONIZED OpenXR : PostSessionStateChange:[pid: 18824] XR_SESSION_STATE_SYNCHRONIZED -> XR_SESSION_STATE_STOPPING

and the main error which was:

xrEndFrame frameTransaction failure detected, might due to compositor frame blocking, swapchains not marked as used-in-frame 2270

The number 2270 is arbitrary and you could insert any other number instead of this. I am asking if there is an extended documentation and what version of the Unity Editor to use, to work with the development of XR/AR applications with the latest possible feature set without any errors?

\$\endgroup\$

1 Answer 1

Reset to default
1
\$\begingroup\$

I just had and fixed the same 3-dots issue after upgrading from Unity 2021 -> 6000, however I wasn't receiving the same errors as you so my solution might not help.

My solution requires Meta SDK (either All-In-One, Core, or earlier versions have the same option).

Then in at the top under Meta > Tools > Remove AndroidManifest.xml followed by Tools > Create store-compatible AndroidManifest.xml. Build your APK again and install via MQDH or SideQuest.

enter image description here

I'm not sure what you mean by:

I would like to access functions that are not available in the player

I would suggest removing those "functions" until you get past this error.

You can also try to run Tools > Project Setup Tool which opens a panel and shows any potential issues.

\$\endgroup\$
1
  • \$\begingroup\$ As it turns out my issue was that I was using the new Input System instead of the old one. However even though Unity complains that I should use the new one, I just ignore the prompt and now my application runs well. \$\endgroup\$ Commented Jul 11 at 7:46

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.