mmike87

I tried another experiment. I stayed with the latest Varjo Base, but set both registry keys to 0 and also disabled Quad Views in DCS. I then re-enabled OpenXR Toolkit, and enabled Turbo Mode and the fixed foveated rendering. My frame rates seem a little lower ... less time at 90 and more time in the 70-80s... BUT, I swear it seems smoother and there are fewer stutters. To make up for not being able to increase the focal-point resolution like we can with Varjo Foveated, I set the render resolution in DCS to 2.0 ... and then the middle and outer rings of the custom FR in OXRTK to 1/8 and 1/16 respectively. The visual quality still is not as good as with Varjo Foveated, but overall I think the experience seems smoother. Not sure if I will keep it this way ... and I am not even 100% convinced the fixed foveated rendering is working because changing it doesn't seem to change anything visually. I do miss being able to use the post-processing features. Anyway, an interesting experiment.

Out of sheer curiosity, I decided to move to the latest Varjo Base after sticking with the last 3.x version for so long as the 4.x versions seemed to kill performance on the "all-but-abandoned" Aero (thanks, Varjo! You're why I ordered a Somnium VR-1!). I tried the registry settings suggested by the Varjo blog post, uninstalled Varjo-Foveated, and ran my usual Caucuses free-flight route and frame rates and visual quality were noticeably worse. Not sure if I did something incorrectly or not, it's possible. I noticed that the Varjo-Foveated Github suggests not using the tool any longer and going with the Varjo solution - which makes we wonder if I did something wrong given that mbucchia's solution (for me at least, and it seems a lot of folks) still offers the best performance option for Varjo users. Blows my mind that someone who doesn't even work for these companies can still out-do them on the side and for free. Makes me really appreciate Varjo-Foveated and still wonder why no one else can seem to get it right. Procedure I followed: 1) Uninstalled Varjo Foveated 2) Downloaded latest Varjo Base and installed 3) Verified the headset was working correctly 4) Made registry changes as per Varjo blog post 5) Re-started Varjo Base using the option in the app 6) Started DCS 7) Verified that "Quad Views" option in VR was checked (it still was) 8. Started free-flight mission and marveled at the giant step back in performance and quality I un-did everything except the 4.4 Varjo Base install, re-installed Varjo Foveated and all is well again. The only good news is I can at least run the latest Base software, for whatever that is worth given the lack of attention the Aero receives. At least whatever was killing performance on the Aero in earlier 4.x versions seems to have been fixed.

I have tried them all and I think that E gives me the best results. It seemed to have less motion blur.

I assume some of you have tried nvidia driver 560.81, that came out a few days ago? After installing via the Nvidia App and rebooting a couple days ago I noticed my performance in DCS and Cyberpunk 2077 PL was severely degraded. In DCS I was showing severely CPU bound and my frame rate was 45 or less (normally 90 most of the time). My Cyberpunk framerate was cut almost by 2/3. I rolled back and problem solved in both games. Just wondering if anyone experienced anything similar? The latest drivers actually seem pretty popular, especially with the MSFS folks.

Ah, OK - that makes sense. I'll try that. Thanks! What a mess ED has created and allowed to continue ...

I took a leap of faith (big mistake) and installed the new version this morning. Removed all mods, did a clean, etc. Deleted shader folders. Started up Varjo Base, started the game, crash as soon as it tried to enter VR. I am using Varjo Foveated and not Quad Views. I uninstalled VF and the game starts, but I only see the mirror window which tracks with the headset, but there is nothing in the headset of the Varjo Base "headset view". Re-installed VF and back to crashing. The game logs don't show anything obvious, but the VF logs have the "xrEndFrame failed with XR_ERROR_HANDLE_INVALID" entry three times in a row as the last entry. I swear this game is like being in an abusive relationship.

Good grief ... I haven't downloaded the new version yet, comma, and at this point, I may just create a whole nother install. I'm on an Aero but have always used Varjo Foveated, So hopefully it will be fine. Love this game ... But is always three steps forward, two or more steps back with most releases.

To be fair, "early access" DOES imply continued, on-going development. Nothing is settled yet, but I don't think people are being unreasonable to not feel warm and fuzzy about the situation, especially after Razbsm's comments and subsequent lack of attention to their modules. II'm not going to change the clock on my computer. That's ridiculous. The fanboy attitude that somehow this is all okay just because it's "early access" doesn't really make a lot of sense.

My company's old Excel add-in used to get flagged as a virus all the time. It was a false positive, I know as I compiled it myself more than once. I seriously doubt all these modules are "infected".

I thought I saw a slight dip recently as well, but I can't prove it.

Thanks!

I've searched this forum and the web, and found a few that seemed to have been pulled down. I am looking for IRIAF skins for either the AI F-14 or the paid module. I recall there being a skin available for the AI plane at one point (I've created missions with it a while back) but I'll be darned if I can get it to show up in the mission editor. Maybe my search terms are lacking, but if someone has a link to one of these skins, or an idea of why I can't get it to show up in the mission editor, I'd appreciate it. Thanks in advance.

How did you get reShade working in VR? I installed it, selected Dx11 and OpenXr, and reShade opens and works in the mirror window but not in the headset?

