**Viggen Release Information (27th)**

[theOden]

Tack för den kroppsfinten.

[Boomer_QLD]

3 Versions of DCS on my SSD, no thanks I'll wait until you come to a decision about which one is more important to you :-)

[IzoAzlion]

3 Versions of DCS on my SSD, no thanks I'll wait until you come to a decision about which one is more important to you :-)

 

Literally only need one version and a quick "patch to this version" button.

 

But okay, lol.

[Paveway333]

I updated to Open Beta using Skate's GUI updater as I have done before, but now I don't know

if im still in Release Version or Open Beta because they have the same version number.. =/

[EasyEB]

This is great news guys! I only run the beta so this is perfect!

 

 

Thank you Leatherneck!!!!

[IzoAzlion]

I updated to Open Beta using Skate's GUI updater as I have done before, but now I don't know

if im still in Release Version or Open Beta because they have the same version number.. =/

 

If the versions are identical then it shouldn't matter is my guess.

[uboats]

if you don't know what branch it is, open the autoupdate.cfg in the root folder of dcs, and check the 2nd line

 

"branch": "openbeta",

[myHelljumper]

If the update bugged the release version peoples won't be happy either... Some are never happy.

[BlackLion213]

Thanks for the heads-up on 1.5.6 - this gives me a day to make sure my Beta branch is ready. :thumbup:

 

-Nick

 

PS - Good luck this Friday!

Edited January 26, 2017 by BlackLion213

[Enduro14]

Way to much Snow flakes in here, its winter i got it but it really isnt a big deal. This is the state we are currently in with DCS until Unification day. Thanks for the heads up at least their is communication on this now rather than day of.

Major online server hosters have already stated they will be running the beta to support Leatherneck. If you think about it the open beta is the better version to run as its the same thing minus the very few situations like this.

[probad]

Major online server hosters have already stated they will be running the beta to support Leatherneck.

 

very nice of them!

[NeilWillis]

We always have the Beta branch maintained on our server. We run whichever is relevant at any point in time, so clearly, this Friday it will temporarily be switched to the Beta until the release version catches up.

 

As the current iterations of release and beta are identical, I can't see why anyone has any reason to complain. It is so simple to change the status of a single install, and naturally, a major update will be better handled as a beta release.

 

The one significant question that everyone has missed entirely is what is being added/changed in DCS World this weekend? Preparations for an impending release of Normandy in the next few weeks maybe? We'll have to wait and see what is said in the change log.

[Enduro14]

We always have the Beta branch maintained on our server. We run whichever is relevant at any point in time, so clearly, this Friday it will temporarily be switched to the Beta until the release version catches up.

 

As the current iterations of release and beta are identical, I can't see why anyone has any reason to complain. It is so simple to change the status of a single install, and naturally, a major update will be better handled as a beta release.

 

The one significant question that everyone has missed entirely is what is being added/changed in DCS World this weekend? Preparations for an impending release of Normandy in the next few weeks maybe? We'll have to wait and see what is said in the change log.

 

Exactly, it seems this is a major update and should bring excitement i too wonder what major additions are coming along with all the new tech that the Viggen brings

[Meiz]

If the update bugged the release version peoples won't be happy either... Some are never happy.

 

This.

 

Viggen on Beta branch, only really impacts the Viggen owners that wanted it on release day and don't know how to switch their stable branch to beta. A bad DCS patch pushed to stable branch impacts everyone. It being the first patch for a while means there could be many more changes and additions to other modules and DCS world too. I'm sure we've all experienced some of the bad patches last year that broke some things that were quite annoying.

[theOden]

It's not the expected bugs, it's that they sell it as "27th Jan on STABLE 1.5" and that's what I bought and, sadly, planned for this weekend. Not sure what you defenders are chasing after.

[NeilWillis]

The announcement was made by an agency that has no control over the update schedule. Hence the announcement in advance of the release to rectify the mistake.

 

"Everything is subject to change" is a phrase you will always see as a caveat on all announcements for a very good reason.

 

