New i9-13900K & RTX 4090 PC and suffering stuttering on all settings so far?

[fab.13]

Hello,

Using occulus, you don't need WMR toolkit like described in previous post ( G2 headset )

You should try native occulus api first as suggested by dburne

( OpenXR tuning will be mandatory in a future when DCS will support that only one API... )
 

So See this thread to use native occulus api with DCS MT
Check DCS log ( first pages ) about which VR API is used when have launched DCS

 

[DirtyMike0330]

20 minutes ago, Glide said:

Whatever.  Try just the game settings then. Vis Range = Low, Terrain shadows off, AA off, AF off.

Yeah, buy a 4090 and high-end CPU and then drop your settings to low lol You are a genius. 

[DirtyMike0330]

OP, the goal here is that you need to figure out why 45 ASW is not working on your system, if you are indeed selecting it but your frames are staying unlocked and hitting the 70s. We have a similar system and the same VR headset, unlike some folks giving you insane advice. I have attached pictures of my settings so you can compare. In the picture of the Oculus Home app, you would click on the Quest Pro and you can slide the render scale to the right to 1.5 or 1.7 (I have mine maxed at 1.7)

With these settings, your ASW should be locked to 45 and you will have smooth gameplay in every scenario, including multiplayer. If, with these settings, your ASW is not locking you to 45, then something else is going on in your system. 

You do not need WMR, you do not need to drop your render resolution, you do not need anything extra. Also, I am running this on the multithreading executable. 

Edited April 14, 2023 by DirtyMike0330

[minimi66]

10 hours ago, DirtyMike0330 said:

OP, the goal here is that you need to figure out why 45 ASW is not working on your system, if you are indeed selecting it but your frames are staying unlocked and hitting the 70s. We have a similar system and the same VR headset, unlike some folks giving you insane advice. I have attached pictures of my settings so you can compare. In the picture of the Oculus Home app, you would click on the Quest Pro and you can slide the render scale to the right to 1.5 or 1.7 (I have mine maxed at 1.7)

With these settings, your ASW should be locked to 45 and you will have smooth gameplay in every scenario, including multiplayer. If, with these settings, your ASW is not locking you to 45, then something else is going on in your system. 

You do not need WMR, you do not need to drop your render resolution, you do not need anything extra. Also, I am running this on the multithreading executable. 

 

Ok, i'll give it a go and report back.  I've tried everything else that's been suggested on this thread and nothing has worked yet.  I understand though that some of those things will have worked for others.

Thanks again for the help.

[minimi66]

10 hours ago, DirtyMike0330 said:

OP, the goal here is that you need to figure out why 45 ASW is not working on your system, if you are indeed selecting it but your frames are staying unlocked and hitting the 70s. We have a similar system and the same VR headset, unlike some folks giving you insane advice. I have attached pictures of my settings so you can compare. In the picture of the Oculus Home app, you would click on the Quest Pro and you can slide the render scale to the right to 1.5 or 1.7 (I have mine maxed at 1.7)

With these settings, your ASW should be locked to 45 and you will have smooth gameplay in every scenario, including multiplayer. If, with these settings, your ASW is not locking you to 45, then something else is going on in your system. 

You do not need WMR, you do not need to drop your render resolution, you do not need anything extra. Also, I am running this on the multithreading executable. 

 

Hey can you supply your OTT Quest Link settings please?  I have some from Tenpox's post so i need to know if they are ok or will mess something up here?

Thanks v  much.

Edited April 14, 2023 by minimi66

[DirtyMike0330]

26 minutes ago, minimi66 said:

Hey can you supply your OTT Quest Link settings please?  I have some from Tenpox's post so i need to know if they are ok or will mess something up here?

Thanks v  much.

 

I use basically the same settings  P.S. I would also disable bloom in DCS, it generally doesn't look great in VR.null

null

[minimi66]

Thanks, so i've tried the OTT Profile on the MT Build and the frame rate is absolutely locked down at 45 Hz the entire time. Unfortunately the ground stuttering/jerking is still there.  The image quality is fantastic though, best yet.

Am now going to try the same profile on the Non-MT Build.

Thanks again.

[minimi66]

Same result on ST Build.  So i'm now fairly sure its a hardware issue?

Can't think what else it could be?

[Glide]

11 minutes ago, minimi66 said:

Can't think what else it could be?

You will always have the ground stutter with those settings.  Trust me.  I didn't test clouds, since I turn them off.  Vis Range LOW, AF off, AA, off, terrain shadows OFF.  The issue is in the graphics pipeline.

[DirtyMike0330]

3 minutes ago, Glide said:

You will always have the ground stutter with those settings.  Trust me.  I didn't test clouds, since I turn them off.  Vis Range LOW, AF off, AA, off, terrain shadows OFF.  The issue is in the graphics pipeline.

