Oculus 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=sharing445Views0likes0CommentsOculus 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.622Views0likes0CommentsOculusPlatformSettings 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.899Views1like0CommentsTrying 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.1KViews0likes4CommentsADB 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.605Views1like0Comments