Quest Pro Help

[Matt18C]

Just picked up a new Quest Pro and 30% of the lower screen is a brighter contrast and see a lot of pixilation going on. Is this a hardware problem or software and is there a fix or do I need to return this?

[Qcumber]

Is that when you are using it standalone or connected to your pc? If the former then that sounds like a problem with your headset. Try restarting and updating to the latest software. 

[jcenzano]

Just picked up a new Quest Pro and 30% of the lower screen is a brighter contrast and see a lot of pixilation going on. Is this a hardware problem or software and is there a fix or do I need to return this?

Are you using Air Link and Oculus Debug Tool?

It looks like it can be some issue with the video compression/bitrate.

Try lowering the resolution or the encoding bitrate.

Are you experiencing also broken/distorted audio?

Sent from my SM-A528B using Tapatalk

[slughead]

If you've been messing with the settings in the Oculus Debug Tool, don't. The default works just fine. FYI, it's the link slicing. Disable it.

If you haven't messed with the settings, I expect your headset is fubar.

[Ahogephilia]

Oculus link is horrible.

It's not stable, it's not performance friendly, it's not functional, and the UI is more more more horrible.

 

Use Steamlink or VDXR.
 

[Qcumber]

1 hour ago, Ahogephilia said:

Oculus link is horrible.

There are a lot of people who would disagree with this. To qualify, air link is not great but cable link is very good. VD is a close second. Steamlink I found to be very laggy compared to the other two. 

[slughead]

I’ve used Oculus Link, Oculus Air Link, VD and SteamVR.

There’s nothing wrong with Oculus Link. It’s the only one I use once I had tried all the others.

Edited April 12, 2024 by slughead

[Dogmanbird]

Till now, Oculus link has given me the best results too on q pro and q3

however, my q3 headset finally updated to v64 yesterday/today and I've lost a small amount of fps via link, plus my link cables no longer reliably connect as USB 3 and I now need to flip the usb connectors on all my link cables to connect as USB 3 (very strange).

edit- v64 appears be affecting our business headsets in the same way. I think they've tweaked the power settings again. i have a spare PC still on v63 pc app which has the same symptoms as above with the v64 headsets, so might be the headset software causing it 

edit edit - attempting to sideload v63 (which didn't work) seems to have triggered a later v64 update and I've regained the fps. Unfortunately the USB-C cables still need to be inserted in reverse (several cables tested which worked as usb 3 prior to v64 update) for the connection to be seen as USB 3.

Edited April 17, 2024 by Dogmanbird

[Qcumber]

I am suddenly having problems using QP and quest link. About 80% of the time when I take the headset off it crashes. Black screen with egg timer. I know the easy answer is don't take the headset off but this is not always an option. I have tried putting tape between the eye pieces but if I do this the headset does not activate. Does anyone have any advice?

[slughead]

12 minutes ago, Qcumber said:

I am suddenly having problems using QP and quest link. About 80% of the time when I take the headset off it crashes. Black screen with egg timer. I know the easy answer is don't take the headset off but this is not always an option. I have tried putting tape between the eye pieces but if I do this the headset does not activate. Does anyone have any advice?

All of a sudden? Hmm. Anyway, known bug with DCS although ED haven't acknowledged it. mbuuchia put a workaround into his quad view foveated rendering OpenXR layer tool. ED could fix it from looking at that. It's only a line or two of code.

If you install QVFR, you don't have to enable it for it to solve this problem. Add the following to the end of the settings.cfg file in your C:\Users\<username>AppData\Local\Quad-Views-Foveated folder to disable quad views but still retain the fix. You can then remove the tape.

[app:DCS World]
unadvertise=1

 

mbucchia/Quad-Views-Foveated: An OpenXR API layer to emulate quad views and foveated rendering support on many headsets. (github.com)

Edited May 2, 2024 by slughead

[Qcumber]

33 minutes ago, slughead said:

All of a sudden? Hmm

Sudden problem. Well. Sort of. It was an occasional problem. Now it's a pain in the arse. It's happening way to much. VD works fine but the link cable is more stable than VD WiFi. 

[slughead]

Remember that Mbucchia wrote the VXDR layer for VD. I expect he has put his fix in that, too.

[Qcumber]

Just now, slughead said:

Remember that Mbucchia wrote the VXDR layer for VD. I expect he has put his fix in that, too.

Good point. I like using VD. I just wish I could get a bit more stability. Even with optimised WiFi setup it's just not quite as stable as link-cable. With my Pico 4 I could use ethernet-usb for a stable 400 Mbps but it does not seem to be an option for QP. 

[slughead]

I'm suffering from this, too. We should capture some logs and start a new thread in the VR bugs section.

[Qcumber]

26 minutes ago, slughead said:

I'm suffering from this, too. We should capture some logs and start a new thread in the VR bugs section.

It seems to have started after the latest DCS update. I wondered if it was somehow related to the meta update to v63/64/65 but that's just guesswork. I'll try to get some logs over the weekend. 

[Bazz_Mulder]

Mbucchia VXDR layer is resolving this issue. You can take off QP and it will still show the feed.

[slughead]

1 minute ago, Bazz_Mulder said:

Mbucchia VXDR layer is resolving this issue. You can take off QP and it will still show the feed.

That’s for VD, not oculus link.

[Bazz_Mulder]

15 minutes ago, slughead said:

That’s for VD, not oculus link.

No, its for link. I'm speaking about that VDXR runtime he released as fix for meta/dcs v63 problem. I was using it for some time without VD

[slughead]

1 minute ago, Bazz_Mulder said:

No, its for link. I'm speaking about that VDXR runtime he released as fix for meta/dcs v63 problem. I was using it for some time without VD

VxDR runtime is for VD, not Oculus Link.

[Bazz_Mulder]

1 hour ago, slughead said:

VxDR runtime is for VD, not Oculus Link.

Instead of helping others, you always need to be a smart ass, don't you
 

Here it is, VDXR for Oculus Link: 

 

Edited May 3, 2024 by Bazz_Mulder

[slughead]

1 minute ago, Bazz_Mulder said:

Instead of helping others, you always need to be a smart ass, don't you
 

Here it is, VDXR for Oculus Link: 

 

 

It’s not about being a smart arse. If you added more information to your post in the first place there wouldn’t be such confusion.

What’s more it’s totally useless for me as it doesn’t support hand or eye tracking.

[slughead]

22 hours ago, Qcumber said:

It seems to have started after the latest DCS update. I wondered if it was somehow related to the meta update to v63/64/65 but that's just guesswork. I'll try to get some logs over the weekend. 

Are you using the OpenXR Toolkit with Turbo Mode On? I've heard that may be the causing the crash when removing the headset. If so, try turning it off.

[Qcumber]

17 minutes ago, slughead said:

Are you using the OpenXR Toolkit with Turbo Mode On? I've heard that may be the causing the crash when removing the headset. If so, try turning it off.

Yes. Just read about that and have not tested yet. However, I have been using turbo all the time. I'll test it over the weekend. 

[slughead]

I'll let you know how I get on. I've been chasing crashes, so turning stuff off, testing, back on etc. It takes a lot of time.

[Lange_666]

13 hours ago, slughead said:

Are you using the OpenXR Toolkit with Turbo Mode On? I've heard that may be the causing the crash when removing the headset. If so, try turning it off.

I have crashes with Rift-S and running MT with Turbo Mode On when taking headset off (ST is fine). Turbo Mode set to OFF solves the problem.
Bug has been around for quite a while, nothing to do with latest updates (either DCS or Oculus).