sze5003

Quest pro can do 72hz so I can try that as well but I've noticed the micro stutters still occur even when ASW is on and it's locked at 45fps. With a 13900k and 4090 I should be able to use the full resolution of the headset, at least I'm reading that from others with the same specs. But I don't want to hijack the thread I opened my own post in the bugs and performance section. Hopefully this will be a good guide to folks that come in new and need some ideas on where to start.

I would also add if you are in VR don't have a lot of extra stuff running in the background and in your Nvidia control panel settings you should use prefer max performance for power settings and low latency mode to ultra, virtual pre-rendered frames to 1. I'm still going through and trying to understand why I have so many micro stutters in multithreaded DCS. Hopefully will get to the bottom of it but I've tried unparking cores, disabling HAGS, optimizing my windows install. I don't get the same issues in single threaded mode. There's gotta be a combination of settings that will work at some point I just haven't found them yet.

Devs of virtual desktop said it's a meta bug from a software update introduced a while ago. It's also apparent on quest 3. If you use virtual desktop and use high settings on there vs god mode or ultra it should reduce the sparkles.

This is visible to me too on my quest pro using virtual desktop mostly. Not so much in link cable or air link.

I'm using a 13900k, 32gb ram and a 4090. In dcs multithreaded I'm always getting CPU bound in the performance metric. I also fly in VR with a quest pro and in MT version I get a lot of microstutters. To the point that it becomes really annoying and sometimrmes unplayable even though ASW kicks in and I'm at 45fps. In ST mode I don't get the CPU bound message and I also don't get the microstutters or hiccups. Tried unparking my cores but that didn't seem to help with anything.

I've tried unparking all my cores in an attempt to see if the microstutters that happen in MT DCS will go away. Unfortunately this did not resolve anything for me. I still get a lot of intermittent microstutters and the only time I don't see them is when I'm only getting 90fps. Even if ASW kicks in and I'm at 45fps as the perf fps built in chart of dcs shows, I still get microstutters so I'm wondering if having asw on could be the cause.

Hi All, I've recently bought a Quest Pro and have had a chance to set everything up. I'm encountering some performance issues and was wondering if I could get some help with what I can do to alleviate them. I have attached a zip file with my DCS Logs, a few track files, and my settings. What I am encountering here is lots of stutter, fps spikes up and down, its generally not smooth due to the stutters every couple of seconds. After some time DCS becomes pretty laggy. You won't see it in the tracks because they are not that long but I've had to force quit before. I'm on the latest nvidia drivers, Gigabyte OC 4090, 32Gb DDR5 and intel 13900k. I am not seeing the same issues in single threaded DCS 2.9 open beta. If anything some initial stutter when I first load into a mission but after that it is pretty smooth overall. I read about core parking/unparking but I've tried two programs Park Control and CPU unpark but neither claimed to do that as I still saw in Windows Resource Monitor that some cores were parked. Also not sure if it is supposed to be there but if I enable the built in FPS monitor I always see "CPU Bound" in Red test at the top of the graph. DCS_VR_Log.zip dcs.log

You need to download it from here on the PC. It's not mentioned anymore because oculus headsets past the rift pretty much became standalone. https://www.oculus.com/rift/setup/

I know at one point you needed a developer account to enable eye tracking on the headset. I got Pro new a week ago and eye tracking is already enabled by default once you update to the latest software. I can turn it on and off from the headset dashboard. Although I did not install quad views yet myself. Mainly because I have a lot of stutter and fps drops and spikes in multithreaded DCS version and sometimes it gets so bad that it drops to 5 fps in the main menu in VR and I have to force quit it. DFR needs the multithreaded version of dcs to work properly. Just a heads up with his YouTube video settings, that bitrate did not work for me (960) and I don't think those are his current settings anymore. You can crank the resolution in oculus home to 1.5 and then change the bitrate as you see fit so you don't get any audio crackling or visual artifacts. Really no need to set resolution encode width either in the debug tool.

