Immersive Debugger spams error message
Hello Community, i try to use the Immersive Debugger in a Unity 6 project. But i do not get to manage that the following error message disappear: "In the render graph API, the output Render Texture must have a depth buffer. When you select a Render Texture in any camera's Output Texture property, the Depth Stencil Format property of the texture must be set to a value other than None." My guess is, that the error appears because of the debugger itself. The error will not be printed in the Unity Log if i start the application with the Simulator (but it will also appear in the Immersive Debugger Log). Has someone an idea whats wrong?
Quest 2's "Go LIVE To YouTube" Feature Not Working
So recently I've seen that in the Camera, there's now an option to go live on YouTube and see your chat while you stream. I've tried to use this feature, but every time I do it always says "something went wrong". (for the record I use OBS studio and stream the oculus.com/casting window. WHAT I'VE TRIED: - Going live on OBS then casting - Starting a scheduled live If someone could please tell me what I'm doing wrong I would appreciate any help.Potential Fixes and Workarounds for "Liquid or Debris in charging port" warning
Hi everyone, After struggling with the issue of the "liquid or debris found" error message when using the link cable for development and pushing builds, I thought I'd share a couple of workarounds that seem to work some of the time until Meta issues a fix for this. 1) Try a different port on your computer, maybe a different type of port. I had the error pop up nearly 100% of the time I plugged in my cable when I was using a USB type C 3.2 port on my computer. When I switched to using a USB 3.2 type A port with an adapter, I am experiencing the issue much less. I am yet to use this for an extended period of time but I'll provide an update on how frequently the error pops up later. 2) Use ADB over Wifi. If you can get your headset connected at least once, it may be worth the time to get the Meta Quest Developer Hub and try using ADB over Wifi. I believe you have to connect the headset over cable once before you can use this feature but it may save you some time down the line. Of course, this won't work with features like Unreal's VR Preview but you will still be able to package projects and push the APK over wifi as long as you are fine with waiting for the time it takes to package every time.
"Multiple Devices Can't Access This App At The Same Time" Error for my App with Latest QuestFirmware
In-house Quest 2 headsets started getting this error ("Multiple Devices Can't Access This App at the Same Time") as soon as they got the new firmware today, whenever more than one person (logged into the same developer account on multiple Quests) launched the application at the same time. This hasn't been an issue for us in the past. I assume there's some permission flag we need to set to allow this, but I'm struggling to find it. Does anyone have any guidance? Thanks! -Eric
