Meta Quest Pro Settings

[Mr_sukebe]

If it helps anyone, I successfully use the following:

 

https://www.amazon.co.uk/gp/product/B07K7DGKHN/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&th=1

I use the above straps side to side over the headband for comfort.  Dirt cheap and works really well

https://www.amazon.co.uk/gp/product/B07FMYV5H6/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&th=1

The above is the USB cable.  Not expensive, and just works.  I data stream AND power the unit with it

https://www.amazon.co.uk/gp/product/B00VE4UJD4/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1

I've ended up with 3 of these powered USB hubs and now run ALL of my USB peripherals off them.  My Gigabyte motherboard has had USB failures and I wonder if that's a result of using them to power peripherals.  

Edited October 24, 2023 by Mr_sukebe

[sze5003]

If it helps anyone, I successfully use the following:
 
https://www.amazon.co.uk/gp/product/B07K7DGKHN/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&th=1
I use the above straps side to side over the headband for comfort.  Dirt cheap and works really well
https://www.amazon.co.uk/gp/product/B07FMYV5H6/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&th=1
The above is the USB cable.  Not expensive, and just works.  I data stream AND power the unit with it
https://www.amazon.co.uk/gp/product/B00VE4UJD4/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1
I've ended up with 3 of these powered USB hubs and now run ALL of my USB peripherals off them.  My Gigabyte motherboard has had USB failures and I wonder if that's a result of using them to power peripherals.  

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.

[Ahogephilia]

9 hours ago, slughead said:

I don't know what specs you are running but I can maintain 72fps over normal Oculus Link. The real test is what can you get near ground level over a town and max corner speed/ Level flight is not really a test of performance.

Yes, this benchmark isn't perfect, but I wanted to show a non-CPU dependent change.

Even when Cpu is depended, there is a slight frame improvement.

 

test condition : 5800x3d, 48gRAM, rtx3090ti, msaa x2, af x16,

not using shader mods, airlink 400mb/s

oculus via openxr + qvfr

 
 

 

vdxr + qvfr

 

 

Edited October 25, 2023 by Ahogephilia

[nilpointer]

11 hours ago, slughead said:

Righty then. I might give it another go. Ta mucha.

Keen to hear if you have a favourable outcome. I was previously using your KISS methodology (which I subscribe to also) for my Link setup and getting pretty ok results, but the new VD is really exceeding my expectations and I find it much simpler to use than my "mostly works" link cable setup. As an added plus I can plugin to power and eliminate the battery drain issue.

It is worth noting a couple of things:

- Like you I am using a 4090
- My router is 3ft from my flight setup and my PC is ethernet wired to said router as well

I've spent another 2 hours since last posting just trying all of the variations of VD graphic settings with DCS settings and testing the outcomes against a few benchmark flights and I remain a little torn.

With everything high + DLSS + VD Godlike I can reliably keep my 72fps through most flying conditions. The latency is up + 40ms but it's not really noticable to me. My switching down to VD Ultra and keeping DLSS I can get that latency down or go to DLAA which does improve clarity slightly, but I would already say that for me with DLSS on the clarity of MFDs on VD already exceeds that of Link.

Unfortunately as is oft evidenced reading this forum there is such a wide array of setups that it is really often hard to tell what works for one may not always reliably replicate for someone else on a similar rig.

I definitely am impressed though.

[sze5003]

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.

[Ahogephilia]

39 minutes ago, sze5003 said:

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.

 

Do you have HAGS turned on?

I've experienced severe stuttering when both oculus link and 'hags' are enabled.

[markturner1960]

Have you tried using with a different title such as MSFS etc? At least that would give you an indication where the issue maybe. I will repeat my advice to persevere, as once you find the issue ( and you will) the headset is awesome. 
 

I was lucky enough to have Lukas Wolta help me troubleshoot my issues, maybe reach out to him? 
 

what were you using before? Maybe some residual conflict? 

[slughead]

8 hours ago, nilpointer said:

Keen to hear if you have a favourable outcome. I was previously using your KISS methodology (which I subscribe to also) for my Link setup and getting pretty ok results, but the new VD is really exceeding my expectations and I find it much simpler to use than my "mostly works" link cable setup. As an added plus I can plugin to power and eliminate the battery drain issue.

It is worth noting a couple of things:

- Like you I am using a 4090
- My router is 3ft from my flight setup and my PC is ethernet wired to said router as well

I've spent another 2 hours since last posting just trying all of the variations of VD graphic settings with DCS settings and testing the outcomes against a few benchmark flights and I remain a little torn.

With everything high + DLSS + VD Godlike I can reliably keep my 72fps through most flying conditions. The latency is up + 40ms but it's not really noticable to me. My switching down to VD Ultra and keeping DLSS I can get that latency down or go to DLAA which does improve clarity slightly, but I would already say that for me with DLSS on the clarity of MFDs on VD already exceeds that of Link.

Unfortunately as is oft evidenced reading this forum there is such a wide array of setups that it is really often hard to tell what works for one may not always reliably replicate for someone else on a similar rig.

I definitely am impressed though.

I gave it a try last night. For me, at various god like, ultra etc settings I could not maintain 72fps in Caucus free flight. It was quite a stutter fest. No sparklies though. I had qvfr working as well. I am linked direct to my pc wireless hotspot and which has no issues at all. What I could see on the DCS fps meter is huge spikes whereas running with Oculus Link is mostly flat with some tiny bumps. Something clearly isn’t right. I might have another go today but I’m feeling that I’ve wasted £15 on an experiment when my Oculus Link was working ok.

What I did notice, albeit not enough time to really tell, is that with VD there was no audio stutters.

