mmike87

I can't see past 24 inches in real life. Everything is clear in the headset other than the fact that I can't get the eye track to to work with whatever my prescription is. Im just nearsighted.

I've been unsuccessful with eye tracking from day one. Calibrations, if I could get them to succeed at all, sometimes took 15 or 20 iterations. Once in game, the performance was terrible and often the eye tracking was jumping all over the place randomly without me changing my gaze. After many hours of troubleshooting with the latest beta 4, I think I found the culprit. My contact lense prescription. I didn't have any issues with eye tracking and my contacts with my Aero. At first I thought it was my multi-focal contacts. Nope, tried a regular fixed-focal set, same result. And, everything was blurry with the fixed focal contacts. Removed contacts entirely. Everything nice and clear. Eye tracking calubrated first try. VR Ootician's web site for prescription inserts states that they "adjust your prescription to be compatible with the VR1." I'm guessing the focal length or whatnot for the VR1 is very short because without any prescription I can't see anything clearly past 24 inches. I had no issues with tracking or clarity with the Aero. But, once calibrated, removing the headset and putting it back on resulted in the crazy, random tracking that basically makes the view seem like it's flickering. I confirmed with the once-again enabled heat map.

Has anyone achieved decent performance and visual quality with the VR-1? I've had mine a week or so, and the only way I can have a good experience is using the Steam VR runtime with OXRTK fixed foveated rendering. Even then I'm locked at 45fps with motion smoothing. I was getting 90 most of the time with my Aero, and it would seamlessly transition to 45 with MS. With Dlss 4, the Aero was working great. If only it had a better FOV. The image is fantastic, bright, great fov. But when dialed up to look as good as the Aero, the performance is a low FPS, stuttery mess. I realize for the wider field of view will have to be some compromises, but I wasn't expecting this level of image quality loss just to achieve a decent frame rate. To get 90 fps you basically have to dial it down to where the instrumentation is unreadable. 4090/13900k/64gb DDR 6800

I had a similar experience. I rolled back to the Cuda SDK development drivers that also fully support DLSS 4. I've had zero issues with those drivers, despite being non-release drivers.

So far, so good. Here are my specs and settings FWIW: 13900K, HT off, 5.6GHz all P-cores, .090mv undervolt 64GB DDR5 6800 Gigabyte Gaming OC 4090, +25 core clock, +1025 memory over factory All system temps way below the threshold when playing DCS Varo Aero, running 35ppd, OpenXR, Automatic Vertical Sync with Motion Smoothing to "always on" Varjo Foveated with 1.3/0.80 with vertical and horizontal scale set to 1.2 and Turbo Mode to ON Latest DLSS 4 DLL installed via DLSS Swap Resizable BAR and DLSS profile "K" set in Nvidia profile inspector HAGS enabled in Windows 11 Prod VR pixel density in DCS at default 1.0 These are my DCS settings. This is while playing multiplayer with no mods. One of the mods I use in single player is supposed to reduce shadow impact, but at this point I can't tell any longer. nullnullAnti-Aliasing = DLAA Upscaling = DLSS DLSS Quality = Quality Sharpening = 0.30 All textures = "high" Shadows = "low" Flat Shadow Blur = ON Secondary Shadows = ON SSS = ON Visibility Range = HIGH Civilian Traffic = OFF Water = HIGH Clouds = HIGH SSAO and SSLR = OFF Lens effects, Heat Blur, Motion Blur, DOF = OFF Volumetric Lights = ON Anisotropic Filtering = ON, 16x Terrain Object Shadows = DEFAULT Global Cockpit Illumination = OFF Rain Droplets = LOW Vsync = OFF Full Screen = OFF With the above setup, provided something doesn't set my max power on the 4090 to 30% behind my back, is the overall smoothest and clearest DCS experience I have ever had so far. Stuttering is rare ... maybe a little if a whole bunch of stuff comes into view suddenly, such as when turning head to side quickly, but it's rare now. DLSS 4 seemed to have really helped with the ghosting, which was previously TERRIBLE - especially when the Aero dropped to 45 hz and when full-on motion smoothing. With the above, now with DLSS 4 I stay at 90 hz most of the time, and even at 45 the ghosting is there, but noticeably less and bearable. Some observations: With the above, setting the Aero to its "39 PPD" setting (which I think is simply a build-in supersample) I don't notice any difference in image quality, but performance seems to be a little worse but is still very good My overall performance is better with DLSS 4 ... I am at 90FPS a lot more, even flying low cities in the Persian Gulf or Siani. Syria is of course worse, but still a lot better than before. Varjo Foveated "Turbo Mode" really helps, and IMO that software still provides the best overall combination of clarity and performance. I just wish I could use OpenXR Toolkit to play around with the post-processing. The Quad Views application IMO performs worse and looks worse than Varjo Foveated. God help me if it ever stops working. I have a Somnium VR-1 ordered and hopefully will have it in a couple of weeks. Anxious to see how that all performs. I am 100% satisfied with the Aero's visual clarity even after all this time, I just wish they didn't abandon the product and had actually implemented local dimming, which is coming to the VR-1.

