VR Seems Strange

[Lowlyslows]

Hey all!

First, I am not a computer wiz by any means. I can build one but all the magic that happens inside is greek to me. Also, sorry for double spacing, I can't figure out how to go single space.

My Setup:

CPU: AMD Ryzen 7 3700X 8-Core 3.60 GHz

RAM: 32.0 GB of Dominator

GPU: EVGA RTX 3080Ti

Mother Board: ASROCK X570 Taichi

Power Supply: 750 Watt

VR Headset: Oculus Quest 2 with Oculus Link Cable

 

Issue, it seems like my GPU is being under utilized. My FPS drops to the 20s and both my CPU and GPU are low with regards to percentages. Wouldn't my GPU start to ramp up to keep up with the FPS demand? See picture. 

 

Edited January 1, 2022 by Lowlyslows

[Lange_666]

18 hours ago, Lowlyslows said:

Also, sorry for double spacing, I can't figure out how to go single space.

Shift-Enter

[edmuss]

CPU usage will be low because DCS is largely single threaded, essentially the more cores you have, the less usage you'll see until the multicore engine upgrades are rolled out in the future.

What settings are you running at in DCS?

Set the headset resolution to 100% and PD1.0 in DCS, set the VR preset to get a baseline and see what it's doing. Don't know what performance tools the quest has for displaying frametimes in the headset but it's incredibly useful to be able to do so.

[ishamppl]

@edmuss Thanks for that insight as I'm having similar issues. Question: Where do I find the option to set the headset resolution to 100%? I've seen that suggested before I can never find that setting. Thanks! 

[edmuss]

I don't know on the quest unless you're driving it through steamvr (which I believe is much slower than natively through the Oculus app) in which case you say the render resolution in the steamvr settings menu.

Thinking back to when I ran my Oculus dk2, the Oculus tray tool had a supersampling option, set it to 1 and you're at 100%, set it at 2 and you're at 200% etc.

Edit: @Lowlyslowslooking back at your screenshot, the fps is recording as 20 but your render time is 10.2ms which is 98fps (1000 / 10.2) and your core clock and memory speeds seem in the right ballpark. I think the fps shown is a red herring.

Press right ctrl + pause on the keyboard whilst in flight and it should give you the current fps in the top left corner of the view.

Assuming my understanding of how the quest works is correct....

If you're below 90fps then it should step down to 45fps as asw (motion smoothing) switches on to synthetically interpolate frames to keep the image smooth. Whilst asw is engaged it should stay at 45fps, if you're above the 90fps refresh rate then it should stay at 90fps even though the frametimes can be lower.

Edited January 2, 2022 by edmuss

[Lensman]

2 hours ago, ishamppl said:

@edmuss Thanks for that insight as I'm having similar issues. Question: Where do I find the option to set the headset resolution to 100%? I've seen that suggested before I can never find that setting. Thanks! 

You go to the Oculus PC app. Select devices. Assuming your Quest is connected to the PC there will be a ticked green circle. Click the arrow and scroll the resulting window down to 'graphics preferences'. Here you can set refresh rate and rendered resolution. To get 1:1 pixel (maximum quality) rendering on the Quest you need to move the slider far right. This will render the image at native resolution in the centre of the display panel.

[Skopro_PL]

https://www.gamersbynight.com/dcs-settings-vr/

Edited January 3, 2022 by Skopro_PL

[Lowlyslows]

On 1/2/2022 at 8:09 AM, edmuss said:

CPU usage will be low because DCS is largely single threaded, essentially the more cores you have, the less usage you'll see until the multicore engine upgrades are rolled out in the future.

What settings are you running at in DCS?

Set the headset resolution to 100% and PD1.0 in DCS, set the VR preset to get a baseline and see what it's doing. Don't know what performance tools the quest has for displaying frametimes in the headset but it's incredibly useful to be able to do so.

Hey Edmuss,

Attached are my DCS, Oculus Graphics Settings, and Oculus Debug Tool settings.

[RED]

You are CPU limited. 8 cores-> DCS uses one thread ->1/8 ~13%.

Make sure there is nothing else in the background running. RGB software, anti malware, bloatware etc.

Did you overclock your CPU? If you applied a simple multiplier for all cores you likely slowed it down on Ryzen.

[edmuss]

Now that is odd, my CPU (6c12t) normally has about 30-40% usage and GPU at 95%+. Could you be bottlenecked by the Oculus link? Presuming you're on WiFi is your pc simply waiting to send the info to the headset?

Perhaps try reducing the pixel density and see if it allows more to go through. I think the pixel density of 1.4 would equate to a 200% render resolution which is going to be trying to transmit a hell of a lot of data over the WiFi. Think of it as trying to empty a swimming pool through a hose or emptying a bucket through a hose, which is going to be faster?

edit 1: ah just saw you're on the link cable, perhaps there's a maximum recommended throughout or settings that can be changed to improve the throughput.

edit 2: a quick bit of googling, see the response by nalex66 at the end of page 1 of this thread, mentions performance loss when using a bitrate of 500. Perhaps try reducing it and see if that helps?

https://forums.oculusvr.com/t5/Oculus-Quest-2-and-Quest/Question-about-Oculus-Link-bandwidth/td-p/861094

Edited January 3, 2022 by edmuss