DCS Update Patch Notes Discussion Thread

There is no point in having an open beta build if it's to push crashes in the release branch, along with pretty much all of the other bugs.

Im guessing that ED didn't consider this bug to be a huge showstopper, otherwise they would not have pushed this version to release.

In principle though, I agree with you. "Stable" should only be updated when it is perfectly stable and with a minimum ammount of bugs. If a big bug is introduced in a beta patch, then that version should not be released to stable before the bug is ironed out.

But, may I ask...

Why merge versions if you KNOW that that particular update has bugs in it? And don't tell me this is a third party issue, because the signal tone bug on the AIM-9X was there last week on Open Beta and it is now on Stable too, and the multiplayer Lag/Connection issues have been dragging for weeks, now also making a show in Stable. This is all ED, not third party.

Why not solve the bugs first on OB and then release the fixed updates on Stable? It's not a stable version if it has unsolved OB bugs. It's just another Open Beta with delayed updates, isn't it?

I agree on most of the things said here, but the summer period is about to end and so are the holidays, lets give them some time to sort things while keeping the things said here in the back of their heads, before we raise the torches and pitchforks.

But, may I ask...

 

 

Why merge versions if you KNOW that that particular update has bugs in it? And don't tell me this is a third party issue, because the signal tone bug on the AIM-9X was there last week on Open Beta and it is now on Stable too, and the multiplayer Lag/Connection issues have been dragging for weeks, now also making a show in Stable. This is all ED, not third party.

 

 

 

Why not solve the bugs first on OB and then release the fixed updates on Stable? It's not a stable version if it has unsolved OB bugs. It's just another Open Beta with delayed updates, isn't it?

Sent from my SM-G892A using Tapatalk

"Why not solve the bugs first on OB and then release the fixed updates on Stable? It's not a stable version if it has unsolved OB bugs."

This has been discussed forever! ED made a claim that 2.5 was OB and everyone is supposed to be quiet and enjoy the bugs.

Release version is just an older OB version. That's it.

No one from ED has ever said that. Please dont make false or unconstructive statements.

Fair enough. My choice of words might have been too harsh. But there are no less than a few dozen posts since 2.5 was released stating exactly that position..

It is a confirmed "beta public test build". Here's hoping for fixes.

RAZBAM had already been looking into it, it is their module, they would most likely be responsible for it being fixed, 3rd Parties are generally responsible for their own stuff, and need to get fixes in for releases. The Mav crash is avoidable, dont use the mav for now on the Harrier. It's not reasonable to hold up other fixes for other modules.

They said it was an issue on ED's end... guess that changed?

https://forums.eagle.ru/showpost.php?p=3597913&postcount=12

So what if the updates we get have bugs. That's the nature of software development and bugs will always arise if ED is continuing to bring us new features and improvement, which I am grateful for. The bugs are not show stoppers so relax and understand that these things take time resolve.

It's fixed internally now, just fired a Maverick on the next release candidate for Open Beta.

 

No matter where the issue was, its a RAZBAM module, if the need to work with ED to get something changed in the core, then that is what is needed, I don't know what changed to fix it, but it appears fixed now and should be working next patch.

Great news, thanks for the update.

So what if the updates we get have bugs. That's the nature of software development and bugs will always arise if ED is continuing to bring us new features and improvement, which I am grateful for. The bugs are not show stoppers so relax and understand that these things take time resolve.

Except it's already resolved and was way before the update. If you fly in the Harrier not being able to use this standoff weapon is pretty annoying and while you can go around it, it is a show stopper because it's a crash while trying to use the aircraft in a very common scenario.

The bug was fixed by ED, but they found another bug that also causes a crash. In any case, the fix and missiles will be available on next update.

What about you guys stop complaining about bugs in early access modules and come back when they get released!

What about you guys stop complaining about bugs in early access modules and come back when they get released!

No, people are complaining that known bugs are being transferred to stable without fixing. Thus making stable, not stable.

No, people are complaining that known bugs are being transferred to stable without fixing. Thus making stable, not stable.

