MHAce75

thanks! i will check that out.

i found that with -100% i get a faint vertical black shade when moving the head rather swiftly from right to left, and it disappeared at around -40%. Although in some jets i am not using it (i think every adjustment will have to be computed somehow, so... cpu frametime), but in some crafts, maybe Apache included, the shaking is more profound than in others. but... i didn't know zoom works in VR... i have zoom key bound to the slider on my hotas and it never did anything... how do you use zoom in your VR setup?

was waiting for quest pro posts to pop up, because i have also one, and most guides are quest 2... I do have some weird settings now that work for me (so it is not recommendation, just sharing): Oculus app set at 72Hz, with resolution slider all the way left (!) at 0.8, then I use Oculus Tray tool and have set up a profile for DCS with Super Sampling 2.35 (may go to 2.25), which gives me a 0.8*2.25 = 1.8. ASW Mode 45Hz, Adaptive GPU ON, CPU Priority High. Oculus Tray Tool Quest Link Settings Distortion Curvature LOW, Encode Resolution 3664, Encode Bitrate 350, Sharpening Enabled. OTT Game Settings (this one is not in the game profiles) OVR Server Priority REALTIME. In the OTT Profiles main page also Desktop Resolution 800x600. In-game DCS settings textures all high, visibility high, clouds ultra, water medium, shadows high, terrain shadows flat only, MSAA 2x (that bothers me the most...), but trees, grass/clutter, all the way up, even civilian traffic on (medium i think, i like a little movement on the ground), preload radius 100, global cockpit illumination OFF, Anisotropic Filtering 16x. Also Rebar enabled in BIOS and in NVIDIA Profile Inspector, although i haven't noticed any difference. Big game changer for me was disabling Hyperthreading and Intel Adaptive Thermal Boost (Intel Boost and Intel Boost Technology 3.0 enabled). I have now a very smooth experience in Caucasus, and even with a Helicopter like KA-50 or the Huey flying over city-scapes in Syria works at those high settings. A fly-over with F18 over Mariana's gives heavy stutters, but I think here I will go down with textures and turn off shadows for game-play. As mentioned, my gripe is that I can't get smooth experience with MSAA 4x, as it does look considerably better. Ah, in game OpenVR Toolkit: NIS enabled but at 100%, Turbo ON/OFF depending on situation.

that is what i thought too, however my experience is a very discernible difference when yanking up the memory clock +1900 in terms of having less frame drops. no benchmark evidence, so it may or may not work for others. DCS never uses it efficiently anyway, mine doesn't even hit much higher than 61 degrees, and max. mid-80s utilization. And my DCS graphics settings are nearly all the way up (except shadows, which are high for cockpit, flat only on terrain).

As others have noted, DCS doesn't like GPU overclocking too much. Core Clock OC does little and above a certain value it creates white dots in the sky, if too high DCS CODs. I can get my 4090 overclocked stable without the dots by +104. Voltage slider also +100. However, I played with the Memory Clock slider and all the way at +2000 I have much stabler fps and far less micro stutters. Then DCS CODs. But it's stable for me at +1900. I make sense of it, as DCS is VRAM hungry, highest GPU Memory Clock values will probably give stabler frames. 11900KF, All Core 5.3GHz, 240mm water cooled MSI Coreliquid V2, VCore adaptive -0.090mV, 4090 Ventus 3x

My understanding is that the aggravated artefacting is a current known bug and being worked on, though.

interestingly, with native OpenXR I now get better results with OXTK Turbo On with ASW 45, or Auto/Adaptive, but not with 45 forced (stutters/no smooth movement)... quite different than before. Which is strange, because OXTK says Turbo On "disables" ASW... no cpu overheating issue with rebar? or at least observed hotter cpu? ...

had previously posted in 4090 thread on the matter. I just tried it again with rebar enabled and nvidiaprofileinspector rBar - Feature enabled, rBar - 0x00000001 (profile description says "Battlefield, etc." and rBar - Size Limit also... it definitely does something, GPU ms went over 15ms (from previously 0 to 9ms) and all artefacts I had observed prior disappeared (especially visible in external view F3, when the plan flies towards you) however, heavy stuttering especially when looking to right or left (loss of smooth motion). Then I wondered whether i should change something in OTT (e.g. modfiy "Default ASW Mode" to something different than 45Hz forced), but then my PC crashed and rebooted --- either overheating (which I believe i had observed earlier, hence my post in the 4090 thread) or because under such load, CPU couldn't handle my slight undervolting values in ThrottleStop... might also be that my prebuilt MSI MEG Infinite XTE just can't handle it, even though I swapped to a 1000w MSI PSU and 64GB Corsair RAM... Definitely worth a few more tries with Rebar enabled, thought. Will remove undervolt and try to play with OTT or OXRTK as long as my gear allows. If it crashes then again its most likely due to overheating (stock water cooler... yikes)...

rebar on created massive stuttering on my end. might be cpu overheating though. I disabled rebar, hyperthreading and intel adaptive boost technology in bios (MSI Z590) and it has been smooth since then.

Turning off hyper threading in bios was the solution for me. -> difference like night and day Also turned off Intel Adaptive Boost Technology in bios.