2.5 open beta / stable update strategy

[nessuno0505]

I'm quite new to DCS and so I'm asking in order to understand the strategy behind. I mean: now 2.5 open beta is out, but it is still quite full of bugs, some of them come not solved from 1.5.8, but some others are totally brand new and 2.5 specific. I'm still with 1.5.8 and I'm waiting for the 2.5 release version, thus hoping to avoid a lot of this new bugs (and maybe have also some old ones solved). Now I ask: when a beta user finds a bug, how much time does ED take to solve it? Will all of this bugs pass to 2.5 stable or can I presume there will be a major fix / update of open beta before stable will be out? I hope the only difference won't be only the time of release, otherwise I can't see an advantage in waiting for stable version...

Edited February 4, 2018 by nessuno0505

[NeilWillis]

Some bugs are fixed quickly, some hang around for a long time.

 

It depends entirely on how major ED consider them to be as to what takes priority and what doesn't.

 

Generally, the Beta updates quickly migrate to the release version after it has been exposed to the community for a while to confirm nothing major is wrong.

 

I am afraid you will be waiting a long time if you want a bug free DCS World. By it's very nature it is constantly evolving, and at any point, things can break. Unless you defer updating until you know that the bugs have been ironed out - as a lot of multiplayer communities do, then you'll get minor and sometimes persistent niggles.

 

The release of 2.5 will we hope make that less of an issue as the underlying technology will not be changing quite as much as it has in the recent past, and having a single basic DCS World will mean less time spent in adapting updates twice too for 1.5 and 2.0.

[nessuno0505]

I'm not waiting for a totally bug-free version of DCS: even 1.5.8 stable has some bugs but I can live with them. I'm waiting for the stable since I do not want to be a tester. For example, I've read that cockpit illumination of the a-10c and even more the ka-50 is heavily bugged in 2.5 and this is a high priority for ED to correct. Now, cockpit illumination of these modules in 1.5.8 is fine, so I assume that this bug in particular will be solved before 2.5 stable release. And this is why I patiently wait my at least two weeks for upgrade availability. Otherwise, if cockpit illumination bug will still be present in 2.5 release, what is worth for a beta version?

 

P.S. I deal with cockpit lights since this is an example of a quite major bug that is present in 2.5 and not in 1.5.8; I know there are others similar and, according to my point of view, this kind of "new" bugs should be a major priority to correct in any case.

[DonutDudeDD]

I too am remaining with 1.5.8 until the 2.5 stable comes out. Anxiously awaiting word on an approx release date (1 to 2 weeks?) for the 2.5 Stable release....from their website soon I hope.

[BIGNEWY]

From Wags

 

The team is working very hard to bring 2.5 OB to final release. We have been reading all the feedback and striving to address all valid issues. The biggest one we are focused on is memory management. Less than a week after the 2.5 OB release, we released a hot fix today.

 

We don't want to paint ourselves in a corner and provide a 2.5 stable release date as there are too many unknowns regarding fixing some of the identified issues.

 

Thanks

[ebabil]

a few days later, it will have been 2 weeks

so we may see something.

[cichlidfan]

a few days later, it will have been 2 weeks

so we may see something.

 

Actually, we are most likely to see something when they solve the memory leak issue. Not before. The number of days is so irrelevant it isn't even funny.

[Tinkickef]

I'm not waiting for a totally bug-free version of DCS: even 1.5.8 stable has some bugs but I can live with them. I'm waiting for the stable since I do not want to be a tester. For example, I've read that cockpit illumination of the a-10c and even more the ka-50 is heavily bugged in 2.5 and this is a high priority for ED to correct. Now, cockpit illumination of these modules in 1.5.8 is fine, so I assume that this bug in particular will be solved before 2.5 stable release. And this is why I patiently wait my at least two weeks for upgrade availability. Otherwise, if cockpit illumination bug will still be present in 2.5 release, what is worth for a beta version?

 

P.S. I deal with cockpit lights since this is an example of a quite major bug that is present in 2.5 and not in 1.5.8; I know there are others similar and, according to my point of view, this kind of "new" bugs should be a major priority to correct in any case.

 

Cockpit light bug has been around since deferred shading was introduced to DCS 2.#. So its been around a long time, and most of us night owls have found workarounds. I could probably start the Hog blindfold now. :smilewink: More serious bugs have come with 2.5 that affect the view out the window.

 

ED are no doubt busting a gut to repair the problems, but a lot of them will be very complex and deep seated, so don't expect it done quickly.