If you are referring to a bug in the Harrier remember again the Harrier is in early access. You may argue that it's in a stable release, but this issue is localized to the Harrier only if I am correct.

Bugs on early access modules are irrelevant. AGM not working, then stop using, it's early access, stuff might be broken!

BTW, fixing that bug following the proper development pipeline would mean pushing the fix first to OB to make sure it's working properly before updating Release branch to the same patch, delaying all the other fixes on Release by a week. For a non blocking bug on an early access module, that would just be silly.

Stable should be called "Delayed Beta" as most of the time it has the exact same issues as the previous weeks Beta release.

 

Anyone using Stable may as well download OB and have their game broken a week earlier so they don't waste time and can do something else.

 

This 100% :thumbup:

Bugs on early access modules are irrelevant. AGM not working, then stop using, it's early access, stuff might be broken!

 

BTW, fixing that bug following the proper development pipeline would mean pushing the fix first to OB to make sure it's working properly before updating Release branch to the same patch, delaying all the other fixes on Release by a week. For a non blocking bug on an early access module, that would just be silly.

What is silly is to push CRASHES to a STABLE release. And it has nothing to do with early access, any released aircraft could have gotten this problem and it would have made no sense to push an already fixed crash in a stable version of DCS.

The stable branch is made to be stable not to have crashes and bugs all over the place, which is apparently what ED wants to do with it. The open beta is 80% of the time more stable then the stable branch and people who play the Harrier will upgrade to an open beta version to get a more stable experience next week.

Please keep the discussion on the patch notes, and not what you like or dislike about ED's patch schedule please.

We're not so much discussing the schedule of the patches but what ED considers to be stable for a release version, it's off topic anyways.

We're not so much discussing the schedule of the patches but what ED considers to be stable for a release version, it's off topic anyways.

The conclusion would be to remove all Early Access/Beta modules from the stable branch. Problem solved. :pilotfly:

The conclusion would be to remove all Early Access/Beta modules from the stable branch. Problem solved. :pilotfly:

Or, for some people to stop moaning about EA modules, and just stop using them until they change to release versions.

I mean, all this fuss over 1 weapon in 1 EA module? It’s crazy.

Of course there will be issues, but I can’t remember the last time I experienced a bug that was so severe that I couldn’t use DCS in OB form.

DCS is a project that will be in a constant state of development because of its nature, i.e.new modules, new features.

[…]Of course there will be issues, but I can’t remember the last time I experienced a bug that was so severe that I couldn’t use DCS in OB form.

Perhaps are you flying several modules at the same time and when a module has a problem you can fly on another one ? In my squadron, we only fly one module, when there is a problem with it, it can be frustrating to not be able to fly a COMAO missions because a part of the wing is left out by a software development problem.

I would not mind to wait several weeks for the stable version to be updated as long as it keeps its stability. I know it can be difficult to wait for the latest new toy or improvement and this is why betas exist. It should be fairly easy to understand for users that a stable branch will receive way less frequent updates to the benefit of stability while an Open Beta will push for regular updates at the cost of … stability.

At least we have now better communication from ED, waiting a week for a fix is not that long. I really hope to see some change in the management of the stable and beta branches.

Perhaps are you flying several modules at the same time and when a module has a problem you can fly on another one ? In my squadron, we only fly one module, when there is a problem with it, it can be frustrating to not be able to fly a COMAO missions because a part of the wing is left out by a software development problem.

 

I would not mind to wait several weeks for the stable version to be updated as long as it keeps its stability. I know it can be difficult to wait for the latest new toy or improvement and this is why betas exist. It should be fairly easy to understand for users that a stable branch will receive way less frequent updates to the benefit of stability while an Open Beta will push for regular updates at the cost of … stability.

If you are using a released module, then I sympathise with your situation, but otherwise, my comments still stand.

I cannot see how DCS will ever be in a ‘stable’ state. There is constant development and hence constant bugs of some kind, but users can minimise their risk by only using released modules.