Oculus Link Infinite Loading?
I've been using Quest + Link almost since release and it has been working just fine but now all of a sudden it has stopped working. It says on the oculus client that my Quest is active and ready to go. I put on the headset and enable oculus link. When I do that my screen goes black and then I'm stuck on an infinite loading screen. All I can see are the three moving dots and nothing else. I've tried reinstalling, repairing and restarting the oculus software but nothing has worked. Any help would be greatSolved229KViews15likes38CommentsQuest 3 controller pairs but not working at all
right quest 3 controller paired and tracking, but no inputs work. Controller moves around when viewed through headset. but if you pull the trigger, grip , thumbstick, a, b, or meta button. they don't work, or move like there even getting a signal when viewed through headset. Left hand is fine. Charged every thing up, left batteries out over night, paired controllers through app. tried factory reset but cant continue since it wants me to press the meta button on the right controller and it wont do itSolved135KViews4likes53CommentsFIXED: Quest 3 Locked After Setting Password Instead of PIN - NO Reset Needed
Problem: I accidentally set a password (e.g., "Meta Quest") using the hidden Android settings on my Meta Quest 3. After that, the headset asked for a PIN, not a password -- and there was no way to type letters. It looked like a factory reset was the only way out. Solution (No Factory Reset!): You can unlock your Quest and reset the passcode using the Meta Quest mobile app, even if the headset is stuck at the PIN screen. Step-by-Step: 1. Open the Meta Quest app on your phone (Android or iPhone). 2. Make sure the app is connected to your locked Quest headset. 3. Tap Menu > Devices > Headset Settings. 4. Scroll to the bottom and tap Passcode. 5. The app will prompt you to enter a PIN -- but it only shows a number pad, so you can't type your password here... yet. Workaround: 6. In another app on your phone (like Chrome, Notes, etc.), type your actual password -- for example: Meta Quest 7. Copy the password to your clipboard. 8. Go back to the Meta Quest app's PIN entry screen. 9. Paste your full password into the PIN textbox (yes, even though it shows a number pad). 10. Hit Enter -- your Quest will immediately unlock, and you can now set a proper 4-digit PIN. 100 percent working on Meta Quest 3. No factory reset needed. No debug mode. No PC. Just the Meta app plus this trick. Hope this helps others!1.8KViews1like5CommentsTrying to troubleshoot crash on start
I'm having trouble creating a consistently working player prefab. Using Oculus Integration v1.38 on Unity 2019.1.2f. I have the updated manifest.xml, I set to android platform, using ASTC, using GSL3, etc. I have an empty scene where the player prefab works and builds fine. I import that player prefab into an existing scene, apply the same settings, and it crashes! It takes a long time to rebuild and test small changes, but I've tried everything I could think of. The debug logs don't tell me anything about the crashes. I thought my scripts were calling OVR components too soon, but I fixed that. I get different kinds of crashes: App crashes immediately App crashes after a few frames App has stopped working message App never loads (3 dots) App runs but with black screen The player prefab builds correctly in an empty scene - so it can't be the project settings or the scripts on it. The existing scene builds correctly with Oculus' Avatar prefab - so it can't be the scene breaking it. If it's the scene conflicting with my scripts, I would get a debug error at least. I can't figure it out.1.1KViews0likes4CommentsOculusPlatformSettings ERROR (does not appear in Inspector tab on Unity and more...)
Hello! I'm attempting to set up the Quest with Unity, and next I'm supposed go Oculus (tab) > Platform > Edit Settings and then edit the settings on the OculusPlatformSettings (which should show up in the Inspector tab). However, 1. instead of Oculus > Platform > Edit Settings, it only shows Oculus > Tools > Use Required Project Settings/OVR Performance Lint Tool/....Oculus Platform Tool...etc. 2. When I search up the OculusPlatformSettings asset file and click on it, it says (in the inspector tab) "The associated script can not be loaded. Please fix any compile errors and assign a valid script." Apparently it shows the same for ONSPSettings and OvrAvatarSettings asset files. Keep in mind that I didn't touch any of these scripts at all. I've searched for solutions and tried out solutions for days, and nothing worked. Should I just use the Oculus Platorm Tool and add in my App ID and Token there (and then press Upload) instead of the OculusPlatformSettings (is it basically the same thing)? Help would be GREATLY appreciated.916Views1like0CommentsLogHMD: Error: Failed to load a depth texture frame description for the left eye.
My packaged Unreal build for the Quest 3 will not start and stays at the Unreal Editor splash screen. I dumped the log and saw the title of this post dozens and dozens of times in said log file: [2024.08.03-01.35.34:788][399]LogHMD: Error: Failed to load a depth texture frame description for the left eye. [2024.08.03-01.35.34:790][399]LogShaderLibrary: Warning: Spent 4.39 ms in a blocking wait for shader preload, NumRefs: 2, FramePreloadStarted: 2686, CurrentFrame: 2686 [2024.08.03-01.35.34:803][400]LogHMD: Error: Failed to load a depth texture frame description for the left eye. [2024.08.03-01.35.34:846][401]LogHMD: Error: Failed to load a depth texture frame description for the left eye. [2024.08.03-01.35.34:846][401]LogSVRLoadScreen: Display: BlockTick delta: 0.11 seconds. Current elapsed load screen time: 4.35 [2024.08.03-01.35.34:858][401]LogHMD: Error: Failed to load a depth texture frame description for the left eye. [2024.08.03-01.35.34:864][401]LogHMD: Error: Failed to load a depth texture frame description for the left eye. [2024.08.03-01.35.34:881][404]LogHMD: Error: Failed to load a depth texture frame description for the left eye. [2024.08.03-01.35.34:881][404]LogHMD: Error: Failed to load a depth texture frame description for the left eye. ...and on and on. The error seems to be linked to a custom node that uses the return ResolvedView.StereoPassIndex; command in order to adjust an effect per-eye. When I remove the node, the game starts properly. Everything runs fine in PIE, no troubles at all. I've never run into this error before on other projects, yet this particular one is plagued by it. What could the problem be?802Views1like1CommentADB Driver Not Downloading Correctly
Hello, I apologize if this is a duplicate. Basically, when I go to install the drivers on my computer, the folder comes through but the zip file does not so I am unable to extract and install. It just shows a standard folder titled oculus-go-adb-driver-2.0 but again the zip is not underneath as I have seen pictured in many tutorials. Any help here is greatly appreciated thank you. EDIT: Additional details. I am using Google Chrome (fully updated), Windows 10, Lenovo ThinkPad, and Windows Defender.640Views1like0CommentsOculus Link TroubleShooting
For this of you who have the Beta Link option available, I would like to discuss some troubleshooting parameters that might have your games crashing. If you have game bar from windows enabled, I would recommend disabling it while using the Link Function. It causes the Steam VR to fail quite a bit as when it tries to optimize it causes a sever malfunction. The same goes with Razer Cortex gaming optimization. For any of you owning Razer products It might have been installed with your Razer Synapse. This can also cause the program to malfunction while operating. And finally another item that may cause it to crash is Nvidia idea of recording gameplay. I would recommend turning off GeForce Expereince as the pop up can drop frames and latency connection with the Oculus Link and can result in crashing or connection failure.637Views0likes0CommentsOculus 2 will not boot, possible sensor issue? Log cat included
Hello everyone. I apologize for such the low level question but I am not sure where else to turn. Out of nowhere, my oculus 2 stopped booting and is stuck on the logo. I know the proximity sensor was on the way out bc I would have to turn it off in the MQDH app in order for the screen to come on. But now, it is just stuck on the boot logo. I have not factory reset, because I do not want to lose connectivity to SideQuest and MQDH, but I have sideloaded the latest Firmware 63.0.0.146.363.566760361 via adb in the bootloader, but still the same issue. Any other suggestions? Thanks to all PS I have a more verbose logcat available however I did not want to attach here due to size restrictions. https://drive.google.com/file/d/1MemNFUiJ3-taw-i0BSZ1MDDEyj_YCqUI/view?usp=sharing457Views0likes0Comments