I think i figured out my issues ... the drivers, DLSS, etc. were all red herrings ... I finally opened up MSI Afterburner that I use to apply a small core OC and the typical, 1000+ 4090 memory clock and I noticed my power limit was set at like 35%!!!!!!!!!!!!! Not sure how this happened ... I have not even opened Afterburner in months. I think that all the nVidia App's "optimization" crap did something since it seemed to default to "on". I removed the nVidia App and will just use the profile inspector and the trusty nVidia Control Panel for as long as I can. After restoring my power limit to 105%, I am smooth as silk again in Profile K. Someone asked me for my settings - I will play a bit and make sure it's all kosher and then post what I use.

Well, it just so happens that everything I said was wrong. The driver update was NOT the cause of the huge performance drop ... as the next time I played, even with the Dev drivers, the issue came back. I re-installed the release drivers and was able to get it smooth again. But, the issue came back AGAIN after shutting down and coming back later today to fly some more. I have now uninstalled the nVidia app and I'll see if that helps. I monitored my GPU and CPU when the performance was bad ... and 1 or 2 p-cores were pegged at 100% and the in-game FPS counter was red for CPU render thread. When it's smooth, it's not doing that. I messed with core affinities ... I have Process Lasso sticking the game on P-Cores 0-8 (HT is disabled) on my 13900k. Nothing is throttling ... when the FPS is bad, GPU is 50% or less, CPU package temps are about 52C, and no cores are thermal throttling. Everything else is shut down and what can't be shut down is running on and e-core via PL. I may roll back to the previous DCS release. I have never had this issue before, and I moved to the latest release and DLSS 4 around the same time. It's not DLSS causing the issue, as I can fly with all AA off and the issue persists, until it magically goes away for awhile. I swear this game is like dating a smoking-hot chick who is amazing in bed but occasionally goes nuts and throws things at you. Or, so I hear.

I noticed odd behavior after switching to DLSS 4 and the latest release driver. On my Aero, my framerate seemed stuck at 45-ish instead of 90. I rolled back to the Cuda SDK dev drivers, kept DLSS 4 at setting J, and everything worked great again. I am wondering if it's the new Nvidia App.

If DLSS Tweak still works, you can force an on-screen indicator of sorts. I think there is a registry key that can be set, too. However, in my VR it's tiny and illegible.

I was running DLSS 4 on "quality" and pre-set "J" via profile inspector on my 4090 / Aero ... With the CUDA SDK dev drivers. HANDS DOWN... Best DCS experience in VR I've ever had. Today I installed the official driver update and the new NVIDIA app. My settings were blown away and I had to re-enable the resizable bar and preset J. The NVIDIA app will not let you do it for DCS because it says it's not supported. Start the game and my frame rate was literally cut in half. I don't know if it's the drivers or if the new version of the NVIDIA app is setting something to a non-optimal setting behind the scenes. I re-ran the CUDA SDK install and it wouldn't override the new drivers. So I had to completely manually uninstall them and roll everything back to the CUDA SDK version.I Presto! Nice and smooth, very little ghosting, And I'm running pretty high settings. Has anyone else noticed the difference in performance with the new drivers versus the development drivers? Or it may be the NVIDIA app?

Me too... Everywhere I look. I used to only see it at night flying over urban areas. I'm on an Aero and using Varo Foveated instead of QVFR.

I tried it and it's definitely a step up IMO. Less ghosting and better, clearer visuals. I swear I'm seeing less stutter, too... But that could just be because the planets are in alignment.

I started receiving this error today and saw this post mentioning motion blur. Disabling motion blur cleared the issue for me.

I suffered from horrible "double vision" ghosting on my Aero with a 4090 running "auto" vertical sync which downgrades to 45 from 90 if the game can't generate 90fps. Thus, I also have MR on all the time. The latest DLSS version, pre-set F solved 85% of my ghosting. It's strange, because I've tried it before, and it didn't seem to do any good. So I uninstalled the Varjo Base software, and dynamic-related rendering software (Varjo Foveated), and reinstalled everything from scratch. And since then, my visual quality and smoothness and lack of ghosting have greatly improved. I run with pretty high settings... With DFR at 1.4/1.0 and DLSS on "quality". Sometimes I can tell when it drops out of 90 Hertz and switches to 45, but overall it's been a much improved experience. There are, of course, some occasional stutters which I am convinced at this point have nothing to do with graphics settings. My guess as a 30+ year veteran software engineer with considerable multithreading experience... It's sort sort of thread-synch issue. I have lowered my graphics settings all the way down to the bare minimum and my 64GB DDR5 6800 13900K can still see occasional stuttering.

