MHAce75

i meant from not using any preset (and staying on stock DLSS dll) to J or K... before doing any of this, I was CPU bound, now I am GPU bound by a great deal. I am not complaining, smoothness is still there, I was just wondering whether this is expected behavior BTW, does anybody of you dabble with VR pre-rendered frames in NVIDIA settings (e.g. 1, or 2?)

plenty on DCS official site under "download/user files"

is it expected that with swapping to DLAA 4 and choosing Preset J situation switches from CPU bound to GPU bound (by a great deal...)?... no super discernable performance degradation but neither huge visual improvements, but like to work with the latest stuff always.

with a 4090 i am mostly CPU bound, i9-11900KF a bit dated already, sadly.

how? going offline, i only see the frogfoot and unarmed Mustang variant... user-made/free-mods perhaps... Or am I missing something?

The thread doesn't seem to be in the right section, as this section deals with VR issues. Staying in online mode, a reboot and restarting DCS should fix the issue, pending you have a working internet connection. Otherwise, try a slow repair with DCS Updater Utility. DCS offline play is limited to 2 planes that come with the initial installation.

oic.

Interesting finding. I set OXRTK to safe mode, and after I installed Meta-Foveated I see the OXRTK in both eyes.

DFR = meta-foveated from mbucchia?

Yes that's why I asked. I try to have the least SS beyond Oculus settings as possible (such as in OTT etc). My primary purpose was to check whether people are rather using 72hz or 90hz in Oculus desktop settings and I got my answers. Thanks

Ok. Maybe my bad, 10000 miles away from home ... so the max value for 72hz is 1.3 in Oculus desktop app? Then I stand corrected . Thanks

Ok. Maybe I am thinking about something else. I only use Oculus desktop app (at 72hz 1.7, or at 90hz 1.5 (I may have reversed the values I am not near my PC these days) and started to leave OTT SS default. I actually do not know, what "in Meta" means :-)). I assumed you meant the Oculus desktop app, which at 72hz allows values higher than 1.3, or am I mistaken? I mean this 90hz max 1.5 72hz I think max 1.7 (I think) (Yes it shows Quest 2, I grabbed from the internet to show what I mean. The menu looks the same in Oculus desktop app for QP)

Thanks I will try it out this weekend! One question back, you run 1.3 in Meta and 1.15 in OTT = 1.45. why not just run 1.5 in Meta and OTT default?

Currently abroad can't test latest updates and meta-foveated until Saturday, so I am doing some pre-thinking. Rig with 11900kf, 5.1Ghz, 4090, 32 RAM. What has plagued me since the beginning of time, nevermind 72, 80, 90hz, that it is for me unplayable without AWS forced 45 + Turbo Mode, but then AWS forced introduces heavy ghosting, which is especially annoying when dogfighting. What are my best chances to remove ghosting? Going to 72hz (1.5), AWS off, if meta-foveating works for me, or staying at 90hz (1.7), AWS off, if meta-foveating works, and dialing down DCS graphics settings? 90hz looks and feels better, but is it too taxing for my CPU?

Yes. If introduced heavy audio stuttering and more motion interruption here too. For audio I went back to other BT headset to alleviate the audio issues

frame rate in Oculus is for both eyes (72, 80, 90), ODT/OTT for each eye (18, 30, 45), OXRTK framerate target and limiter is again for both eyes.

are you using the OpenXR Toolkit and have set framerate limit? set max framerate in Nvidia settings?

once again this forum is proving helpful. I didn't know what LOD negative bias was and why it was recommended CLAMP. I had set it to Allow, and then noticed excessive shimmering, but I didn't connect the dots... until this post... well, to my experience shimmering can never be eradicated in DCS VR, can only be minimized with the setting above, high PD, MSAA 4x and clouds Ultra, which in this combination needs a very strong rig... even then, still some shimmering (aliasing)

11900kf and 4090 Ventus 3x here, i have come to the conclusion that I can only tolerate 72/36 with AWS on (OTT 45hz), with relatively high settings (PD 1.55, MSAA 4x, etc.) and because of AWS on, 45hz, I have to live with ghosting. with ASW off i have unbearable ground stuttering, unless I reduce PD and/or DCS settings. The ghosting bothers me little in cockpit, only annoyance is chasing a plane which will look like a biplane, due to the ghosting (best example, P51 quick mission Caucasus Dogfight vs. FW109D.

this never works for me (oculus on 90hz with AWS off), no ghosting whatsoever, but steady stutter of buildings and trees beyond my acceptance level (one could argue it is a fly-by blur, but it is more disturbing than pleasant). Even though my rig is pretty strong, 11900kf 5.3ghz, undervolted (no overheating, MSI coreliqued water cooled, idle at 38 degrees, with DCS rarely over 80 degrees) and max pl1, pl2, and pl4 so no power limit either + nvidia 4090. I ultimately went back to 72hz, oculus slider 1.5 and ott ss 1.2 (max was 1.35 which gives a super crisp picture, but occasional stutters), nvidia frame rate capped at 72, AWS on 45hz (not forced, just 45). Very smooth with beautiful graphics almost maxed out (except terrain shadows, off), but of course depending on the situation, subtle to profound ghosting, which is a bit annoying when chasing a plane in WWII dogfights, but I can deal with that better than with the aforementioned. on heavier maps like syria and marianas, etc., the occasional stutters are more often, but then I can scale down some graphics to make them work. Work very well with Huey fly-over Syria city-scape, real fun to hover and race around the buildings.

Only terrain shadows or cockpit also?

i think the problem is that the software interprets tiny/minute movements as in one or the other directions, resulting in a shaking simulation, making it difficult to focus on cockpit instruments. in reality eyes and brain will compensate shaking and the picture we see will remain stable. I found the cockpit shaking is more profound for some aircraft. I recently installed an additional module - i believe it was the Huey helicopter - where the cockpit shook unbearably and also unrealistically, so the shaking reduction to -40% helped with it a lot

mh, cockpit shadows high work for me (not secondary shadows though). terrain shadows i have off too. well, that is in caucasus and less populated areas of syria, nevada, channel, but of course in marianas i have all shadows off, that is a different story though.

that's it. i tried with -100% again, it is quite pronounced, all down to -50% i have that faintly still, at -40% its ok, and that is where i have settled now.

thanks! i will check that out.