RealDCSpilot

@fatboy 1. you bind left mouse button, right mouse button and scrollwheel functionality to your HOTAS (UI controls category) 2. you set the HMD to have the mouse pointer fixed in the center of your view 3. from there you just need to look at a button or knob in the cockpit and use those HOTAS bindings to interact with it

In fact, the Index uses also inside-out tracking. The optical sensors on the HMD and the controllers look for the emitted laser fields of the base stations. This offers a higher rate of precision, much more redundancy than SLAM with basic CCD chips and doesn't have the problem of dead angles. That's why you will always find professional HMD's using SteamVR instead of cheaper "inside-out" tracking.

I hope they don't bring that back, even it's hilarious but stupid.

Searchlight for targeting at night!? At what range please? :doh: What is that, a tactical searchlight for lining up that Vihkr shots??

The current 2.5.6 open beta has serious performance issues, you may try to convert back to 2.5.5 open beta to get much better frametimes.

Just a reminder, SHKVAL is a TV system and will always be useless at night, unless there is a lightsource near the target (battlefield illumination, fire or full moon etc.). Try the S-8O(M) rockets for illumination, but i haven't tested them lately...

+1000 DCS is so unique, thanks for pushing this forward all the time. Keep it going and alive, you have something very special here.

@Aluminium Donkey check every setting outside of DCS first, settings of your monitor, Windows display settings and driver settings. Looks like something is already messed up there, so DCS will always look wrong without cleaning the other stuff up first.

If gamma is set too low, the sun won't blind you. At 2.2 it has a pretty good blinding effect in combination with lensflare.

Another addition, if you choose to fly the Ka-50 (the oldest and simplest cockpit model) with DCS 2.5.6 in PG for instance, VRAM usage doesn't fill up over 100%. It's still quite high, but doesn't overshoot and performance is ok when flying over Dubai. Every aircraft with the latest and most detailed cockpit fidelity, especially the F-16, leads to VRAM overflow and tremendous performance hits.

FFB is still working with G940 base in DCS 2.5.6.

Guys, check your VRAM usage, this might be the source of the performance issues. I hope ED can fix this quickly.

Yep, i can confirm. VRAM usage is going nuts once you are in the cockpit. Even a 2080ti hasn't enough VRAM to tackle this.

@Gryzor Congrats! I think you found it! I just checked my VRAM usage and it is totally out of control. Even a 2080ti doesn't have the belly for it. So a VRAM memory leak is causing all the troubles...

Interesting find, might be worth looking into it for ED.

@petsild Did some more tests, you were right. Water quality on high switches those SSLR reflections on. I tried medium and they were gone. Then i tried SSLR ON, but those reflections didn't come back. So now i wonder what does the new SSLR mean? What other reflection effects are rendered with this option? One the other side i found out that water quality on HIGH doesn't have an impact on performance, so SSLR on water does a pretty good job now. First i thought that this could be the culprit of the performance problems of 2.5.6 ... Back to square one.

I just found out how to do this. I thought this was controlled by the new SSLR option, but instead it's controlled by the water quality setting. Try medium and the reflections are gone.

As a sidenote, i disabled the secondaries of the lensflare in the lensflare.fx shader (which should be a mandatory option for VR!). This doesn't affect the issue. Visually i can see no difference between SSLR on or off. Only that the SSLR effect of 2.5.6 looks much more detailed and clean than in 2.5.5. And well, there is the huge performance hit... @petsild this may lead in the right direction, so water quality on the highest setting forces SSLR always on? However, i can clearly see the difference in details from the former implementation of SSLR (2.5.5)...

And here the log files. Logs.rar

Here are screenshots...

Try setting Gamma to a value between 1.8 and 2.2. At 1.0 all lighting, especially with a VR HMD will be unrealistic darkened. DCS uses High-dynamic-range rendering for lighting which opens up the bandwidth for colors, contrasts etc. check https://en.wikipedia.org/wiki/High-dynamic-range_rendering. There is a simple check for realism, fly at high noon and clear sky, if you can easily look directly into the sun and clearly see it's round shape your gamma is set too low. Think of what happens if you do this in reality, you will burn your retina. If the sun blinds you with a huge glow, you are close to a realistic value.

For me only the F-16 seems to have serious performance issues, other modules seem to work better.

Besides that... The new lighting looks absolutely incredible. So far i only have serious performance issues in the F-16, other modules seem to work better. I absolutely love the new dynamic cockpit lighting and how much nighttime lighting has improved!

...regardless of what i set in system settings. Those reflections (buildings, trees etc.) on water surfaces are always there.

and finally: https://sendvid.com/2fx0z4oc