obious

You know what, I’m starting to think this may be exactly what it is. I’m running 1.7x rendering resolution in the Oculus settings (slider is all the way to the right) and I’m maybe thinking I should turn it down as whenever the ‘micro stuttering’/whatever happens I notice my FPS dips to ~82-83fps before rising back up to 90. This is even more proven by the fact that I just spent the last two hours installing windows 11 on an empty NVME drive, I had lying around only to experience the exact same behaviour

Tried this, had no noticible impact. Thanks for the suggestion Thinking about it a bit more, this is actually a more acurate description of what I experience (micro 'sawtooth'/tears in the image)

Just to clarify a bit more, the ‘micro stuttering’ as I refer to it as doesn’t just happen when I do fast barrel roles. It also happens if I do a flyby of an aircraft (whilst looking at it) or just look around the cockpit. I wouldn’t say it’s every few seconds on a repeatable basis either but certainly happens 2-3 times in a 10-15 period. Just to be clear again, this issue goes away with turbo mode enabled and comes back when it’s off (every single time).

Hmm, I’m thinking of building a new rig when the 14th gen Intel CPUs come out but it’s interesting that you’re not seeing any microstuttering with your rig which is significantly more powerful than mine. BTW, I take it you don’t have the same experience with toggling turbo mode on vs. off like I do (ie you have no stutters when doing barrel roles etc with turbo mode off?)

I don’t think my microstuttering has anything to do with the CPU and I can toggle turbo mode on and off in game and the stutters appears and disappear accordingly. I had bloom turned off as per the instructions for DVR and I did try running my QP at 72Hz but I got an intolerable flickering that I couldn’t handle. I don’t think FPS/frametimes are the issue as I have plenty of headroom (my testing missions is a simple free flight mission in the PG using the F18); my CPU frametimes are around 4ms with my GPU frametimes sitting around 6ms

I’m running at 90fps with a PCIe 5 (Z690 TUF WifI) motherboard. I’m also running a water cooled setup and thermals have never been an issue. As well as my overclock, I’ve disabled e cores so I’m forcing DCS to run on the performance cores and I’ve also disabled hyper-threading. I am however running Windows 10 which could possibly be an issue? I did experiment with the DFR mod but tbh, it feels like a bit of a ‘hack’ given all the steps you have to go through so I turned it off (I also was seeing a very noticeable ‘box’ in the centre of my FOV which I can only deduce as being caused by the border where the DFR shifts from high-res sections of the quad view to low-res. It wasn’t immersion breaking but was a little annoying to say the least). Are you running turbo mode with OXRTK? Like I mentioned above, my experience with micro-stutters goes away when I enable turbo mode which is a bit annoying as I loose the ability to see how hard (or not) my system is working. I may test out a Win 11 install later tonight with a spare SSD I have lying around.

Any update on this at all?

Yes, I’ve done that. I may try turning on HAGS as someone mentioned in a primer post but at this point I’m just clutching at straws

Ha got it. Thanks

Overall, I have to agree with the sentiment here; perf with MT has definitely improved. In ST I’m getting a GPU frame time of around 8ms whereas in MT I’m getting 5/6ms (this is just a free flight mission in the PG map). I suggest deleting the original install and downloading a new copy. I will however say that I’m getting pretty evident microstutters in MT that aren’t present in the ST version. The only way around this is to use Turbo Mode but that has its own issues

Got it, thanks

When using my Quest Pro with the MT exe, I notice that I'm getting pretty evident micro-stuttering occuring (that isn't being reported in the frame rate counter) when performing fast actions (ie fast barrel roles whilst looking at a fixed point on the terrain or doing a flybys etc). Whats weird is that these micro stutters are gone when using the ST exe. I've done a number of things trouble shoot (disabled E cores on my CPU, lowered my rendering setttings etc, deleted my DCS install and downloaded a 'fresh' copy, installed the latest Nvidia drivers) but the only thing that seems to solve it is to enable Turbo Mode in the OpenXR Toolkit. This would normally be fine but it prevents framerate counters from showing performance info (CPU/GPU response times) which makes fine tuning graphics settings difficult and generally causes other unstableness. Has anyone else experienced this or just me?