Again, a false statement. I can zip through a major city on the PG, on the deck, looking out right or left, and it is perfectly smooth. And you preface your BS with statements like "I turn off clouds". Like, why are you even in VR? Why spend money on this hardware if you are going to lower your settings so drastically? Also, why are you continuing to offer up your BS to someone with superior hardware to yours and a completely different VR ecosystem? Go away lol

[minimi66]

Ok, so i disabled Hyper-Threading and Virtualisation in BIOS and the ground stutter is MUCH reduced!!  Its pretty much un-noticeable 95% of the time.  The slight issue now is ghosting of buildings/trees/objects etc.  That sensation of the object stretching very slightly as you look at it passing over it.

I've had this before a while back and i think i fixed it with either an in-game setting adjustment or possibly a change of encode resolution width in OTT/ODT or a change of rendering resolution in Oculus app?

Point is this is the most progress made so far! I'm a happy camper right now!  Still work to be done though!

Thanks again.

[DirtyMike0330]

23 minutes ago, minimi66 said:

Same result on ST Build.  So i'm now fairly sure its a hardware issue?

Can't think what else it could be?

Just to clarify: You have confirmed you have the correct runtime selected in the Oculus Home App, your multithread launcher has "X:\DCS World OpenBeta\bin-mt\DCS.exe" --force_OpenXR in the properties target field? Are you using OpenXR Toolkit at all? I would recommend it because it will allow you to turn on a performance overlay that will show you what your CPU and GPU is doing during gameplay. 

Quickstart | OpenXR Toolkit - https://mbucchia.github.io/ - It is VERY simple to setup. 

Also just do a quick inventory to make sure you don't have any unnecessary or possibly conflicting software still installed, such as anything to do with windows mixed reality. 

1 minute ago, minimi66 said:

Ok, so i disabled Hyper-Threading and Virtualisation in BIOS and the ground stutter is MUCH reduced!!  Its pretty much un-noticeable 95% of the time.  The slight issue now is ghosting of buildings/trees/objects etc.  That sensation of the object stretching very slightly as you look at it passing over it.

I've had this before a while back and i think i fixed it with either an in-game setting adjustment or possibly a change of encode resolution width in OTT/ODT or a change of rendering resolution in Oculus app?

Point is this is the most progress made so far! I'm a happy camper right now!  Still work to be done though!

Thanks again.

The only annoying thing with ASW that I have noticed is with other airborne craft. If a plane flies by you quickly, they may ghost a little, this is currently unavoidable. I mostly notice it on merges; formation flying, and things of that nature are not a problem. However, your ground visuals should be smooth with ASW. 

I also have hyperthreading disabled 

[minimi66]

8 hours ago, DirtyMike0330 said:

Just to clarify: You have confirmed you have the correct runtime selected in the Oculus Home App, your multithread launcher has "X:\DCS World OpenBeta\bin-mt\DCS.exe" --force_OpenXR in the properties target field? Are you using OpenXR Toolkit at all? I would recommend it because it will allow you to turn on a performance overlay that will show you what your CPU and GPU is doing during gameplay. 

Quickstart | OpenXR Toolkit - https://mbucchia.github.io/ - It is VERY simple to setup. 

Also just do a quick inventory to make sure you don't have any unnecessary or possibly conflicting software still installed, such as anything to do with windows mixed reality. 

The only annoying thing with ASW that I have noticed is with other airborne craft. If a plane flies by you quickly, they may ghost a little, this is currently unavoidable. I mostly notice it on merges; formation flying, and things of that nature are not a problem. However, your ground visuals should be smooth with ASW. 

I also have hyperthreading disabled 

Ok thanks v much, i did have 2 WMR apps installed but not any more!!  

I just downloaded OpenVR Toolkit v1.3.1 from GitHub.  I have NO idea whatsoever how to access or use though!! Lmao!!

Please advise?

Ctl + F2 to open in game?

Then what? 

Edited April 14, 2023 by minimi66

[DirtyMike0330]

5 minutes ago, minimi66 said:

Ok thanks v much, i did have 2 WMR apps installed but not any more!!  

I just downloaded OpenVR Toolkit v1.3.1 from GitHub.  I have NO idea whatsoever how to access or use though!! Lmao!!

Please advise?

Ctl + F2 to open in game?

Then what? 

 

I have mine set like this because I don't like the default key binds to open the app in-game (see attached). So, once in-game, I hit ctrl + down arrow to open the app and then ctrl + up/right/left to navigate the menus. What you are looking for is under PERFORMANCE and then OVERLAY. Highlight the ADVANCED option, which should then put the overlay in your view when you exit OpenXR toolkit. This will give you your CPU/GPU performance. So, when you are flying in an area and looking at the ground, if you see stuttering, make a note if your CPU or GPU is exceeding 10ms of frame time or going haywire in some fashion. 

