Quest 3 passthrough black after developing with Unreal.
Hey, the normal passthrough function in the Quest 3 doesn't function anymore / is black after diving into Unreal development and setting everything up. The toggle in the menu is NOT greyed out. Passthrough works when playing First Encounters though. Anyone experienced the same thing? Thankful for any kind of help!
Set HDR enabled/disabled at runtime?
Passthrough still won't works (black screen) if HDR is enabled in the render pipeline asset settings, so I must build the project with HDR disabled. How can I activate HDR when the passthrough stage is done to get post processing effects on ? Actually I can successfully tick from script the HDR option, but it is not activating post processing effects at runtime. // This ticks the checkbox while running on editor, but no effects at runtime on the headset. var urpAsset = (UniversalRenderPipelineAsset)GraphicsSettings.renderPipelineAsset; urpAsset.supportsHDR = true;My Quest 2 was reset to factory settings and I can't use it because of the proximity sensor
My quest 2 had a boot loop and I tried a few things like factory reset and firmware update, and in the end I found out that it was due to the proximity sensor, so I removed the faulty proximity sensor from the quest 2 and it booted up normally But now it's stuck on the black screen because of the faulty proximity sensor and I can't set it up because it doesn't allow me to use it since I can't see anything I tried to deactivate the proximity sensor through the computer, but for me to deactivate it I need to activate the usb debug mode, but then another problem appears, I paired the quest 2 with my cell phone to activate debug mode and it does not allow me to activate it My account is already verified, I don't understand why it doesn't allow me to activate this option Honestly, I don't know what to do, I can't set it up through the quest because it has a black screen because of the sensor, and I can't even deactivate the sensor because I can't activate debug mode on my cell phone If anyone can help me I will be very grateful, because in my country Quest 2 is really expensive, and there is no authorized assistance from Meta, I contacted support but they asked me to send it to another country but even if they fix it my quest 2 in another country, when it is sent back it will be taxed at basically the price of a new onePlease skip Guardian check when Guardian is disabled on Quest 2
I appreciate the developer feature of disabling Guardian, which saves us time. Thank you. I'd like to report a serious bug in the latest Quest 2 firmware update that wastes developers' time. A simple 2 steps to reproduce it: 1) Settings > System > Developer > Disable Guardian. 2) Long press the power button > Restart Quest 2 will then get stuck in black after the Meta logo disappears, and the only way for a developer to get out of it is to factory reset the device. It appears that Quest 2 got stuck checking Guardian when Guardian was disabled. If so, please make the firmware skip the Guardian check if Guardian is disabled. This will save us lots of time, from developers to developers.
when I run appin quest, guardian wall paper appear and screen turn black
hi, i have package a project from ue 4 for quest. side load the project in quest . found the app in unknown source. but when i run the app, long time three dots appear like loading the app . after that the guardian wall appear and screen turn black.. last tow day i am trying to solve this .. but no luck.. very frustrating.. any help..Random black screen on quest
Hi First off, apologies if you see this question twice - I asked it once and the post disappeared immediately! We're experience a severe issue where, after a relatively small period of time (15 minutes to an hour) the screen in our app simply turn black and will never come back. The game is clearly still running (we can hear sfx in response to movement on controller, still use voip and verify the online connection is valid etc), however the screen is simply black. We've got some suspicious log cat output: 10-18 08:42:42.963 1037 1463 I ActivityManager: Process com.oculus.vrshell (pid 1809) has died 10-18 08:42:42.964 1037 1463 D ActivityManager: cleanUpApplicationRecord -- 1809 10-18 08:42:42.978 1037 1585 I WindowManager: WIN DEATH: Window{890a751 u0 SurfaceView - com.oculus.vrshell/com.oculus.vrshell.MainActivity} ... 10-18 08:42:43.099 1037 1583 I DisplayManagerService: Display device removed: DisplayDeviceInfo{"com.oculus.android_panel_app.AndroidPanelLayer-#main": uniqueId="virtual:com.oculus.systemux,10060,com.oculus.android_panel_app.AndroidPanelLayer-#main,0", 770 x 241, modeId 2, defaultModeId 2, supportedModes [{id=2, width=770, height=241, fps=60.0}], colorMode 0, supportedColorModes [0], HdrCapabilities null, density 160, 160.0 x 160.0 dpi, appVsyncOff 0, presDeadline 16666666, touch NONE, rotation 0, type VIRTUAL, state ON, owner com.oculus.systemux (uid 10060), FLAG_PRIVATE, FLAG_NEVER_BLANK, FLAG_OWN_CONTENT_ONLY} Specifically the 'WIN DEATH' and 'Display Device Removed' However nothing else to go on. As far as I can tell we aren't hitting memory issues or anything either - mem use stays relatively stable throughout. We're on unity 2018.4, Oculus SDK 1.29.1. Happy to upgrade if likely to fix things, but we're near ship so would rather not do so unless it's likely to help! Has anybody seen this / have a suggestion. Any help from devs or the Oculus team would be hugely appreciated Thanks Chris
