RealDCSpilot

@Pikey Shaders are rebuild during loading, when dcs is started or loading a scenario.

I also see no performance gain from the VR shader mod. It may have some effect on lower end systems, but on my end i only see that NVG peeking feature as useful. I have my doubts about how this black mask rendering makes any sense, because if it's added later in the pipeline, those covered pixels are rendered anyway and turned into black in an additional step. What has an effect on FPS is Nvidia driver settings and turning DCS settings down, like he did in the video. But that doesn't help with how AI units tank performance afterwards.

On my side it's not the shaders, it's AI units. They pull to much CPU frametime. In an empty map, FPS are normal. The VR shader mod didn't change anything at all. Maybe it works for lower end systems, or is just a placebo and lowering game settings does the real job in those cases.

If you are testing FPS, try a free flight in an empty map first (with mission editor). Check FPS and then try a mission with AI units.

I just tested a simple scene in the editor, 20 Bf 109's on a turning point besides the airport and me starting from the runway in a christen eagle. Framerate was tanked right from the beginning, simulation value was extremely high (around 80) frametime also extremely high (around 70). When i left the area and was around 10 miles away, the frametimes started to get better but still to high to hold 45 fps (30 fps, VR with forced motion smoothing).

Thanks to Knock-Knock, this shows the problem at best: https://forums.eagle.ru/showpost.php?p=4238222&postcount=188

The number of objects, my hyperintelligent friend...

Thanks to Minsky https://forums.eagle.ru/showthread.php?t=265686 for making USSR_Rik aware. Minsky's info is much better, in his screenshots you can see low drawcalls vs. an increase of "Simulation".

Hmmm, i'm running an i9 10920X with hyperthreading disabled (12 real cores). After watching DCS's load on the CPU i used process lasso to restrict DCS affinity on these 3 cores. Later i used the extended FPS view in DCS to see whats going on in the "Main:" line, which lead me to the conclusion that the value behind "Simulation" maybe the source of the problem. So i came to the conclusion, that something that is calculated on the main thread is increasing CPU frametime making the GPU wait by taking too long. So there is definitely no more cost on the GPU (indicated by low usage). @Worrazen ??? In the multiple testing sessions i used the Huey to circle around those parked planes and then turned away from them to watch the FPS go up again as soon they are out of my FOV. I even build a replica in the mission editor to see the same happening on the other 3 maps as well. However, it's not my job to analyse deeply whats going on there. The info should be enough for ED to know where to look for.

@(504)Blade i'm currently back on 2.5.5 and face the same problem, but it tanks performance not as hard as 2.5.6. In 2.5.5 fps drop from 45 to 30 which is already extreme, in 2.5.6 it drops from 45 to ~20. When i look at the built-in FPS counter, the Simulation value of the main thread seems to be related to the fps drops. Might be a calculation that is taking too long and slowing down the CPU. My GPU usage shows that there is still headroom for more work, but the CPU is unable to deliver in time.

@-0303- Holy ... much respect for bringing a C-64 to battle! ;)

The more concerning value on all these screenshots is "Simulation" on the main thread. In my tests this value has the biggest impact on framerate. Sometimes it's crazy going up and down, what is this? Physics calculations?

There is definitely something wrong with AI units, the CPU might be doing extra or doubled but unnecessary calculations. Or it's a deep implemented, but bad concept of code in DCS.

I just tested recreating the same scenario in the mission editor. Just put some groups of AI units on an airflied and visit them after that.

Made no difference on my end. By the way, image sharpening does not work in the HMD it only affects what is displayed on the monitor. Texture filtering to high performance instead of high quality can free some extra frames and VR prerendered frames to higher than 1 may help reducing reprojection artifacts (motion smoothing etc.).

I have a pretty beefy machine and can run DCS at insanely high settings in VR, i can hold stable 45 fps without problems in OB 2.5.5 or 2.5.6 ... The only reason for heavy performance drops on my end are AI objects in vicinity, it's not the new shaders or eye candy. Modern GPU's (1080 - 2080ti) eat pixelshaders for breakfast, so it's definitely not the "new lighting". Please ED, focus all of your optimization at this particular matter! It's been there for years and slashes back everytime! There is no mission or campaign i can play in this state. In 2.5.6 my fps drop from 45 to 20 in the same scenario. Check those screenshots (made in 2.5.5 latest OB)

@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.