Sr.

This is actually working. Long story short, it allows you (me anyway) to run SteamVR SS at 100 and MSAA 4x with no frametime loss. https://forums.mudspike.com/t/openvr-fsr/12743 borrowed from another poster My current config file: { "fsr": { // enable AMD FidelityFX Super Resolution "enabled": true, // Per-dimension render scale. If <1, will lower the game's render resolution // accordingly and afterwards upscale to the "native" resolution set in SteamVR. // If >1, the game will render at its "native" resolution, and afterwards the // image is upscaled to a higher resolution as per the given value. // If =1, effectively disables upsampling, but you'll still get the sharpening stage. // AMD presets: // Ultra Quality => 0.77 // Quality => 0.67 // Balanced => 0.59 // Performance => 0.50 "renderScale": 0.75, // tune sharpness "sharpness": 0.75 } } Worth a look

The PD slider will align the "sweetspot" to you eyes, but staring from a 60 PD myself, I usually slide mine about 61-62 and it's fine. I stop when the 2 centers start to converge. I bet you can get by with 60.

See my post above referring to Speed of Heat's guide. I have applied his 1080ti to my brother's system (also running a 2070) with great results. He's running a Vive Cosmos Elite, so yours should do well with the G2. You might however consider an additional 16GB of RAM. You can get there, it will require some tweaking, shader mods etc. The "blur" you're seeing is likely EDs way of reducing shimmer. This is a great mod for increasing the clarity. Especially great for systems using reduced SS. My current settings: SteamVR SS 80% DCS PD 1.0

What is PD set to under the VR tab on your end? best to start at 1.0 Also, don't confuse DCS "IPD" with actual IPD. In DCS it refers to "world scale" (cockpit size). IPD (inner pupillary distance) is controlled via the button/slider on the G2.

Ah!... thanks!

Curious what commands are used to open some of the other tabs on the kneeboard? I have tried multiples but can't seem to open the AAR, AOCS or REF tabs. Or are they simply not yet implemented?

Have you cleared out the C:\Users\<username>\Saved Games\DCS.openbeta\fxo and metashaders2 folders? Doing so will cause them to be recompiled, and will take "some time". This will need to be done per map and aircraft.

Thanks... I may have actually done it without breaking anything But the day is still young...

Is there a thread available for how to daisy chain with Bailey's. I only just recently started using VA/Vaicom(licensed). Prior to that, I tried Bailey's and hoped the 2 could be used together. Or would it be easier to just find a separate profile to do other tasks like "lower launch bar", "formation lights" or "landing configuration?" I'm really exited to get to using VaicomPro...but man it can be overwhelming.

Same And lately I'm getting solid 45 w/ 15-17 frametime over Syria

Current implementation. I have the rear end of the cable firmly attached to the back part of the frame using thin velcro tape. Add a slight counter clockwise twist and the loop stays vertical and off my head.

Definitely a poor design. At least where the cable port plugs in to the headset. Just the action of unhinging the head "strap" causes a 90-90+ degree bend in the cable at that point. Done several times a day over the course of several weeks, few cables could stand that kind of bend radius and fatigue.

I put Digital Combat Simulator in all 3 boxes

Just under a month. Got my new cable today

whew... I thought I had broken something, again

Start here: He also has a link for 1080ti (what I used to run). My brother has a 2070S and his looks great on a Vive Cosmos Elite (with lens mods even better)

Man! I've had nothing but crashing trying to use the Radeon software. Seems no matter what preset I try to use, it will eventually crash with some message referencing "Wattman". While DCS itself wouldn't crash, it would crash WMR, another game I play (Rocket League) and even Chrome would stop while simply reading a page or watching youtube. Often, a black screen, complete restart crash or blue screen with "IRQL_NOT_LESS_OR_EQUAL". I have since done a clean uninstall/re-install of the DRIVER only and now use MSI Afterburner to control fans, clock speeds etc. No more crashing. Welp... turns out I actually had a RAM configuration this new motherboard doesn't support. I had 4x16 DDR4 2666 running at 3600 XMP. After several mem test failures and cross checking the ASRock compatibility list, I'm back to 2x16 DDR4 same XMP profile. I think I still prefer using MSI Afterburner to handle the OC, fans etc.

I will say, there appears to be LESS horizontal jaggy-ness in the distant clouds where they meet the horizon and against hill tops.(standard and high presets). Ultra look great, but come at a performance hit of 4-6 ms in frametime. VR specifically

Agreed. Even the new one is still too cartoony for me.

Any idea why I had to redownload 3 aircraft, Supercarrier and 3 terrains? And why are they ending up in these HUGE backup folders? I just finished a complete redownload/install 5 days ago.

Whatchu talk'n bout Willis?

Works for me now... after the redo I've been through lol

At first launch they were not "listed" in the game menu. But under the module manager, they were listed as "let's install some modules" or something to that effect. At that point I exited, and copied them over from backup, restarted DCS and they were listed where expected, and under module manager the were now shown as installed. The only thing appearing to be "broken" was the Caucuses map. Which prompted the repair install. The repair install then removed (moved to backup) everything I had restored from backup.

Lately I've been fighting multiple issues attempting a DCS cleanup/repair install. The repair would run for hours only to fail with an error "Inflate (-3) incorrect data check". Contacted support and they advised it was my Antivirus...ok, but I already had the usual folders excluded, and several other attempts I had real time & cloud protection disabled. Still no joy. Eventually, I decided maybe it was time for a wipe/reload, windows, DCS, the works. Backed up my saved games and DCS install folder. Spent all of last night and into this morning doing a fresh install of DCS open beta. Rather than re-download my modules, I restored them from my previous backed up installation. Opened the game, everything seems to be there... except the textures in Caucuses are jacked up... bright magenta, pink & green pixels on most buildings... SO... once again, I run a repair install. Once it completes it reports that everything I had moved over from backup aren't "part of the vanilla install" and removes them. Is this going to be the behavior any time I need to do a simple "file integrity check?" I am logged in at start up. How does the game engine not know which modules I am "allowed" to have installed?

Strange . Assuming 21H1 plus all patches? Yep. Just completing a complete wipe/reload... had some other issues and figured it was just time.