Simply put, do I still need the --force_enable_VR --force_OpenXR switches for the desktop shortcut or can I do without them?

I’m not necessarily talking about increasing the amount of memory I have, just the speed

Given that we've had MT for a while now and most of the bugs people saw early on have been quasahed, I'm wondering if RAM speed still plays an important role in VR? I currenlty have 32GB of Corsiair Dominator RAM (CAS16, 3600Mhz) and given where RAM prices are at the moment, I wonder if it'll add much to my experience if I switch to a kit running at 4000Mhz (current limit of my mobo). Overall, my Quest Pro VR experience with multi-threading has been positive but I suffer from what only can be described as micro-stuttering from flying even simple quick start missions (NTTR F-18 Free Flight mission for example) and am trying to think of what hardware changes I can make to improve things (GPU frametimes are siting about the 5ms that mission). I'm already running Tubo Mode from the OpenXR Toolkit which has definitly helped but the seemingly random micro pauses are detracting from the overall experience andw enjoyment. Thanks

Is that the frame rate throttling setting? @mbucchia Does the OXRTK Companian App in-game pop up save the setting values to a file anywhere? I'd be great if I could change the settings via a file rather than the pop-up

Nope, I've checked under aircraft specific settings as well as under General

For the life of me, I'm unable to change the default cockpit FOV when playting in pancake/2D mode. I've changed the external FOV setting, has no effect. I've also changed the default snapview setting via RCTRL+NUM0 and it still doesn't take effect. Anyone else have this problem? Thanks

Where are you capping the frame rates?

Could possible be due to Turbo Mode being on? I had the same experience

To chime in here, I was having terrible micro stuffers until I enabled turbo mode now they’re 98% gone. I wonder what Turbo Mode does to help combat micro stuttering

+1

Can confirm that ED have done something to break this setting (shadows=5). All my settings are reverted to default if I open up the settings menu without touching anything.

Turbo mode is off Will try that Yes, the outline of a rectangle is what I mean. I've also tried the PG map and I can see it their also. Thanks

Ok, so after playing around with this for the past few hours I thought I'd provide my 2 cents. The performance improvement is immediately apparent. After runnning a simple NTTR F-18 free flight mission (with Broken Clouds 7 on Ultra, 2x MSAA) that struggled, the same mission becomes instantly playable. I'm finding it difficult to dial in my settings (to take account of the additional system resources I now have. Prior to DFR, I was seeing around 30% headroom being reported via the OTT HUD Performance view but when using DFR, that number jumps to 98%. I'm not entirely sure its accurate as after changing some settings to utilize the system headroom (MSAA now at 4x, render scalling in the OTT at 1.2), that 98% headroom figure doesn't really change. The only impact I see is that the Quest Pro I'm using drops down to 45PFS from 90FPS (which I rearly experienced before). After closing DCS and starting it again (to change an OTT setting etc), DCS hangs (white box; see attached image). Anyone else experienced this? Not sure if this is a DFR thing or not but the sound is very 'choppy'. I'm using an encode resolution of 3664 and an Encode Bitrate of 960 but I'm not entirely sure if these settings are correct? When using DFR, I notice what I can only describe as a 'box' that follows my line of sight/my eyes and is viewable only in the periphery (I'm assuming this is the 'fully' rendered image vs. the lower-res part of the quad-view). Its only noticible when looking at parts of the rendered image that span high brightness/contrast levels (like when I look back at the wings of my F-18 and I can see both the sea and the sky in the saame image. Not sure if I need to tune the settings.cfg here somewhat/somehow. Whilst the instructions are great and perfectly clear, I think using DFR with the Quest Pro may not be for everyone. I had to setup a Meta developer account (which required a credit card and home address) and toggle a bunch of settings deep in the bowls of the Oculus software.