darkman222

And if so, that would also have been the case before the update. So what?!

Be sure to learn the basics of the radar like @skywalker22 said. Learn about what the symbols mean you are seeing. And which ones you can actually lock on. A common mistake is seeing a radar contact that comes from data link. But you cant lock it because its too far away, because your own radar cant see it (yet). Or you are scanning the wrong altitude, and thats the reason you cant lock. Or the bandit is jamming your radar. The reasons why thats happening to you in combination are countless.

Add me to this request too. In the end I am not even sure if the manual is really up to date right now.

In short: Same settings in 2.8 compared to 2.7 = Fps loss in 2.8

@BIGNEWYDeinstalled Tacview. Framerate drop is still the same. And no matter what terrain shadow mode I use OFF, Default, Flat. The framerate drop stays comparable.

Dont know if we can do anything about it. Modified LUA files for countermeasures now get flagged for tainted. Even a custom F16 menu theme will get flagged too, which makes no sense to me. How would someone cheat with a modified menu theme?! ED has to change the files that get checked.

@BIGNEWY Sorry for being late with a test of the latest 2.8.0.32235.1 Open Beta. You can see that even without any shadows switched on, with my PC I lose about 2 ms GPU frame time. And a little CPU frame time. I am sure you guys are already investigating in every direction. But the performance drop is still present without any shadows. This is tested with a single F16 over Caucasus and nothing else in the mission to eliminate as much factors as possible. Running a RTX 4090, I 19200KF and Pimax 8KX headset. perf_test_caucasus.miz

Thanks for the heads up. What do the people with Varjo Base Beta do now? Still works fine for me. The beta is 3.7.2.31 and of course wont find an update as the release version is x.13 and not x.31.

Might make sense in your case. But I dont understand why people try to compensate the performance drop. Even MSFS2020 starts to be playable in VR due to optimisations. And it started with really awful frame rates in VR. Number 1 should be performance in a military sim. Also MP performance should be in second place. And there was no worse time for the performance drop than now. Some people purchased an RTX 4090 to get higher frame rates. And a few weeks later 2.8 smashed the performance boost from the new hardware back to 2.7 or even lower.

You can go to where your DCS installation is and run in the command line in that directory: dcs_updater.exe update 2.7.18.30765@openbeta It could look like that: YOURDRIVEHERE:\DCS World\bin>dcs_updater.exe update 2.7.18.30765@openbeta

I dont have this experience with the current Viper, but from what I read and know from other sims that this behavior might be correct and to expect. My feeling is that a Viper standing still until pushing the throttle a good way forward seems to be modeled with a too high force to be ovecome, which keeps the Viper still. I started a thread about it but it died already. Also when the Viper starts rolling, it just does not start to roll, it jumps into a movement instead, which feels like an auto brake mechanism releasing. But who am I to judge...

I was guessing so too. But although the CPU frame time was rising the gpu frame time was rising independently. You can see in my testing Screenshots that the gpu was not bottlenecked by the CPU. There is also something that drove up the gpu demands.

Yeah, some servers run Stable but most of them run open beta and my squad runs open beta servers too. But thats not the discussion here. Lets stay on topic.

Dont want to start a discussion about it here. But the 10% or maybe more percent of VR users are enthousiasts, willing to purchase a lot of DLC and hardware as long as DCS runs smoothly. I personally own at least a total amount of DCS modules of a value of more than 1000$. I dont think a casual 2D flat screen keyboard player spends that much on DCS already. As I already said. I dont care about performance loss in "high" presets. As long as I can be sure that my hardware will still keep performing on "low" settings.

Motion prediction is nice for flying around in MSFS2020. But not for DCS. As it says its just a prediction, on no headset it ever worked in a close air combat dogfight. We need a "performance" mode for DCS and if people like eye candy I am fine with "high visuals" mode. But I am not going to win any dogfight with eyecandy instead of fps. The thing is we have been at high resolutions and high fps together with the RTX 4090. At least I was, for a couple of days with my RTX 4090. That was until the 2.8 update was dropped.

The Viper still performs relatively good. Try the F18 or the F14 instead. Try to check for CPU frame times. Its like 3ms CPU frame times more in the F18 /F14. If I was a regular F18 or F14 player I would have made a report for sure for these airframes.

To keep it together, this is the result from my other PC ( the PC for gaming in 2D) I posted earlier.

@BIGNEWY here are my numbers from my high end gaming pc with a pimax 8kx. Low preset - f16 free flight. Went down from almost 87 fps to 70 fps. These are the specs from that machine. I also posted the results from my "non VR PC " earlier in this thread. Also a comparable amount of fps decrease although not in VR just in 2D only.

Big difference before the 2.8 update yes. Comming from 3090 to 4090.

Yeah. Exactly. RTX 4090 didnt last long until the 2.8 killed its performance. I am not complaining about not be able to play on "high" preset. There is just nothing left I can turn off to go back to the previous smooth performance in VR. Sure, if the "high" preset performs worse after an update, okay. But if the mega "low" preset loses 20 fps thats a no go.

Yep. This is what I am really worried about. Just updated my PC a few weeks ago for a smooth running 2.7. Which was busted with one single update.

And even if its not VR. The frame drop from 2.7 to 2.8 is even in 2D mode. I tried it on my other PC. ( weaker one with "only" a RTX 2070 instead for 2D playing) 2.7 runs in 2D mode with identical settings at 91-108 fps 2.8 runs in 2D with identical settings at 77 fps. That would resemble the 20 fps drop in VR too. 20 fps is a lot, which causes to desync the VR headset. If you play in 2D mode you might not realize the drop at the first glance. 2.8 2.7 Although its "just" a 2070 in that PC the specs of it are decent too.

I am using both. OpenVr / OpenComposite for the Varjo Aero and the regular DCS OB version for the Pimax 8kX. Fps loss on both.

Same for me. Yesterday my high end PC with RTX 4090 was well capable of playing DCS with decent fps now its a stuttery mess. RTX 4090 +i12900 KF Pimax 8KX and Varjo Aero. I already created a thread in the VR subforums about it. ED needs to fix that.

I went back to low on everything. The next thing I can use to compensate is lower the resolution which is a no go for me. I purchased the 4090 for playing in full resolution. And I have been playing in full resolution... BEFORE the update.