DCS World Patch Notes Discussion Thread

[donkeyrider]

Thanks for the timely update.

[speed-of-heat]

my opinion, likely unpopular, one patch a month is frankly enough, so ED keep on holding to your guns and release when its ready ... there is quiet an eco system around DCS, and a patch a month gives everyone a chance to catch up with their mod or scenario or whatever, not to mention deal with changes as players ... which is the point.

[shagrat]

Don't expect anything big or new this week, just expecting to repair the FPS drop in F-18 because of SA. Why should we wait the next week or two weeks. I don't count on anything new, I just want them to fix what we already have. Are these such great desires? Small steps forward, it's important to do them. :)

The SA fps drop seems to improve / is fixed by reverting to a non bugged Nvidia driver (older one, or maybe the brand new fixes it, as well), according to reports on the forum. I never encountered it anyway, as I still run the 435.x, but it seems that fixed it.

[TAW_Blaze]

my opinion, likely unpopular, one patch a month is frankly enough, so ED keep on holding to your guns and release when its ready ... there is quiet an eco system around DCS, and a patch a month gives everyone a chance to catch up with their mod or scenario or whatever, not to mention deal with changes as players ... which is the point.

 

Holding back critical bugfixes for a month despite internally being fixed is nonsensical. Looking at the Viper datalink for example..

[Fang333333]

Holding back critical bugfixes for a month despite internally being fixed is nonsensical. Looking at the Viper datalink for example..

 

+1

[Padonis]

The SA fps drop seems to improve / is fixed by reverting to a non bugged Nvidia driver (older one, or maybe the brand new fixes it, as well), according to reports on the forum. I never encountered it anyway, as I still run the 435.x, but it seems that fixed it.

 

 

Well, but this is not a solution to the problem that has been bothering us for over a month and does not allow you to enjoy the plane.

[speed-of-heat]

Holding back critical bugfixes for a month despite internally being fixed is nonsensical. Looking at the Viper datalink for example..

It all depends on dependencies, packaging and release methodology.

 

We don’t know what hooks, it is dependent on in other parts of the code... changes that look atomic to the user are often more interwoven than you might think.

 

Packaging a release is typically quite complex, and it’s often easier to bring a number of changes together than just do one, or two even if it is possible.

 

Methodology, is often overlooked, and I’m certain you don’t care , because it hurts you not to have the datalink in the viper, but it is important to understand that in a complex code base having smaller numbers of releases , with appropriate, methodology increases quality and decreases regressions.

 

YMMV. My 0.02GBP. I am not offering legal advice... :music_whistling:

[=Pedro=]

Holding back critical bugfixes for a month despite internally being fixed is nonsensical. Looking at the Viper datalink for example..

 

Also getting 30ish FPS in VR on almost quantum computer is nonsensial.

[jasonbirder]

Is it gonna be a verylarge patch with many changes?

After 30 days without patches it should be

 

Holding back critical bugfixes for a month despite internally being fixed is nonsensical

one patch a month is frankly enough

:lol::lol::lol:

[Conroy]

Holding back critical bugfixes for a month despite internally being fixed is nonsensical. Looking at the Viper datalink for example..

 

+1

[Eldur]

Also getting 30ish FPS in VR on almost quantum computer is nonsensial.

 

This is the big constraint at the moment. Especially since this does not work at all, at least I'm not seeing any controllable planes or cockpits when I try.

But my guess is since the new footage is already ver 2.6.0, they're not going for another 2.5.6 version anymore and just adding something new might as well have been 2.5.7. So it's a bigger step and hopefully we'll see the performance again. To be fair, it's not VR only, it just shows there a lot more. If that extra week happens to get us a good update, I'll happily wait another week for it and do some freeflights (like Case I or AAR) or completely different things meanwhile.

[TAW_Blaze]

It all depends on dependencies, packaging and release methodology.

 

We don’t know what hooks, it is dependent on in other parts of the code... changes that look atomic to the user are often more interwoven than you might think.

 

Packaging a release is typically quite complex, and it’s often easier to bring a number of changes together than just do one, or two even if it is possible.

 

Methodology, is often overlooked, and I’m certain you don’t care , because it hurts you not to have the datalink in the viper, but it is important to understand that in a complex code base having smaller numbers of releases , with appropriate, methodology increases quality and decreases regressions.

 

YMMV. My 0.02GBP. I am not offering legal advice... :music_whistling:

 

I'm familiar with these problems, but it's clear there were already attempts at fixing and something just went wrong. Having a release train that is incapable of delivering specific changes on demand is a sign of a lot of problems in general.

 

The VR issues are debatable since it's not just "one specific bug" so I can understand how that goes on for a while. I've seen a lot of VR users turn away personally because it is just straight up unplayable. I'm lucky enough to have retained good performance on a normal screen.

[Harlikwin]

my opinion, likely unpopular, one patch a month is frankly enough, so ED keep on holding to your guns and release when its ready ... there is quiet an eco system around DCS, and a patch a month gives everyone a chance to catch up with their mod or scenario or whatever, not to mention deal with changes as players ... which is the point.

 

I think the bigger issue is that what upsets people is when there is a "schedule" and it gets broken or out of whack. I personally don't care if the patch is once a month or every two weeks, just make sure it actually gets out in some predictable fashion. At this point for me all I ask is just give us like 2-3 days notice if the patch/module release is coming out so I can plan around that. There are plenty of people with busy schedules, some even take days off for major releases (I'm not one of them, but I've seen the epic rage posts when things go wrong from those guys). But I do like to schedule an hour or two to check out new features.

 