[Andrew u.k.]

I flew with 10 others over Syria last night in quite an empty map, it was a nav exercise. 
I was getting down to 20 FPS, I have an RX6950 XT, and i5-10600K , 64k DDR4 3200. Quest pro on a cable.

It looked awful, should I be expecting better?
2xMXAA and I was getting stutters

I've followed Slugheads instructions, kept it simple previously, it looked good, I hope you figure it out soon and give me an idea of what to do. 

Do I need to upgrade the processor?  

[slughead]

6 hours ago, sze5003 said:

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.

This sounds like you are experiencing the core parking bug in the multi-threaded binary. There is a workaround here:

 

[sze5003]

 

Do you have HAGS turned on?

I've experienced severe stuttering when both oculus link and 'hags' are enabled.

Yea I checked this morning and HAGS is on. I will try tonight to turn it off and see if that resolves anything.

Have you tried using with a different title such as MSFS etc? At least that would give you an indication where the issue maybe. I will repeat my advice to persevere, as once you find the issue ( and you will) the headset is awesome. 
 
I was lucky enough to have Lukas Wolta help me troubleshoot my issues, maybe reach out to him? 
 
what were you using before? Maybe some residual conflict? 

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.

This sounds like you are experiencing the core parking bug in the multi-threaded binary. There is a workaround here:
 

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.

[slughead]

4 minutes ago, sze5003 said:

It does sound like that after having a slim 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.

A simple test is to try the single-threaded binary. Also, I run with HAGS on and don't have any problems.

[halufpv]

8 hours ago, sze5003 said:

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.

Use 500mb link encoding. Anything above is prone to problems in my experience, especially the audio stutters. I can't tell a difference and I doubt you can.

[slughead]

2 minutes ago, halufpv said:

Use 500mb link encoding. Anything above is prone to problems in my experience, especially the audio stutters. I can't tell a difference and I doubt you can.

Exactly. I actually find leaving it on default settings does the job. More is not always better.

[halufpv]

Also, I would change nothing else on the oculus debug tool than the bitrate and ASW if you don't like it, but that's it. The minecraft graphics when loading are normal. I'd try resetting all your DCS, nvidia panel, uninstall openxr everything and see if it's still that bad. With your graphics, it shouldn't be that bad on default everything, so I suspect you've messed something up at some point. Establish a baseline and change one thing at a time

[sze5003]

Use 500mb link encoding. Anything above is prone to problems in my experience, especially the audio stutters. I can't tell a difference and I doubt you can.

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

[sze5003]

Also, I would change nothing else on the oculus debug tool than the bitrate and ASW if you don't like it, but that's it. The minecraft graphics when loading are normal. I'd try resetting all your DCS, nvidia panel, uninstall openxr everything and see if it's still that bad. With your graphics, it shouldn't be that bad on default everything, so I suspect you've messed something up at some point. Establish a baseline and change one thing at a time

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.

[Mordants]

32 minutes ago, sze5003 said:

56 minutes ago, halufpv said:

Use 500mb link encoding. Anything above is prone to problems in my experience, especially the audio stutters. I can't tell a difference and I doubt you can.

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

I had to down to 200 to achieve a stutter free esperience

[Flyingfish]

42 minutes ago, sze5003 said:

1 hour ago, halufpv said:

Use 500mb link encoding. Anything above is prone to problems in my experience, especially the audio stutters. I can't tell a difference and I doubt you can.

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

I've been getting bad stuttering with the link cable in 2.9 but didn't get it in 2.8. For some reason though it works very well with airlink so if you've got a good router it might be worth trying airlink and seeing if you still get the audio stutter/stutters

[sze5003]

I've been getting bad stuttering with the link cable in 2.9 but didn't get it in 2.8. For some reason though it works very well with airlink so if you've got a good router it might be worth trying airlink and seeing if you still get the audio stutter/stutters

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.

[Flyingfish]

7 minutes ago, sze5003 said:

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.

Yeah, bitrate needs to be 0 for airlink. Good luck

[FupDuck]

12 hours ago, sze5003 said:

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.

I think your settings are just too high. I don't think there's any computer that can run the settings you have smoothly in VR. I suggest setting the Oculus slider to 72Hz, 1.0x resolution (default), and see how it looks, then if its smooth, work your way up. Bitrate doesn't really have that much of an effect on your FPS unless it's way too high. I recently bumped mine from 400 to 700 with no difference in smoothness (via cable, I find VD gives lots of stuttering compared to link, all else being the same). Also, MSAA is not your best bet these days for anti aliasing, given the new options available. In general, your DCS settings will affect performance way more than bitrate.

I really don't think this is a problem with your headset. You just need to start low with all your settings and work your way up. This is the way of VR .

Edited October 25, 2023 by FupDuck

[sze5003]

I think your settings are just too high. I don't think there's any computer that can run the settings you have smoothly in VR. I suggest setting the Oculus slider to 72Hz, 1.0x resolution (default), and see how it looks, then if its smooth, work your way up. Bitrate doesn't really have that much of an effect on your FPS unless it's way too high. I recently bumped mine from 400 to 700 with no difference in smoothness (via cable, I find VD gives lots of stuttering compared to link, all else being the same). Also, MSAA is not your best bet these days for anti aliasing, given the new options available. In general, your DCS settings will affect performance way more than bitrate.
I really don't think this is a problem with your headset. You just need to start low with all your settings and work your way up. This is the way of VR .

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.

[Flyingfish]

41 minutes ago, sze5003 said:

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.

Using turbo mode in openxr toolkit made a big difference in reducing stutters for me. I think it'd definitely be worth trying that 

[sze5003]

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.