Spetz

I ended up setting my IPD in game to the same number from when I calibrated the Rift. The only one that looks out of place is the A10 which just simply looks very wide, but all other air frames look great. I don't fly the Hog much, so not a biggie to adjust as required.

HA!!! Never saw the version # tag there before. And yes, it works quite well in 2.5 :)

Excellent.. Thanks BD!

Yes.. been rereading all the settings regarding this. Will do some more. Regardless, still have a solid 45 in cities and higher up high with 1.6 PD. Thanks for the incite!

via the User CP, top left of the menu bar below the big ol' DCS logo

These are my in game settings. With this I get a pretty much constant 45 FPS going through cities. Seems only the UH-1 and SA342 drop it at times. Textures: HIGH Terrain: HIGH Civ. Traffic: MED Water: HIGH VIS RGE: HIGH Heat Blur: OFF Shadows: FLAT Res: 1280x768 (Because VR) Resolution of Cockpit Displays: 512 (because VR) MSAA: OFF DOF: OFF Lens Effects: Dirt and Flare Deferred Shading: ON Cluuter/Grass: 500 Trees: 100% Preload: 150000 Chimney Smoke: 4 Gamma: 1.6 AF: OFF Terrain Objects Details: Default Cockpit Global: ON VR Settings PD: 1.6 Nvidia Profile Inspector Settings. I am forcing AF at 16x and using MSAA at 2x. The picture below was from a just before I started using Inpector to force AF and MSAA instead of using ingame settings. Runs, IMHO, much smoother this way. Profile says DCS 1.5 but it is for 2.5, just reattached DCS.exe from 2.5. I'm swapping between using MFAA and MSAA to see if there is a notable difference with VR, so far nothing I can see.

Now that 2.5 is out, I can't to wait start using this again once fixed!

**DELETE PLEASE***

Don't know what my rift IPD is set at, but I messed around with the in game settings. I set my position while looking down at the seat and set it as if my game seat is in the same place as the cockpit seat. Settled at 65 I believe. Before the Mirage cockpit seemed tiny but now looks.. comfortable. Haven't tested the A10 yet, but it usually looks HUGE. I noticed the biggest change was how radio menus and the options page in cockpit look.

Welcome to IFR flying! I don't know if the FC3 aircraft have the ability to vary cockpit lighting like other modules. Try increasing the time of day by 30 minutes at a time until you find something you find manageable.

Had the same issue for a few versions now. I just ignore it mostly now.

Here's my settings. so far so good, but will do some more testing. https://forums.eagle.ru/showpost.php?p=3373700&postcount=7

Hmmm.. Any way to remove the Mirage sunvisor data and add it to the Sa342 in the short term? Would be nice if Polychop acknowledged this..

What a change! Reloaded the metashaders, set graphics options, threw on the rift and made an early morning winter mission with overcast skies in the Mirage. It finally (IMHO) looks life-like in the Caucasus region! The street lights, rolling hills, tiny rivers and streams flanked by trees, runways, water and waves.... Looks amazing and for me runs ssoo smooth. Love it! I think all my missions will be winter oriented for awhile!

If you have an Nvidia card, use Profile Inspector and use MFAA instead of MSAA. Works great. Have 16x AF set in game and 2x (or 4x) MFAA. Looks great and minor FPS loss.

These are my in game settings. With this I get a constant 45 FPS. Only dropped twice, both with the UH-1 and SA342 flying through the cities. Dropped to high 30's for a few seconds: Textures: HIGH Terrain: HIGH Civ. Traffic: MED Water: HIGH VIS RGE: HIGH Heat Blur: OFF Shadows: HIGH Res: 1280x768 (Because VR) Resolution of Cockpit Displays: 1024 MSAA: OFF DOF: OFF Lens Effects: Dirt and Flare Deferred Shading: ON Cluuter/Grass: 0 Trees: 100% Preload: 150000 Chimney Smoke: 4 Gamma: 1.7 AF: 16x Terrain Objects Details: Default Cockpit Global: ON VR Settings PD: 1.6 Nvidia Profile Inspector Settings. I am using MFAA at 4x. Sorry if it's hard to see, screen shots suck on a 4k monitor when trying to increase size. Profile says DCS 1.5 but it is for 2.5, just reattached DCS.exe from the new install yesterday.

Beslan was a weird one for me too. I think I tried "Bez Lhan", but it was more "Bez Lun". Just mimicked how it was said in game via ATC and now it works 100%

Thanks!

do you speak with an accent? I am a native English speaker and I still had issues at first. For example I would want "helo" recognized, but I would have to "hello" instead of "hee-lo" as I would say in Canada. I found going in game and listening to how ATC would say something, then mimicking it in Viacom usually sorted myself. And word training helped too.

Just too bad we won't be able to see it very clear.. come on Pimax 8k!

Can't wait!

Was going to report the same thing. Cheers

Yup.. Only having a single radio to use out of the three..

Like most here, I run a 1080Ti. Never drop below 45 FPS (have seen 90's up high) using CV1 with pretty much maxed settings except AS off due to the DCS glitch in 1.5 and 2.2. And with SS at 1.6. Normandy sometimes see it drop to the high 30's with the low level fast flying, especially in cities. Get the best you can afford, but I don't think you'll be disappointed with a 1080. But that would be the minimum I would recommend. ***EDIT*** Forgot to change power plan via nvidia control panel back to max performance. Normandy runs much better now :)

Test logs sent Hollywood! Hopefully when this is sorted I'll grab the Chatter plugin so I can have the complete setup at 100%!!!