You ought to take more notice of bumper stickers because clearly - "$h1t happens"

[mattebubben]

I find it funny how some people seem to try to blame Leatherneck for this...

 

You guys know this is in no way their fault and they had nothing to do with this change?...

 

Leatherneck (and any other 3rd party dev) has no control what so ever over what Version of the game ED decides to patch.

All they do it give ED a version of their module and ED implements that Module into the patch they are making prior to Uploading it.

 

So leatherneck had absolutely NO say in the matter of it being released on Stable or Open Beta its all up to ED...

 

If anything we should just be very grateful Cobra went out of his way to warn us (and we also very possible he was just given this information himself) since this gave us a heads up so we could prepare the Open Beta version.

 

Leatherneck announced the module would be released (into early access)

on the 27th of January (and they are keeping that promise)

but they had no way to control what version ED

decided to patch that day... so i makes no sense what so ever to blame Leatherneck...

[theOden]

..

"Everything is subject to change" is a phrase you will always see as a caveat on all announcements for a very good reason...

You don't see the extremely unprofessional in that statement, do you?

[Magot]

So in fact its not release in 27th january, because official verison is 1.5.5 or 2.0

It was my last pre Purchase from Leatherneck! :mad:

What is next step waiting next half year? I don't want any annoying betaversions ...

Edited January 26, 2017 by Magot

[mwd2]

So in fact its not release in 27th january, because official verison is 1.5.5 or 2.0

So its was lie ...

It was my last pre Purchase from Leatherneck! :mad:

What is next step waiting next half year? I don't want any annoing betaversions ...

 

You have not read the announcement:

 

Swinoujscie, Poland December 23rd 2016 – DCS: AJS-37 Viggen is now available for pre-purchase!

 

[..]

 

DCS: AJS-37 Viggen will launch on January 27th for $59.99. Pre Purchase now for $47.99 and save 20%!

 

[..][/i][/indent]

 

there is no notice about the version on which they launched the Viggen first! And by the way, the BETA is a testbed, so that your 1.5.5. get not crashed on bugs from the next update!

[Art-J]

You don't see the extremely unprofessional in that statement, do you?

 

It sure is, from western business standards point of view, but c'mon... You sound as if You started playing DCS a few weeks ago, but You're here long enough to know that's alway been the case with this (and any other actually) Russian simulator developer. That's how they run their business and one can only "deal with it" or switch to other sim platform.

[scaflight]

Mattetubben: you should call people out by name when the set (people expressing regret) is so difficult to separate from the subset (people 'blaming LNS'). Otherwise we could end up with a lot of passive aggressive style posts. :)

 

On another topic, I've hijacked a relative's connection and the download is going much faster. Won't have to wait until March to get the Viggen :D

[NeilWillis]

So in fact its not release in 27th january, because official verison is 1.5.5 or 2.0

So its was lie ...

It was my last pre Purchase from Leatherneck! :mad:

What is next step waiting next half year? I don't want any annoing betaversions ...

 

Who said anything like that?

 

Very strange reaction to something totally reasonable and utterly beyond Leatherneck's control. I am sure I speak for everyone when I say how much we will miss you.

[NeilWillis]

You don't see the extremely unprofessional in that statement, do you?

 

I wasn't commenting on how professional or not the statement was, just the fact that it is there.

 

Personally, I don't hold ED or any of the other developers to the same standards as I would one of the major software houses. This is a very niche genre, and it is done on much smaller budgets.

 

We could of course wait an extra 2 months for all these issues to be resolved, but like many here, I get involved in early release, and that comes at a price.

 

The key to all this is a very simple phrase again - "Pre-release" Try and take things in that context and don't hold them to such high, over ambitious standards.

[Galwran]

If the update bugged the release version peoples won't be happy either... Some are never happy.

 

Exactly this.

 

Of course a big update goes first to the beta branch. If it is verified stable, only then it will be released in to the stable branch.

 

A company cannot just go risking the current stable product just because of a single release. Hence the open beta.