It's a lot of testing and messing with oculus settings, resolution, bitrate, back and forth. I have a quest pro and it's tiring. I can't get the multithreaded version of dcs working for me without it turning into 5 fps on the main menu at some point after some time. It doesn't start like that, starts fine and I can fly ok with stuttering here and there but eventually I have to use my headset controller to quit DCS through Link because dcs becomes unresponsive. I've stuck to just running the single threaded version for now.

I have high performance power.plan enabled. With a 13900k and 4090, I disabled HAGS in windows and it ran a little better. But the longer I fly, the worse performance gets. To the point where even in the menu I'm getting freezing and stutter, frames drop down to 5 at times. This is in VR.

No I didn't want to complicate things with testing the headset to see what could be causing my issues. Once I dial it in some more and im happy with the way it looks and runs I'll install openxr toolkit and DFR.

You will have to try it honestly. Just don't touch the settings in graphics options and they should remain intact from your 2.8. My 2.9 installation was fresh on an SSD and my impressions of it was that the reason I was having all the stutters and slide show in VR was because of the multithreaded version. Didn't have any issues with 2.9 in non multithreaded and that's what I'll be using. I still need to tweak it but besides disabling HAGS I didn't change any of my graphics settings in DCS or oculus debug tool (aside from bitrate).

Just make sure you launch the non multithreaded version. The regular bin folder should have the executable which is not mt.

Someone in the VR4DCS discord said in Nvidia control panel you want to turn on threaded optimization. I have not tried it but I'm glad to see that my issues were not from my system or from the USB C cable or headset. It was multithreaded dcs that seems to have some type of memory leak. Because with HAGS off it started out fine and the longer I flew, the worse it got.

Third round of testing tonight I disabled HAGS. When I started some missions everything seemed much smoother. Very slight audio stutter and when it wasn't 90fps and went down, it would stick to 45fps. Overall flying was not jerky and I had much less audio stutter and micro stutters. So I started lowering the bitrate. Didn't notice much of a difference in visuals at 690 from 740. There were still some audio stutters but then as time passes and I kept trying more missions, things started getting worse. I kept dropping the bitrate but it was not helping at all. Eventually even if I closed out of dcs and relaunched it, it would end up with very bad performance. It got so bad I was getting constant drops in the DCS main menu to the point that it lagged looking around so much. I would get the spinning hourglass glass then a side of black as I turned my head. Frame time graph looked insane. So then I found the non multithreaded binary and launched that. With the non mt version of the sim, everything was smooth. 90fps easily up high and around 45 as asw kicked in in low and populated areas. Flying was smooth, no stutters, barely any audio drop outs that I exited and lowered my bitrate anyway. Went back in and had no problems everything looked great, clear and flying was as it should be. Didn't have to turn down any settings. So there's definitely something wrong with the multithreaded version of dcs for me.

The DCS settings/oculus settings I run are not any different than the ones posted here by Tepnox on the second page. I'm using DLAA instead of MSAA too. But you are correct I'll reset everything after I run more tests tonight. I don't have openxr toolkit installed yet or quad views DFR yet. I'll do all that later IF I can get everything working properly.

Yea I have a couple of more things to try tonight: Test with HAGS off, no other settings changed everything as I left it last night. Then test with much lower bitrate than 700 or 500 and then try going even lower. Then test air link but for that I believe the bitrate needs to be reset to zero. If none of the above work then I'll launch the non multithreaded version of dcs. The pro is the only device on my 6ghz router so in theory I shouldn't have any connection issues with airlink. Edit: I did notice in the built in fps counter in DCS, that while I was flying and it was measuring, I noticed it said "CPU bound" above the little frame time chart. Not sure if that means anything.

Yea besides the encode resolution width and encode bitrate I have not changed anything else in the debug tool. Nothing is changed in Nvidia control panel as I installed latest GPU drivers, also using display driver uninstaller to clean up old drivers and did a clean install of the new Nvidia drivers before I got the Quest pro. Thanks to everyone for helping out..I've been away from dcs for like 8 months so this is also a fresh open beta install on an empty SSD. All I have to go on is that it initially started running ok minor stutters which is annoying and then just got worse and random with each instant action mission test as well as a full reboot of occulus service with each bitrate change.

