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

[5ephir0th]

Here is my settings and you have my specs at the bottom, 80hz and 2700px per eye, ffv activated on OpenXR toolkit, 80 fps stables

[minimi66]

8 hours ago, slughead said:

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?

Hi, sorry i wasn't very specific on my post.  I bought this:

https://www.amazon.co.uk/dp/B0BGHVQNCH?psc=1&ref=ppx_yo2ov_dt_b_product_details

on the advice of @DirtyMike0330

In a post he made earlier in this thread.  Just to see if it made any difference to Link Cable connection etc.  Maybe it aint the same model he has but it was the closest i could get on Amazon UK.  Not his fault at all it was my decision alone to try it.  Maybe i got a different model and that's why and maybe it wouldn't have made a difference on my system anyway?

I tried 72  Hz Oculus refresh rate and 1.0 rendering res but again zero difference. 

What is the best DCS executable to use in this situation?  I've been using "F:\DCS World OpenBeta\bin\DCS.exe" --force_enable_VR --force_OpenXR"

Also, am i supposed to apply ODT settings prior to attaching Link Cable or after and do i close ODT before starting DCS or leave it open.  I have the ODT console open as well but have tried it off with no difference in results.

 

 

[DirtyMike0330]

17 minutes ago, minimi66 said:

Hi, sorry i wasn't very specific on my post.  I bought this:

https://www.amazon.co.uk/dp/B0BGHVQNCH?psc=1&ref=ppx_yo2ov_dt_b_product_details

on the advice of @DirtyMike0330

In a post he made earlier in this thread.  Just to see if it made any difference to Link Cable connection etc.  Maybe it aint the same model he has but it was the closest i could get on Amazon UK.  Not his fault at all it was my decision alone to try it.  Maybe i got a different model and that's why and maybe it wouldn't have made a difference on my system anyway?

I tried 72  Hz Oculus refresh rate and 1.0 rendering res but again zero difference. 

What is the best DCS executable to use in this situation?  I've been using "F:\DCS World OpenBeta\bin\DCS.exe" --force_enable_VR --force_OpenXR"

Also, am i supposed to apply ODT settings prior to attaching Link Cable or after and do i close ODT before starting DCS or leave it open.  I have the ODT console open as well but have tried it off with no difference in results.

 

 

Yeah, that does appear to be a different one than the one I linked- mine actually has a window that shows how many amps it is pushing out when it is charging my Quest Pro up. Yours looks like the power delivery port is only the bottom one; you did use that one and not one of the sides, right?

[slughead]

You shouldn't need a HUB but if your motherboard only has one USB-C connection and you need more then I can see why someone would use one. I would be running without the HUB to eliminate variables.

I see you are using winwing hardware. I am not but wasn't there an issue with the software for this causing stuttering? There should be a thread on this somewhere.