As for the "upcoming patch" IMO its basically gonna be the supercarrier release. Plus whatever pent up simple fixes they add for the other aircraft IMO. I very much get the impression its all hands on deck for the SC, so I personally don't expect much for the other AC aside from perhaps the F18 and possibly the F14 since they are related to the SC. I do hope they debugger the F16 D/L problem, but I'm not holding my breath. And hopefully the release will be good since ED seems to be testing the crap out of it.

Edited May 13, 2020 by Harlikwin

[speed-of-heat]

I think the bigger issue is that what upsets people is when there is a "schedule" and it gets broken or out of whack. I personally don't care if the patch is once a month or every two weeks, just make sure it actually gets out in some predictable fashion.

Yep also this, gets easier to hit a monthly schedule, than a weekly one...

[Chopper A-10]

That's for the update NineLine! It will be worth the wait

[shagrat]

Well, but this is not a solution to the problem that has been bothering us for over a month and does not allow you to enjoy the plane.

I never had any "fps drops" in the Hornet, as well as some buddies I play with online these days. The one guy having trouble with fps drops with SA page, had no further issues after reverting back to a not bugged Nvidia driver.

ED can't do much about nvidia messing up their drivers. ...and we are pretty lucky with DCS, some games had issues where they could only choose between two different problems. Latest Nvidia "Hotfix" seems to fix most of the newer issues for DX11. :dunno:

[ngreenaway]

Is it gonna be a verylarge patch with many changes?

 

After 30 days without patches it should be :P

 

I've been compiling the patch notes of features& fixes implemented in OB since the last stable update. I just copy& paste EDs notes, and consolidate topics.

 

After five months it's up to a 30+ page word document.(and continues to grow)

When it finally hits, that's going to be a monster update

[Harlikwin]

I've been compiling the patch notes of features& fixes implemented in OB since the last stable update. I just copy& paste EDs notes, and consolidate topics.

 

After five months it's up to a 30+ page word document.(and continues to grow)

When it finally hits, that's going to be a monster update

 

I'm not holding my breath but I hope you're right.

[ngreenaway]

I'm not holding my breath but I hope you're right.

 

Yea , don't hold your breath- there's no indication that update will drop anytime soon. I'm expecting 256 to get squared away but some unexpected but on SC to continue delaying stable update.

 

Doesn't affect me much, tbh, cuz I primarily fly mi8 in Caucasus map these days, and neither have needed or gotten much love since last update, but I don't have a lot of empathy when an OB feature gets delayed a week or two.

 

It would be nice to finally see the new shark pit tho. And tool around in the Jeff over the newly re-lit PG map before going back to my mi8

[mole_man99]

Stable version update

 

It's been 5 months since Stable version was updated and there have been several Open beta updates since.

 

 

Any sign of a stable update? I have my eye on some of the mods to F-18 listed in the OB updates. Wondering if I should switch and become an OB user.

[Bagpipe]

It's been 5 months since Stable version was updated and there have been several Open beta updates since.

 

 

Any sign of a stable update? I have my eye on some of the mods to F-18 listed in the OB updates. Wondering if I should switch and become an OB user.

 

If you do you will enjoy ALL the good with only a little bad. Others may argue otherwise but they have no patience. :thumbup:

[Aluminum Donkey]

It's been 5 months since Stable version was updated and there have been several Open beta updates since.

 

Any sign of a stable update? I have my eye on some of the mods to F-18 listed in the OB updates. Wondering if I should switch and become an OB user.

 

Go for it! You've got nothing to lose but your sanity :) Seriously though, OB lets you check out the latest goodies without too many problems.

 

People have been saying that 2.5.6 OB is a stutter-fest, but that's not entirely true. You just have to fly it for a while. It's a huge update, and every time you get a really big change, it stutters for a while, then runs fine.

 

I didn't write any code for DCS but it probably has to build some kind of internal database to access graphical assets. I've often found that large updates cause stuttering, but it goes away all by itself after a while. So, maybe running the sim and flying different missions in different maps with different aircraft/units etc. allows DCS to 'map' its assets for quicker access in the future. Whatever the case, "flying it out" seems to work well for me--at least until the next big update.

 

So go ahead and try it out! You can always revert to Stable if you want.

 

AD

[unltd]

Now with the closed beta group, isn't the so called stable release version sorta like a legacy version and the open beta really the release version especially since mp servers run it and all the new modules require it? Seems like we have a semantics issue now that may be compounding the communication issue. Perhaps all we need is a name change...

Edited May 14, 2020 by unltd

[NineLine]

Now with the closed beta group, isn't the so called stable release version sorta like a legacy version and the open beta really the release version especially since mp servers run it and all the new modules require it? Seems like we have a semantics issue now that may be compounding the communication issue. Perhaps all we need is a name change...

 

No not at all, no matter how many people we throw at a version it still doesn't compare to public Open Beta, and its always going to be a good thing to have that buffer before releasing to stable.

[Steph21]

They should have updated the stable on the latest 2.5.5 version, before pushing 2.5.6 on OB. At least Stable wouldn't be so much out dated.

 

OB hasn't been updated in the last 3 weeks.

 

Maybe DCS updates are on COVID-19 lockdown...

 

We probably won't get a stable update until 2.5.6 FPS issues are sorted on Open Beta, so that could take a while! Which is a pain, especially for Mirage pilots where Mirage is broken on Stable and back to really good shape on latest OB (with further improvements incoming).

Edited May 14, 2020 by Steph21