Charly314159

Nice to hear, so maybe in 3-4 months we will be back at the level of performance we had at the beginning of the year....

I have made that decision as well. I have never been complaining for the 3 years that I played DCS but since the f16 release and this 2.5.6 things have taken a terrible direction. DCS now looks like a ponzi scheme feeding on future promises that might never get correctly delivered. Buying EA means accepting that system.

OK so they basically integrated part of keygetis vr shader mod which has been around for 2 years and didn't fix anything in their core... So for people who couldn't afford MSAA because of the awful 2.5.6 performance this update won't change anything...

Honesty, I am not asking for more than 45fps which used to work like a charm on 2.5.5 with much higher settings. 2.5.6 is constantly dropping below asw threshold regardless of the setting and optimization which makes it nauseating and instantly destroys the immersion for me.

Please, I have been struggling with DCS for 4 months, trying any possible solution and testing several freeflights and custom made missions. Performance has dropped by at least 20% from 2.5.5. period AI just makes things worse.

Good for you. We've just been lying for 4 months here.

At this rate the sim might be dead before it happens...

I really cannot see the General "game performance increased" annouced, I'm sorry. still unplayable for most VR user regardless the hardware. 4 months of this and you still won't fix the origin of this 2.5.6 carnage. Again people don't care about the lightning if it's to get a slideshow. I didn't even took the time to try SC more than 10min, I am too disgusted.

20 to 30 FPS on a the SC with a i7-6700k a 1080ti 32gb of ram and a HP reverb with 0.8 PD and every settings to the lowest. Unusable for VR. I got 45fps locked on 2.5.5. Thanks for the "General game performance increased" awaited for 4 months. This is a joke.

How is performance ?

It bas been a long time since I used the rift but you definitively can turn off asw in dcs. I am not sure if I managed it through the occulus tray tool or using the CTRL+0~4 keys inside DCS

I understand BIGNEWY. My point is just that with proper code management devs should have been able to narrow it down on the problematic portion of the code much quicker. The fact that the performance improvement you are talking about (due to AI pathfinding) was pointed out by the community is a clear demonstration of that.

Because they have no idea on how to fix it. Maybe it would have been easier to do after the first 2.5.6 updates had they considered seriously all the report about poor performance. But now we are 3 months later with 4 or 6 updates on top of a broken version. I am not optimistic

You can see your margin with regard to the 45fps threshold by turning off ASW altogether. I bet you lost fps from 2.5.5 of course it is not an immediate issue for you since you still get your 45fps but it reduces your margin and it might become problematic when ED decides to update something else...:music_whistling:

Sorry but NO. We are definitively not at 2.5.5 level of performance. With your configuration you are back above the threshold required for ASW to kick in but I am sure you had more margin before. I am using the HP reverb and have to lower pixel density from 1.3 to 1 to have it run decently (still not perfecr) so I guess that's the kind of performance drop we are still suffering from.

Because stable is almost impossible to use for multiplayer. 2.5.6 is tearing appart communities. Sad...

Of course , that's because ED needs to keep money flowing. Finishing modules or updating core do not induce short term income unlike pre-releasing new shiny modules for us simheads. But because of all the things that have been hidden under the carpet we are probably witnessing the end of that model.

No problem with that if we can avoid catastrophic updates like 2.5.6. Of course it could still happen but in this case you should consider reverting back to the last working version and try to understand what happened internally instead of adding features without patching the issues. It's not like you don't have side effects on your core code.

What I don't understand is why you still haven't reverted the problematic aspects of your code back to their 2.5.5's state since you still haven't fully figured what is causing the problem. You are slowly pushing out of the OB program people suffering from this performance issue. Alienating testers is not an efficient way to progress.

You're right it has only be three months so why should we worry..

My priority is performance improvement since I won't be able to use any of these features if we stay at 2.5.6 level of performance. Sadly it's not listed

I dont see the point of people reporting in every post that they don't have performance issues. I don't even understand why you are here if you don't have any problem. Do you think we are lying ? Some of us, including myself, have been unable to play DCS for 3 months now and I still don't see the end of the tunnel. And please don't start talking about stable, you know very well it is not an option for MP. Loosing 20 to 30% performance in VR from 2.5.5 is unacceptable period. Maybe it could have been if we had gotten the promised 50% boost...

Even if it cannot be said that ED is not delivering (DCS is really an amazing tool), it is difficult not to notice the difficulties they are facing because of the business model they have chosen. Because ED only gets money from modules and because DCS is and will always be a niche product, there is a need for them to keep releasing modules to keep the company going. That could probably be fine with more sales but the issue here is that it is probably unsufficient to have enough budget and manpower leftovers to fix the core issues that have been accumulating over years. The difficulty now is that the core issues seems to impact more and more module implementation in the sim and that the higher and higher hardware requirements probably turns away potential customers and even old customers making things even worse. I am less and less confident about the future if drastic measures are not taken (core rewrite?)

This should have happened weeks ago since it is apparent they have not yet understood what is happening. Instead of that features have been added on the 2.5.6 branch that might be found to be rotten...

Unlikely : https://forums.eagle.ru/showpost.php?p=4298458&postcount=649 I gave up on OB and am back to stable for now...