So does 2.5 Beta automatically patches itself to release 2.5 version?

[DaveRindner]

So does 2.5 Beta automatically patches itself to release 2.5 version?

 

"Cause my 2.5.0.15365 Beta checks for updates but finds none. My internet works fine, thank you.

What is the Release version build number?

 

Thank you.

[HiJack]

No it does not. Download the installer and install, it will copy files needed from your OpenBeta.

[Bluemask]

Somehow the versions seem to be the same: https://updates.digitalcombatsimulator.com/

 

I did a fresh install of the release\stable version on a brand new computer, and the version number is the same as my other machine which is running the Open Beta. Folders on my fresh install do not say "Beta" anywhere, but both updaters return the same the same version number, and the same version number displays inside the simulator.

 

Definitely a bit confusing.

Edited April 7, 2018 by Bluemask

[Mr_sukebe]

My understanding is that right now, 2.5 and 2.5beta are both currently the same.

Assuming that ED follow the type of software standards I've seen elsewhere, then I'd expect that going forward, that new changes will be only applied to the Beta version, i.e. for test in the public domain, only to be applied to the "production" version once the level of outstanding issues is considered acceptable.

Going forward, that would mean that there would probably be a good month trail of the functionality in the production to the beta.

[Art-J]

Open Beta and Release are always separate installs, one never automatically converts itself into the other unless you manually force it to.

 

However, there's always a period of time when release copy "catches up" with the Beta one as far as content is concerned (that's what happened last Wednesday), and both are technically the same for a couple of days/weeks until the Beta moves forward again with next update in the pipeline.

 

It's been like this since introduction of Open Beta concept itself years ago, so nothing changed here.

Edited April 7, 2018 by Art-J

[Fri13]

It is very important to knowledge that when person takes alpha/beta/RC or what ever testing/development version, it is expected they know what they are doing and are ready to follow the updates, versions and all the complexity.

 

Then the stable is for those who want to be care free as much as possible, and not really know all the testing methods and tasks.

 

And it is nice when developers update to stable version, they offer a time window when the test branch can be "transferred" to stable one if one wants to do so.

 

So it is expected that test branch always stays as such, so the tester can do the copy of release and keep then the test branch on the side if so wished.

[QuiGon]

Open Beta and Release are always separate installs, one never automatically converts itself into the other unless you manually force it to.

 

However, there's always a period of time when release copy "catches up" with the Beta one as far as content is concerned (that's what happened last Wednesday), and both are technically the same for a couple of days/weeks until the Beta moves forward again with next update in the pipeline.

 

It's been like this since introduction of Open Beta concept itself years ago, so nothing changed here.

This! It's been like this between the OB and the stable release branch for many years now. It's not something new. You can always manually switch between the two branches using the updater with the following command:

OB -> Stable Release: DCS_updater.exe update @release

Stable Release -> OB: DCS_updater.exe update @openbeta

More info can be found here: https://forums.eagle.ru/showthread.php?t=114030

Edited August 25, 2020 by QuiGon

[Gandalf_56]

Skatezilla utlity do the trick without any effort from your side!!

 

https://forums.eagle.ru/showthread.php?t=160053