Jump to content

Quest2 shows crazy stutter and flashing sky, unacceptable eye damage.


Recommended Posts

Posted (edited)

I still haven't figured out how to record quest 2's PC streaming video

But I found a similar phenomenon. Different game but similar problem. When I look into the sky I see those crazy flashing lighter parallelogram flashing.

 

 

I tried USB3 cable, I tried use Oculus debug tool like this, but none works.

nullimage.png

This happens only in quest2's screen, not on my the PC's monitor. Looks like oculus should take more responsiblity since it is their device cannot render a smooth sky. But now I don't know who to blame with 100% certainty. 

If it is oculus and meta, I need to go to their forum to f*** them for creating such problems that hard to describe.

Edited by dontcsink
Posted

Your weird rant is missing a lot of pertinent information, like how long you've had the Quest 2 and if you were having these issues before. Or if you had any recent updates or changes to your PC. 

I didn't even want to respond to your post because the tone is so cringey, but you should always start by looking at your own hardware and settings first when troubleshooting. But hey, I'm sure going to the Oculus forum to "f*** them" will work out well for you. 

  • Like 1

PC: ASUS TUF 4090oc - Ryzen 7950X3D - 32gb DDR5 6000 - Quest Pro

Sims: DCS, IL2, MSFS

Pilot Skill: Drunk guy from Independence Day

RIO Skill: Goose (post neck-break) 

Posted (edited)

This would normally happen when ASW is on - the motion vectoring for the image calculation is not working well with clear blue colors.

Happens also in DCS with deep blue sky and waters on Quest 2 / Pro - can confirm.

Only solution would be to disable ASW or use 45 fps fixed instead with Oculus Tray Tool. Maybe Meta will fix the ASW algorithm, maybe not. We will see. It has been a problem in some circumstances with Oculus Rift S since 2019 - so nothing new here.

Edited by Tepnox

Ryzen 7 5800X3D // 64 GB RAM // RTX 4090 // Quest Pro // Quest 3

Posted

Here are my latest setting  with my quest 2 +link cable.  Oculus software 90hz 1.3 4128x2096. Oculus debug setting in attached file. SP or MP I'm in the 45-60fps depending on the mission. Not sure if my signature is up to date ryzen 5800x3d 64GB ram radeon 6700xt ssd hard drives. I have a little shimmer on the horizon line but everything else is nice clear. Here's a couple of sceenshots in MP.  This is  openbeta and DCS multithreading .exe and forcevr/openXR shortcut.

Jnull

oculus.jpg

Screen_230323_214444.jpg

Screen_230323_214551.jpg

  • Like 1

Ryzen7 5800X3D. 64 gb ram, 6950XT 16gb,  Winwing Orion F18, MFG Crosswind Rudder, 42 inch lg tv, Quest PRO

USN  VF31 F14A  AE2 1985-1989 CV 59 NAS Oceana

IL ANG 183FW/170FS F16C Block 30 Big Mouth 1989-2006 Full time tech Retired E8

 

Posted
On 4/12/2023 at 3:34 AM, Tepnox said:

This would normally happen when ASW is on - the motion vectoring for the image calculation is not working well with clear blue colors.

Happens also in DCS with deep blue sky and waters on Quest 2 / Pro - can confirm.

Only solution would be to disable ASW or use 45 fps fixed instead with Oculus Tray Tool. Maybe Meta will fix the ASW algorithm, maybe not. We will see. It has been a problem in some circumstances with Oculus Rift S since 2019 - so nothing new here.

 

Hi Tepnox, thanks for the reply. I did more test and found that it is ASW that causes the problem. However it has two aspect

1. The ASW algoritm is indeed causing blue fragment of the screen to shatter

2.The oculus debug tool cannot really close the ASW, I have to use Ctrl+numpad1 to close it. (Confirmed solve)

 

I searched the ASW problem of oculus on google, and found that it is a legacy problem that haven't been completely solved.

Given how facebook performed during the metaverse bubble (and how Oculus did before the purchase), I think there won't be an offcial solution..

Posted
On 4/13/2023 at 2:56 AM, Tomcat388th said:

Here are my latest setting  with my quest 2 +link cable.  Oculus software 90hz 1.3 4128x2096. Oculus debug setting in attached file. SP or MP I'm in the 45-60fps depending on the mission. Not sure if my signature is up to date ryzen 5800x3d 64GB ram radeon 6700xt ssd hard drives. I have a little shimmer on the horizon line but everything else is nice clear. Here's a couple of sceenshots in MP.  This is  openbeta and DCS multithreading .exe and forcevr/openXR shortcut.

Jnull

oculus.jpg

Screen_230323_214444.jpg

Screen_230323_214551.jpg

Thanks for the advice.

I did some test and found that ASW is main reason making the render break.

Closing it with ctrl+numpad1 temporarily solves the problem.

I am a little conservative in terms of increasing graphics settings 

image.png

I didn't increase the Oculus software's resolution, I don't know if  that resolution is handled by its onboard qualcomm chips or using PC's graphic card.

For the pixel density I am still confused, I mean which pixel density has the final say. Oculus debug tool or DCS settings.

I currently use DCS settings and set it to 1.1

nullnull

Posted

I get confused on which pixel setting does what and in which program. My DCS pixel is 1.0.  I copied the debug tool settings from one of the oculus pro post in this forum.  I was just experimenting around and was surprised oh how well it worked. I believe in their post they had a 4090 card and could run the oculus software at 90hz and the slider maxed out. I started out with the slider maxed and just started working my way back down until I found the balance of fps and clarity in the jet. I done all my testing on the 4YA Syria server it seems to be the most demanding for my rig to keep up. 

Ryzen7 5800X3D. 64 gb ram, 6950XT 16gb,  Winwing Orion F18, MFG Crosswind Rudder, 42 inch lg tv, Quest PRO

USN  VF31 F14A  AE2 1985-1989 CV 59 NAS Oceana

IL ANG 183FW/170FS F16C Block 30 Big Mouth 1989-2006 Full time tech Retired E8

 

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...