null

[minimi66]

Can't get OpenXR Toolkit menu to open at all with any key combo.  Nothing happens?

[DirtyMike0330]

9 minutes ago, minimi66 said:

Can't get OpenXR Toolkit menu to open at all with any key combo.  Nothing happens?

Are you using Virtual Desktop? I thought I glimpsed that in an earlier response maybe. If so, see footer #1. 
 

[minimi66]

8 hours ago, DirtyMike0330 said:

Are you using Virtual Desktop? I thought I glimpsed that in an earlier response maybe. If so, see footer #1. 
 

No i uninstalled VD earlier today so it would not interfere with the testing etc.

I'm done for today and not sure to be honest if i can devote much more time to this.  It's still far from perfect and ground stutter is still there quite bad in Syria map particularly.

Tried a few more tweaks with Oculus app and in-game but its not in a state i really want to play in at the moment.  Maybe in a few updates time things will improve and i'll try again.  In the mean time i'm going to fly non-VR only for now  i think.  Not as if i can upgrade my hardware either!! Lol!

Thanks so much for all your help mate, i really appreciate it.  I'm heading back to 2D 180 FPS Heaven!!!  Fully maxed!!  

Good night and have a great weekend.

[slughead]

I run my rig (Oculus Pro) with ASW set to AUTO. There are two 45Hz settings in the OTT. Once is just 45Hz, and the other is 45Hz forced in the OTT. If your fps is not locking all the time at 45Hz then ASW is not forced. And if you can't achieve 90Hz when you've set your headset to 90Hz, then you will get stuttering. I would highly recommend running at 72Hz for now so that you walk before you can run. Once you achieve 72Hz consistently (and you won't all the time in terrains other than Caucus - and even in Caucus, you can make it drop down with hard turns over large towns).

I found the OTT confusing to begin with and couldn't be certain it was actually setting the parameters in the headset/oculus server.

Try using just the Oculus Debug Tool. This is an Oculus tool, unlike the OTT which is a third-party tool. The settings are clearer and might help you resolve the problem which you can then map onto the OTT to make game-specific profiles. Just don't have both running together.

In the ODT, it has 45Hz ASW enabled and 45Hz ASW disabled. It makes it obvious to know which is which. If you have set your headset to 72Hz, this will give you 36Hz, i.e. half your headset refresh rate.

Once you are achieving 72Hz, you can then start looking at higher refresh rates. I have stayed at 72Hz and have my DCS settings to the max including MSAA at x4! But I also don't run at 1.7x resolution. The clarity is fine at 1.3x so pushing higher than that is just making DCS work harder and the Oculus server as it has to compress that image down to the encoder resolution and then the headset down to the display resolution. Walk before you can run.

I saw your benchmark scores. They look ok for your motherboard and 4090. What is your memory speed set to? XMP?

[minimi66]

3 hours ago, slughead said:

I run my rig (Oculus Pro) with ASW set to AUTO. There are two 45Hz settings in the OTT. Once is just 45Hz, and the other is 45Hz forced in the OTT. If your fps is not locking all the time at 45Hz then ASW is not forced. And if you can't achieve 90Hz when you've set your headset to 90Hz, then you will get stuttering. I would highly recommend running at 72Hz for now so that you walk before you can run. Once you achieve 72Hz consistently (and you won't all the time in terrains other than Caucus - and even in Caucus, you can make it drop down with hard turns over large towns).

I found the OTT confusing to begin with and couldn't be certain it was actually setting the parameters in the headset/oculus server.

Try using just the Oculus Debug Tool. This is an Oculus tool, unlike the OTT which is a third-party tool. The settings are clearer and might help you resolve the problem which you can then map onto the OTT to make game-specific profiles. Just don't have both running together.

In the ODT, it has 45Hz ASW enabled and 45Hz ASW disabled. It makes it obvious to know which is which. If you have set your headset to 72Hz, this will give you 36Hz, i.e. half your headset refresh rate.

Once you are achieving 72Hz, you can then start looking at higher refresh rates. I have stayed at 72Hz and have my DCS settings to the max including MSAA at x4! But I also don't run at 1.7x resolution. The clarity is fine at 1.3x so pushing higher than that is just making DCS work harder and the Oculus server as it has to compress that image down to the encoder resolution and then the headset down to the display resolution. Walk before you can run.

I saw your benchmark scores. They look ok for your motherboard and 4090. What is your memory speed set to? XMP?

Hey there,

Thanks v much for what sounds like some really solid advice. I will definitely give those steps a try. 
I’ll have a go with ODT which I used a LOT with my Quest 2.

Yes I was v happy with the benchmark results.

I have XMP enabled and RAM is running at 3600 MHz. I’ve actually got another 32GB of identical DIMMs that I could install but not sure what the Channel 1 & 2 technology will do to the performance in that situation. 
Doubt it’s needed either?

My PCIE bus was set at Auto but I changed it to 4 as you suggested and it raised the data rate through my USB-C cable from 2 Gbps to 2.5

I’m reasonably sure that the PC-Link USB C Cable-Quest Pro chain is bottlenecked to some degree in my case. I’ve got some new hardware arriving that might help there, maybe not.

I’ll try those changes in refresh rate and rendering resolution and report back. 
 

Thanks. 

 

 

 

[Shirtless]

Check your Nvidia Control Panel for Max frame rate. 

In OTT, set CPU priority to high.

 

Hope you find a smooth configuration.

Edited April 15, 2023 by Shirtless
typo

[Bishop8371]

Come check out the VR4DCS discord, there’s some quest specific channel’s there for optimizing dcs. I’ve found way more help there than the forums.

https://discord.gg/vr4dcs-610534461456777257

[minimi66]

4 hours ago, Bishop8371 said:

Come check out the VR4DCS discord, there’s some quest specific channel’s there for optimizing dcs. I’ve found way more help there than the forums.

https://discord.gg/vr4dcs-610534461456777257

Thanks but Discord link expired by the time I saw your post, please send again if you see this?

[minimi66]

On 4/15/2023 at 2:46 AM, slughead said:

I run my rig (Oculus Pro) with ASW set to AUTO. There are two 45Hz settings in the OTT. Once is just 45Hz, and the other is 45Hz forced in the OTT. If your fps is not locking all the time at 45Hz then ASW is not forced. And if you can't achieve 90Hz when you've set your headset to 90Hz, then you will get stuttering. I would highly recommend running at 72Hz for now so that you walk before you can run. Once you achieve 72Hz consistently (and you won't all the time in terrains other than Caucus - and even in Caucus, you can make it drop down with hard turns over large towns).

I found the OTT confusing to begin with and couldn't be certain it was actually setting the parameters in the headset/oculus server.

Try using just the Oculus Debug Tool. This is an Oculus tool, unlike the OTT which is a third-party tool. The settings are clearer and might help you resolve the problem which you can then map onto the OTT to make game-specific profiles. Just don't have both running together.

In the ODT, it has 45Hz ASW enabled and 45Hz ASW disabled. It makes it obvious to know which is which. If you have set your headset to 72Hz, this will give you 36Hz, i.e. half your headset refresh rate.

Once you are achieving 72Hz, you can then start looking at higher refresh rates. I have stayed at 72Hz and have my DCS settings to the max including MSAA at x4! But I also don't run at 1.7x resolution. The clarity is fine at 1.3x so pushing higher than that is just making DCS work harder and the Oculus server as it has to compress that image down to the encoder resolution and then the headset down to the display resolution. Walk before you can run.

I saw your benchmark scores. They look ok for your motherboard and 4090. What is your memory speed set to? XMP?

Hi,

I tried the settings that you recommended but sadly they made no difference at all. The ground stuttering is still there to the same extent.  Tried with Virtualisation and  Hyper Threading on and off but neither made any difference either.

Tried ODT with all settings as per previous OTT ones before but trying both the 45Hz ASW enabled and 45Hz ASW disabled.  Neither made any difference.

The powered USB-C hub i bought didn't even work, there was no connection at all to the Quest Pro.  Quest client said hardware incompatible.

I'm now convinced this is some sort of other hardware issue.  Not sure what but i'm losing the will to live with this?  I'd love to know what my ratio of flying to fiddling is as of now!

[minimi66]

10 hours ago, minimi66 said:

Thanks but Discord link expired by the time I saw your post, please send again if you see this?

Managed to join the Discord channel but even after completing the rules agreement page i can't post anything?

[slughead]

5 minutes ago, minimi66 said:

Hi,

I tried the settings that you recommended but sadly they made no difference at all. The ground stuttering is still there to the same extent.  Tried with Virtualisation and  Hyper Threading on and off but neither made any difference either.

Tried ODT with all settings as per previous OTT ones before but trying both the 45Hz ASW enabled and 45Hz ASW disabled.  Neither made any difference.

The powered USB-C hub i bought didn't even work, there was no connection at all to the Quest Pro.  Quest client said hardware incompatible.

I'm now convinced this is some sort of other hardware issue.  Not sure what but i'm losing the will to live with this?  I'd love to know what my ratio of flying to fiddling is as of now!

A hub? I take it you don’t have a USB-C connection on your motherboard? Do you have USB 3? Have you tried USB 3 to USB-C cable? Alternatively a USB-C PCIE card may solve your problem but I appreciate you probably don’t want to spend more money at this time. Virtualisation has nothing to do with this - this allows virtual machines to run on your PC. Hyper threading does not need to be disabled and I wouldn’t turn it off.

Have you tried it at 72Hz and 1.0x?