Interesting. I'll try that tomorrow. I am running pretty high sharpening and the ghosting is terrible no matter how I set up DLSS.

Along the same lines of FR with the OXRTK ... anyone have any idea why, despite having the option available sometimes FFR seems to work and sometimes it just doesn't seem to do anything? I (like many of us) am continually trying to find the magic combo of settings that work best with my 4090 and Varjo Aero. I actually prefer the three-rung, FFR of the OXRTK - especially now that the foveated rendering "box" is clearly visible since the last update (as others have reported as well). Edit: I just figured it out. If I have a pixel density of anything other than 1.0, the OXRTK FFR shows as available, but doesn't seem to actually do anything.

I've been playing with settings for what seems like an eternity. Just like many other folks. I think I finally found a set of settings that seems to work very well for me. Running 13900k 5.6ghz all p cores, undervolted, HT disabled, DCS locked to 8 p-cores with process lasso, 64gb, 4090. DFR enabled. I locked my Varjo Aero at 45 hz, Motion-smoothing enabled. I run PD in-game of 1.7 with pretty high settings all around. With that level of downscaling I can get by not running any anti-aliasing at all. The cockpit is crystal clear and I have little to no stuttering and everything is very smooth. There's still some ghosting with other aircraft at times. I can enable TAA And I don't really notice any performance degradation and it helps with shimmering a little bit and doesn't seem to make the ghosting any worse. The Aero only offers 30, 45 and 90 hz... If it offered 60 like my g2 did I think it would be golden.

I don't really notice a whole lot of difference to be honest. All the DLSS presets have ghosting. I run my Aero locked at 45hz, Moion smoothing engaged, fps limited to 50, DCS pixel density 1.5, Varjo Foveated 1.5/0.7, using the last version of Varjo Base 3.x and I have more or less managed to eliminate all stuttering and everything is smooth as a gravy sandwich. But, the Ghosting of aircraft in particular is still pretty bad no matter which version of DLSS that I use. I ditched the DLSS and anti-losing entirely and then bumped the pixel density up to 1.5. No ghosting, But there is still some shimmering and artifacting. I tried TLAA and that seems to actually have less ghosting?

At some point over the last couple of updates, the behavior of the AIM-9X missile on the F-16 seems to have gotten a little wonky. When engaging targets at a variety of ranges and aspects, about half the time the missile goes crazy and goes off in a random direction in a spiral flight path. Has anyone else observed this? I've fired the missiles previously into the Sun, etc., and had them not track, but I've never seen them go off in a spiral flight path before. Stretch a slinky. And you can visualize the flight path that the missile seems to be taking. I have no idea what is actually realistic for the missile, but a flight path like that would seem kind of odd to me.

And according to today's changelog, it doesn't seem like anything was done with the recent return of severe stuttering. "What stuttering?"

It's hard to tell ... The FPS jumps around a lot No matter what I do since a couple of updates ago. I used to be able to do 90 most of the time, now it's a struggle. I finally settled on using Varjo Foveated with its Turbo Mode, but with eye tracking disabled and both inner and outer zones set to 1. With the Aero set to "highest" PPD, automatic frame rate sync, and motion smoothing to "always" ... I get decent results and that's what I'm settled on for now. They need to figure out WTH is wrong with this game. We seemed to be making nice progress in regards to visual performance since 2.9 came out, but now we've taken a big step back IMO.

I moved away from the tracking and FR in general on my Aero. The eye tracking isn't fast enough and I can see the detail shift, especially at night when looking at a lit urban area. It's terrible. IMO the fixed FR with three zones in OXRTK offers the best FR experience, as the three zones, along with the Aero's large sweet spot mostly prevent me noticing the detail shift. I'm hoping, if my Somnium VR1 ever ships that it's 120hz DFR will be less noticeable in regard the seeing the resolution change as my eyes move.

DCS MT can cause issues with DCS MT ...

I was able to get it to work last night with Quad Views Foveated (it's known to not work with Varjo Foveated) and everything I tried in OXRTK seemed to work, except FR which makes sense given QVF handled FR itself. The performance wasn't great and the visual quality was worse. I went back to Varjo Foveated to refresh my memory, and it still has the best frame rate and overall visual clarity, but still doesn't seem as smooth (despite the lower frame rate) as just using OXRTK without VF or QVF. What I don't think I tried was forcing "stereo" in Varjo Base and then trying OXRTK. Lots of moving parts - it's fun to tinker with - to a point. LOL.

I have been playing around with all the "new" configurations that seem to be available ... and I wanted to try NOT using Varjo Foveated or QVFR so I could go back to using Open XR Toolkit. At one point, the FFR worked, and then I changed something and now it doesn't seem to do anything. I reset OXRTK to default, disabled the Varjo Base registry keys, etc. and nothing I do makes FFR work in OXRTK with my Aero. If I launch DCS with the "Quad Views" box checked, and OXRTK enabled, DCS hangs indefinitely.