I think if I remember correctly even with 500mb encoding I still had some audio stutter/stutters. I'll have to try it again.

Yea I checked this morning and HAGS is on. I will try tonight to turn it off and see if that resolves anything. I don't have MSFS. I was about to buy it on steam during the last sale but I forgot why I did not. Unfortunately don't have other VR titles to try aside from half life alyx. I used to have a reverb G2 but I uninstalled all windows wmr application items. It does sound like that after having a skim through that. Tonight I'll sit and read more through it. The side effects sound pretty similar and would also explain why I may not have run into the same problems the first night I got the headset.

I am pretty close to giving up and returning the headset. I sat down to do some more testing tonight. Im on a 13900k, 32gb ram and a 4090, using official oculus link cable. Each time I sit down to do something in DCS I get some pretty crazy and sporadic behavior. I know last time I left off with an encode bitrate of 740 and was getting audio stutter. Encode resolution width is 3905. Oculus home resolution is 1.5 and 90hz. Dcs settings are high everything, extreme clouds and visibility, civ traffic off, no lens flare, depth of field, blur and other effects off. Also using DLAA. I load a bunch of instant action missions and with each one I get audio stutter and some micro stutter. So I lower the bitrate by 10 each time. Each time I do this I don't really notice a difference and it seems when I make sudden moves the micro stuttering is there for a split of a second. I also restart oculus service from debug tool each time I make a change. This time I'm down to bitrate of 710 and I load up the river run instant action mission. I also enabled the fps metrics native to DCS. As soon as I load in, I always see the cockpit in super low resolution as if it's Minecraft until the mission fully loads. Not sure if this is expected but it happens every time I load in any mission until it's fully loaded in. From some odd reason the fps starts dropping from 90 to 30 to 20, sometimes even 5 and and back up to 80-90 and then back down like crazy. At this point it's a slideshow and I get the hourglass symbol. Hasn't done this before I'm baffled. Even quitting dcs is impossible at this point. I have to use the pro controller to quit the app from Link and at one point after I exited link desktop my headset just froze so I had to reboot it. Loaded DCS back up again and same thing, it was like an ongoing memory leak or something. This is the multithreaded version by the way. So I decide to reboot the PC and try again. This time it's a little better, I get the bitrate down to 700 but audio stutter and micro stutter intermittently is still there. I'm not really sure what to change anymore. I guess i can go through Nvidia control panel and check my global settings. I thought the G2 was annoying with windows wmr but I never experienced what I did today. Maybe I should reset everything in oculus debug tool and set everything back to zero but just leave oculus home resolution at 1.5 and leave it like that. It doesn't seem like I am making progress and I'm definitely not new to VR, have flown in VR through several headsets and lower PC specs before this, but this is just weird.

Those are all in UK but that's fine it gives me an idea for what to look for. I'm seeing bad reviews for the Syntech charging and data cable. I'll keep looking but I'm glad I at least have the official link cable for right now. I hope to do more testing with settings tonight, fingers crossed for no crashing or disconnects and report findings or what settings worked best here if everything goes to plan.

Thanks, I did return the Kuject cable. I bought an official meta cable and that connected to a type C port on the rear of my motherboard I get 2.3-2.4Gbps in the speed test. I may try another cable or maybe even a pcie USB C card if I can find a reliable one so I don't have to worry about my motherboard having issues with only 1 type C port handling all the throughput. Maybe I'll give the Syntec charging cable next.

My take on the encode resolution width from that statement is, if you use the automatic resolution setting in oculus home, you don't need to change the encode resolution width in the debug tool. If you don't use automatic resolution in oculus home then you would want to make sure the encode resolution width in debug tool matches the width that is set in oculus home (from the slider). But honestly I could also be wrong too.