I'm sure you're quite capable of figuring out the answer to that

Ice, if you thinking that the rework needed for Caucasus campaigns/missions will also be needed for those that are build for Nevada, there is no likely reason for that to be the case since Nevada has not been changed, nor will it be.

I hope so.... but I wasn't just thinking of that. I remember how things would break between patches and going from 2.XXX to 2.5 isn't really just a patch now, is it?

Care to buy the campaign and tell us whether 2.5 borks it?

The possibility of any given patch breaking something is always there. I just don't think the v2.5 release is going to be all that earth shattering for Nevada based missions.

As for me buying the campaign to test it, no thanks.

Yep.... but some people seem to have a knack of hitting the jackpot

2 weeks to go. Who's taking bets? it's getting close. A promise is a promise.

I'm guessing they'll chuck whatever they have out the door and call it 2.5 and if anyone complains of missing features, we'll get the "everything is subject to change" line and Wags will lose whatever credibility he has left.

Pretty much sums it up

Humbug!

Yeah i'm pretty sure they'l just throw it out and if the "everything is subject to change" line doesn't work there's always the moderators to "clean" things up over there.

Some updated info from -> https://forums.eagle.ru/showthread.php?t=200340

Gentlemen, here is some explanations how your current 1.5 (and/or 2.2) will be converted to 2.5, please take a look the attached diagram. Transition will be made in 2 stages:

1 stage: Beta-version. 1.5.8 Open Beta will be updated to 2.5.0 Open Beta. Updater will check 2.2.0 (Alpha) and add necessary modules to 2.5.0. Then Open Alpha 2.2.0 will be uninstalled (user will be prompted about 2.2.0 removing).

1.5.8 release remains as is on this stage.

Some time (maybe one-two weeks, we hope no more) for wide test of this procedure.

2 stage: Release version. 1.5.8 release updated to 2.5.0. User will be prompted before update about saving 1.5.8 Final version in the separate directory.

Modules from 2.2.0 Open Alpha (or 2.5.0 beta - see 1st stage) version will be used for 2.5.0 installation, after that old 2.2.0 will be uninstalled (user prompted).

Open Alpha 2.2.0: this branch is no longer supported. If user have only 2.2.0 Open Alpha, updater will suggest to download 2.5 installer - it will install 2.5 release and remove 2.2.0 Open Alpha.

Home folders (Saved Games\DCS) remains the same (Saved Games\DCS and Saved Games\DCS.openbeta). New Saved Games\DCS.release_1_5 will be created for 1.5 Final version and all content will be copied into it from Saved Games\DCS. We also strongly suggest to remove Saved Games\DCS\Config\options.lua and make graphic tuning from scratch using DCS GUI because of 1.5 and 2.5 renders are significantly different.

Activations. All activation keys are saved in Windows Registry and NO additional activation needed.

1.5.8 Final version installer will be available on DCS site.


and they have a wee picture as well, excellent

So only the beta version gets updated to 2.5 in January? Then 2 weeks later the release, maybe, "depending on wide test of this procedure"?
Sounding like a promise breaking to me.

No, it looks like they will be testing this the next 2 weeks. and the new 2.5 takes from all the versions and combines it in stages to 2.5.. No Promise broken yet

Some Vivaldi to chill things out....

https://www.facebook.com/eagle.dynamics/videos/10159975977600341/

Nate

"2.5 Open Beta coming January 31, 2018."

"Given this, we will be releasing DCS World 2.5 by late-January 2018. This is not an estimate, this is a promise."
Nothing there about Open beta. It clearly states we will be releasing DCS World 2.5 by late January 2018. Not 2.5 Open Beta
Sounds like a broken promise to me. Sounds like ED have missed yet another deadline. Oh well I doubt anybody really thought ED would keep a promise and meet a deadline. Why change now?

And there we have it! 2.5 is being thrown out the door at whatever state it's in... now called "Open Beta" and careful monitoring is now their excuse for any succeeding delays. I'm sure there'll be bugs that will delay 2.5 Release that NOBODY could've foreseen, surely not this company that's been in this business for 27 (?) years.

Anyone taking bets that Stage 2 will be more than "next one to two weeks"?

So now "late January" stands for "end of January and Beta"? For me "late of" is NOT "at the end of", but english isn't my native language. So is "late of" now at "the End of"? But why do we need a "late of" if that always means "at the end of"?
Word gaming... lol!
It's a promise? For sure it never wasn't!
!

"late January" could mean anything during the 2nd half or last 2 weeks of January... or even last week of January as weeks 2-3 would be "mid-January." Knowing ED, I think most of us interpreted this as 31st January 2018 on 23:55:55

Also, as we can see now, "releasing DCS World 2.5 by late-January 2018" means releasing DCS World 2.5 Open Beta. Like I said, they'll chuck whatever they have out the door on the deadline and now they've added the "Open Beta" wording so nobody can really complain when they find out that it's still bug-ridden and in a poor state. "Why do you people complain about a Beta? If you wanted a polished product, wait until Release comes around!" and now they can use that line as their defense.

Gotta love ED!

I got trolled by them prior the Viggen release.
Planned a full evening and stockpiled beer and such only to have the stellar news day before release that we 1.5 series customers was out of luck since the release was going open beta at "promised" date (website still said 1.5 days after release, I don't think they ever wrote anything else but 1.5 actually).

Can you guys see how much I expected this 2.5 to be released as promised?

Yeah, spot on.

Why the hell would you even announce when betatesters are to receive stuff?
Wags is very very different from the project managers and producers I've met in my professional life.

I know he is a very dedicated simmer, just listen to him on that Viggen sortie they did, and I actually like him as a simmer but some days I would like to see on what grounds ED hired him as a producer.