beta to release...should we update/

[fitness88]

I've been using the beta version to date and don't have a release version installed. Am I missing something by staying with the beta and not installing the release version when it finally comes out?

 

 

Thank you.

[mvsgas]

they are both the same version right now

https://updates.digitalcombatsimulator.com/

[Art-J]

You miss nothing, as both are exactly the same at the moment.

 

If next Beta update, whenever it comes in the near future, breaks something important, then you might want to consider reverting back to release, but with conversion procedure being fast and simple anyway, choose whatever works best for you.

[fitness88]

Thanks to both for the info. So when a release version comes out, on that day beta and release will be the same until beta receives another update ahead of release....correct?

[Grimleo]

Thanks to both for the info. So when a release version comes out, on that day beta and release will be the same until beta receives another update ahead of release....correct?

Correct using a conservative Configuration Management (CM) process. Open Beta uses Release Candidates. Closed Alpha and Closed Beta could include debugging code that needs to be removed when compiling a Release candidate.

[Art-J]

Grimleo, no need to make it more confusing than it really is, especially given the fact that Alpha/Beta/whatever fancy terms tend to have somewhat different meaning in DCS compared to any other software :D.

 

@ fitness88 - In DCS reality, though, indeed that's pretty much how it always works.

[fitness88]

Thanks again!

[eaglecash867]

The Beta looks, runs, and feels great! But, I'm keeping my "Stable" right where it is so if I run across something that's broken in the Beta, I still have an earlier generation of the Release version. No point in locking myself out of my "safe space". :)

[Doum76]

I've been using the beta version to date and don't have a release version installed. Am I missing something by staying with the beta and not installing the release version when it finally comes out?

 

 

Thank you.

 

 

I personaly always had both installed (of course fun thing when you have disk space for it) so i always get relased to latest version, i uausaly fly OB until it gets on stable version, when new patches coems to OB and i am not happy, i still can use stable, but for now i use OB for the only reason, some of my mission done in OB has weird behavior when editing in Stable version, so instead of going in one to save and fly in the other, i stay in OB.

[QuiGon]

The Beta looks, runs, and feels great! But, I'm keeping my "Stable" right where it is so if I run across something that's broken in the Beta, I still have an earlier generation of the Release version. No point in locking myself out of my "safe space". :)

It's pretty easy to convert the Beta back to the Stable by using the updater with the corresponding command, so there is not really a need to keep them both installed in parallel.

[eaglecash867]

It's pretty easy to convert the Beta back to the Stable by using the updater with the corresponding command, so there is not really a need to keep them both installed in parallel.

 

Thanks for the suggestion, Quigon, but I've got plenty of space on my program files SSD, so its just easier to keep both in parallel.

[fitness88]

Fortunately we've had a stable beta version and being able to fly F18 and it's nice getting the updates first ...so long as they aren't broken.

Thanks all!