I was able to spend more time with this update over the past weekend, and all I can say is, "Wow, what an improvement!" Running a Varjo Aero, 4090, 13900K (hyperthreading disabled, 5.6GHz all cores, undervolted), and 64GB DDR5 6800 and even with this hardware I had intermittent stutters and had to play around with settings to get good, smooth performance. My setup now: Aero at max resolution, locked at 45 FPS with motion smoothing enabled Running Varjo foveated with 1.0/1.4 settings DCS set to 1.4 DLAA enabled NO upscaling Trees, Grass, etc. set at about 3/4 to the right High details on textures Ultra viewing distance Primary and secondary shadows enabled and at high! Clouds and Water set to High SSAO and SSLR enabled nVidia pre-rendered frames set to 1, ultra latency, and the anti-aliasing set to enhance the game settings I limited my FPS to 50 in both the game and nVidia control panel (not sure this is right, but it seems to work great) Vertical syn in-game enabled I experience no frame drops or stuttering, even flying over Beirut on the Syria map. Everything is very smooth and consistent. There is a little ghosting close-up with fast-moving objects, but a little motion blur at speed up close is not unreasonable (or inherently unrealistic IMO). And - with all of this, I am still not GPU-limited at least according to the in-game display. I have bumped up the PPD higher but lowered it as it didn't seem to make much difference over where I have it now. I am still experimenting with how the focus area and peripheral areas with DFR and the in-game PPD (which is applied across the entire image I assume) play with each other. It seems odd to use both ... I would think I could leave the PPD at 1.0 and just adjust the DFR, but I have yet to find a combination that looks as sharp as what I have now. It's fun (I know, I am a bit sick in the head) playing around and experimenting with all the settings. One observation - I have tried Quad-views as I wanted to use The OXRTK to take advantage of the post-processing and FPS display features, however, no matter how I set it up, the performance was worse and the visuals were inferior. I know Varjo Foveated is a simpler configuration, but OOB it looks and performs better. I'd like to find a config for Quad Views that works as well, as I really miss the OXRTK. As far as the FPS limit and vertical sync go, opinions on the web are all over the place on this. But at least for me, right now - the above settings are killing it and are by far the best experience I have had with this game in VR so far.

FYI I tried this today, and copied in the new DLL from the nVidia SDK. I really didn't see a difference in overall quality, BUT with DFR enabled for my Aero, there was an odd, thin horizontal line of "noise" that tracked with my eyes at the bottom of what I assume is the primary focus area. Switched back to the shipping DLL that is part of the DCS install and the issue went away. I was using Varjo Foviated and not Quad Views, FWIW.

I was only able to free-flight for a bit in the F-18 and my initial thoughts are overwhelmingly positive. The F-18 feels different, but I will have to spend some more time with it to re-acclimate myself. As far as performance goes, I spent a lot of time dialing in my settings with my Aero/13900K/4090 and already had a pretty good experience ... but there was always still some micro-stutters sometimes. With this patch, everything seems smoother and more fluid. I will go back to a default config and re-optimize everything around this patch, but so far - the VR performance definitely seems improved!

I have trouble across the board with 6.x ReShade. I was running it with Baldur's Gate 3 and it crashed frequently. Downgrading to the last version 5 works great. I'm not sure 6 is ready for prime time.

I don't believe there is going to be another Aero. They plan on offering the new XR4 to individuals at some point in the near-ish future I believe.

https://www.studioformcreative.com/product-page/varjo-vr-3-xr-3-counter-balance-comfort-kit-200-gram-7oz

I'm also a recent convert, and agree with your assessment. In regards to the vertical FOV ... I really only notice because the DFR is so good. I can't see the transition between the hi and low res areas myself. With the G2 I was so used to moving my whole head, so the FOV was never an issue. Particularly, I'd like more vertical FOV to improve my ability to glance down at the instruments and MFDs just with my eyes. I can do so somewhat ... But to get to the AMPCD on the 18 I still need to move my head to get down that far. For audio, I am using FIFINE "Studio Monitor" headphones ($30) that have a removable cable, and a short, coiled, angled wire, both from Amazon. The combo works great. I also had CTDT on DCS start 50% of the time, even after building a whole new system with the G2. I've not had a single crash with the Aero that was not related to a mod. Definitely invest the $35 in the comfort kit with the strap and counter weights. I could wear it all day. Overall, I'm very pleased. Not perfect, but very good

Has anyone else noticed that this mod seems to break the function of ships (and possibly more) after the latest Open Beta release? For example, if I choose one of the F-18 Carrier Takeoff missions, all the ships are missing and my F-18 just falls into the ocean. If I try and cycle through ships in the external view, all of them are missing from the mission. Disabling this mod solves the issue.

Confirmed... Grippen mod seems to be/the culprit.

You have a 4090? Are you CPU bound? I have a 13900k and a 4090 and get 90 with DLSS on Quality and DFR configured. I adjusted the outer ring down to .7 and the inner ring to I think 1.7. everything is razor sharp and I'm at 90 most of the time, but I leave MS on to handle the drops. I'm at 39 ppd in Varjo Base.

I know everyone's DCS experiences vary widely, but FWIW I simply used OvGME to install this and gave it a quick run. I see what everyone means about the fuselage hardpoint, but it's not a huge deal for a free mod IMO. I haven't had any issues whatsoever so far. I am going to install the liveries next. My assessment after 15 minutes in the air, so far is "nice job" and thanks for all the hard work putting this together!

It's a huge upgrade IMO. Better clarity across most of the view even without DFR, more adjustments for fit, better software, better performance, and no crashes on startup line I had with my G2. The FOV is fine ... IMO comparable to the G2. We can always use more FOV. Audio? I like the option of choosing. I bought the Conquest VR clip-ons and a $30 pair of light headphones with a 3.5mm jack and a $10 coiled short cable with angled connectors. Works great.