Is this stuttering/jitter happening once a second, 10 times a second, 100s of times a second? (I don't know the extent of your jitter problem). Does it occur looking straight ahead or only when looking on the 3-9 line?

What other apps are running? What does your task manager show for CPU load when idle? What processes are making up the idle load? Have you shut down all non-essential apps?

Is your signature up to date? It says you are running windows 10. I would be running windows 11 as that is designed with your processor in mind whereas windows 10 isn't. I am not saying that's the problem, but that you are not getting the best out of your hardware running windows 10.

Edited April 16, 2023 by slughead

[minimi66]

8 hours ago, DirtyMike0330 said:

Yeah, that does appear to be a different one than the one I linked- mine actually has a window that shows how many amps it is pushing out when it is charging my Quest Pro up. Yours looks like the power delivery port is only the bottom one; you did use that one and not one of the sides, right?

Used both, one didn't connect to headset and the other connected but said incompatible hardware.  I can't get the exact one you have in UK as far as i know?

Am thinking of switching GPU's back to my RTX 3080Ti which i luckily still have and selling the 4090.  I had better results with 3080Ti to be honest.

Thanks for the info though.  It was def worth a try.

[slughead]

32 minutes ago, minimi66 said:

What is the best DCS executable to use in this situation?  I've been using "F:\DCS World OpenBeta\bin\DCS.exe" --force_enable_VR --force_OpenXR"

I am using the multithreaded executable. I haven't tried the single-threaded one that you are using for a while now.

33 minutes ago, minimi66 said:

Also, am i supposed to apply ODT settings prior to attaching Link Cable or after and do i close ODT before starting DCS or leave it open.  I have the ODT console open as well but have tried it off with no difference in results.

Run ODT after the Oculus app starts. You can close it once you have made the changes after the link is established. When the link is disconnected, you would have to make the changes again as I think the link resets to default.

[slughead]

nullThose spikes both me a little. I wonder if these are indicative of your problem. Can you try the multithreaded executable in the open beta? This might solve your problem. If not, you need to look at what else might be running on your machine that's causing these spikes. Unless they're normal of course.... but I don't think I have encountered them.

[DirtyMike0330]

1 hour ago, slughead said:

You shouldn't need a HUB but if your motherboard only has one USB-C connection and you need more then I can see why someone would use one.

I mentioned the hub specifically for providing power to the Quest Pro; the Kuject cable solution did not work well for me, and the headset would still drain too quickly. With that hub, I can play all day and not run out of juice. The display is nice because it shows exactly how much amperage the hub is pushing out (close to 10 amps when it is charging the QP). 

[slughead]

1 minute ago, DirtyMike0330 said:

I mentioned the hub specifically for providing power to the Quest Pro; the Kuject cable solution did not work well for me, and the headset would still drain too quickly. With that hub, I can play all day and not run out of juice. The display is nice because it shows exactly how much amperage the hub is pushing out (close to 10 amps when it is charging the QP). 

Yeah, I can appreciate that. I've not suffered much power loss with my setup. Perhaps my motherboard provides more power. I'm still trying to find out how much. The manual isn't forthcoming.

 

I'm beginning to think the OPs problem isn't headset-related but process related. The spikes in frame-time on his fps graph are indicative of this. It would be worth him ensuring there isn't some other process causing these spikes such as the winwing software/drivers. Perhaps testing in 2D may show this isn't a head-set related issue.

[DirtyMike0330]

6 minutes ago, slughead said:

I'm beginning to think the OPs problem isn't headset-related but process related. The spikes in frame-time on his fps graph are indicative of this. It would be worth him ensuring there isn't some other process causing these spikes such as the winwing software/drivers. Perhaps testing in 2D may show this isn't a head-set related issue.

This is plausible because there’s enough folks here with similar high-end hardware having the same good experience with the QP. Unfortunately a local issue would be a lot more difficult to troubleshoot for the op. 
 

Speaking of which, @minimi66 you mentioned your 3080ti - is your 4090 upgrade brand new? Did you do a full wipe of previous GPU drivers prior to installing the 4090? With something like DDU? Just a random thought. 

[slughead]

1 minute ago, DirtyMike0330 said:

This is plausible because there’s enough folks here with similar high-end hardware having the same good experience with the QP. Unfortunately a local issue would be a lot more difficult to troubleshoot for the op. 
 

Speaking of which, @minimi66 you mentioned your 3080ti - is your 4090 upgrade brand new? Did you do a full wipe of previous GPU drivers prior to installing the 4090? With something like DDU? Just a random thought. 

I didn’t need to wipe my drivers with the same GPU upgrade.

[slughead]

@minimi66

 

 

[minimi66]

10 hours ago, slughead said:

 

SimAppPro WinWing software uninstalled and i understand how to fix tat issue if it returns, which it will if i use the software in future. SimAppPro creates an entry in Export.lue that causes the spiking.  Uninstalling didn't fix the stuttering.

Here is Process Lasso info on my CPU.

[slughead]

That shows that dcs is running below normal priority. Set it to high. It’s effectively being considered as a background application at below normal.

I will link you to another thread about optimising DCS and your system.

A lot of the information in this thread is still relevant for system optimisation, I.e. windows settings and processor priority.

 

 

[minimi66]

See non-VR performance below all settings maxed out.

8 hours ago, slughead said:

That shows that dcs is running below normal priority. Set it to high. It’s effectively being considered as a background application at below normal.

I will link you to another thread about optimising DCS and your system.

A lot of the information in this thread is still relevant for system optimisation, I.e. windows settings and processor priority.

 

 

Sorry, how do i select CPU Affinity in ProcessLasso?  Thanks.

Tried right-clicking but no option to set as High etc?

[minimi66]

So you think Windows 11 is a better choice then mate?  I can upgrade i guess and see?  I've seen a lot of posts over the years saying W11 has issues with DCS?  Hence why i avoided it.

Edited April 16, 2023 by minimi66

[slughead]

23 minutes ago, minimi66 said:

So you think Windows 11 is a better choice then mate?  I can upgrade i guess and see?  I've seen a lot of posts over the years saying W11 has issues with DCS?  Hence why i avoided it.

 

Stick to Windows 10 until you have solved your problem.

 

I don't use processor lasso. You need to change the process priority. Read that thread I linked about system optimisation. It tells you how to change the process priority. Mine is running at normal priority.

Edited April 16, 2023 by slughead

[minimi66]

Ok, but nothing above has fixed it yet?

[Blue73]

OTT can set process priority under profiles.

[minimi66]

8 hours ago, Blue73 said:

OTT can set process priority under profiles.

Thanks mate but already set it at both Normal and High and neither made any difference.

[minimi66]

So the stuttering is ever so slightly intermittent!  About 2 seconds without and 4 seconds with?

[slughead]

12 minutes ago, minimi66 said:

So the stuttering is ever so slightly intermittent!  About 2 seconds without and 4 seconds with?

What other processes are running that might be gobbling up processor time? What apps are in your taskbar?

[Blue73]

I remember just having the windows image viewer running I'd get constant regular 1-2 second pauses as the cpu kept spiking. 

[DishDoggie]

@minimi66 Nice System Sir Congratulation on your new Computer. It should run DCS like a Pro. If you have the time try running DCS like this. Your desktop apps to run DCS. NOTE I run WMR with a HP G2 you do not so do what you would do to run your VR headset. Just make sure you have the Shortcut setup correct and OpenXR Toolkit Companion and OpenXR Toolkit Installed. Newest Version. Start DCS and set up OpenXR Toolkit Companion like the menus below. You have a Nvidia Card so you should try NIS in PERFORMANCE. Turbo mode ON Set your Frame Rate Throttling to your VR headset or not if you wish. SYSTEM With TURBO MODE ON I get Stuttering IF this is not set OVERRIDE RESOLUTION ON=YES DISPLAY RESOLUTION (per eye) I set this to my VR headset resolution per eye specs. Use Your VR Headset Resolution per eye resolution here. After it is set up exit out of DCS to end the VR session and start it up again. With luck you will be Rocking The Socks off of DCS. I ONLY run the Standalone Version of DCS Not Steam. With Luck You already have this working. Congratulations on the New System have Fun

[minimi66]

10 hours ago, DishDoggie said:

@minimi66 Nice System Sir Congratulation on your new Computer. It should run DCS like a Pro. If you have the time try running DCS like this. Your desktop apps to run DCS. NOTE I run WMR with a HP G2 you do not so do what you would do to run your VR headset. Just make sure you have the Shortcut setup correct and OpenXR Toolkit Companion and OpenXR Toolkit Installed. Newest Version. Start DCS and set up OpenXR Toolkit Companion like the menus below. You have a Nvidia Card so you should try NIS in PERFORMANCE. Turbo mode ON Set your Frame Rate Throttling to your VR headset or not if you wish. SYSTEM With TURBO MODE ON I get Stuttering IF this is not set OVERRIDE RESOLUTION ON=YES DISPLAY RESOLUTION (per eye) I set this to my VR headset resolution per eye specs. Use Your VR Headset Resolution per eye resolution here. After it is set up exit out of DCS to end the VR session and start it up again. With luck you will be Rocking The Socks off of DCS. I ONLY run the Standalone Version of DCS Not Steam. With Luck You already have this working. Congratulations on the New System have Fun

Hi mate,

If only it was so simple!  I tried the above both with and without my OTT Profile for DCS MT executable but the ground stuttering is no better and even worse at times.  I don't really understand how i can input the per eye resolution you suggest as the OpenXR Toolkit settings don't correspond to my oculus client rendering resolution or any multiple of it? The frame times and thus FPS are literally all over the place!

If you have any other suggestions i'd love to hear?  I'm probably doing something wrong or one of the 10,000 settings needed to run DCS well is 1 notch off what it should be?   I probably need to do another 6-7 weeks of testing? 

My settings are above somewhere if you want to have a look and let me know?  Thanks again for the advice and your time.  Much appreciated.