MRUK not found despite it being created...?
I'm currently using Quest 3 v62 (now v63) and Unity 2022.3.10f1. Working on a random spawn mechanic in the MR environment where objects can spawn on the ceiling. The feature worked fine when I tested it on Unity Playtest, but once I built it on the standalone Q3 (or simply hooked it up with a quest link), the scene could no longer be implemented. The room setup does indicate that I have my tables and walls, but there's no ceiling. I presume the Spatial data didn't transfer properly (I did write a script to grant permission to Q3 for spatial data, and clicked the Permission Requests On Startup) I have no idea where it all went south. Any ideas?
Infinite Load Screen for App Testing
My other users are continuing to get an infinite load screen when they try to test the build using the Meta All in One SDK. I have downgraded and upgraded the SDK several times but still my users aren't able to enter into the app. However I am able to enter into the app. Please any assistance would be great. I am using Meta All In One 71 and Meta Avatars 31.0.
PROCESS_ERROR
every time i try to upload my game it gives me the • The VRAPI library is not supported for applications created after 06-19-2024. Please refer to this post for more details: https://developer.oculus.com/blog/oculus-all-in-on-openxr-deprecates-proprietary-apis/ error, and i need help on how to make it stop. please help asap
Oculus Audio SDK and Meta XR Audio SDK Geometry based acoustics
I have been using Oculus Spatializer Unity (v47.0) in Unity (2021.3.29f1) to create reverberation based on the geometry of the game environment. It seems that there are a number of inconsistencies and behaviors I cannot explain: 1) When a source changes from visible to non visible (i.e the direct sound becomes occluded) the direct sound remains. Toggling Spatialization enabled resets it to as expected, after a while though it returns to the direct component being included again. 2) A different attenuation curve when reflections are enabled compared to when they are disabled. The former begins as a 1 / r releationship but shows a sharp roll off after around 2.3m. The first point in particular means I cannot use the Oculus Spatializer for my project. Therefore, I had a look at using the Meta XR Audio SDK (v55.0) instead as it is newer and seems to be a replacement for the Oculus Spatializer. However, as far as I can find it does not include the same geometry based acoustic rendering. It only seems to include a shoebox room approximation (described here: https://developer.oculus.com/documentation/unity/meta-xr-audio-sdk-unity-room-acoustics/) and is unable to account for occlusion of the direct sound by the scene geometry. Am I missing something? Or are there any plans to add any sort of geometry based acoustics to the Meta XR Audio SDK in the future? Otherwise, are you able to suggest why this behavior may be happening in the Oculus Spatializer?
It wont let me join preview apps
I'm trying to join this beta through preview apps and I have pictures but what happens is I click the link, it says congratulations, but never appears on headset or in my preview apps, and customer support wasn't being very helpful despite the game devs saying they should be able to helpAPK upload works, but will not run smoothly in VR when tested
I am experiencing a problem with my APK upload from Unity. I upload the APK from Unity just fine, but when I open the game in my headset to test, all movement is delayed, on top of that it is laggy. You cannot move anywhere, my game uses the Gorilla Locomotion System. There are no errors in the Console. The file is only about 200 megabytes. My headset is a Meta Quest 2, so it should have enough processing power to run the file. My headset has run a game the size of a gigabyte before, so it should be fine. Thank You so Much for Your Time, I greatly appreciate it. -RomanEmpire
v69 breaks OpenXR cubemaps with compressed textures
Our application creates a XR cubemap layer and applies textures to it. The cubemap layer is the usual type XR_TYPE_COMPOSITION_LAYER_CUBE_KHR. The 6 textures are loaded from KTX files and use the GL_COMPRESSED_SRGB8_ETC2 format. Starting with v69, this method for creating the environment around the user stopped working and our UI elements just float inside a black empty space. This functionality broke on our published version of the application, so it was probably not caused by a bug on our end. Everything worked fine on v68 and it broke with v69, We have been investigating this issue for several days and it seems that the problem is specifically triggered by the combination of compressed textures and a cubemap layer. Some additional observations: Textures with format GL_COMPRESSED_SRGB8_ETC2 or GL_COMPRESSED_RGB8_ETC2 do not work. Using PNG files for the cubemap does work (GL_RGBA8). Disabling layers also works. Loading other textures with the same formats works (we do it for the controllers).OCULUS_PLATFORM__APK_PACKAGE_NAME_ALREADY_IN_USE
Hi, I am trying to deploy a Meta Quest App to the Meta Store. The first submission was rejected, so I am trying to submit a new one, but when I try, I get the following error: OCULUS_PLATFORM__APK_PACKAGE_NAME_ALREADY_IN_USE The funny part is when I try some other name, I get a new error saying that I am trying to use a new package name, and I must use the previous name. Meaning the previous name that is giving the error of package name already in use So maybe someone has had the same issue. I am totally blocked because of this, because I can not submit the new version of the app. Thank you
