DCS World 1.2.7 Released

My DCS World doesn't detect there is a newer version yet, although the 1.2.7 version is available to download through the ED site... :(

I see they are on the website now.

I assume the update will soon be recognized by the DCSW 1.2.6 auto-updater and not only by the open beta version.

W00T? Really? Not a beta update??

It's the real deal :) But as Turbohog just pointed out its not working.... yet!

I see they are on the website now.

 

I assume the update will soon be recognized by the DCSW 1.2.6 auto-updater and not only by the open beta version.

Yeah, will have some patience... What I found weird though, is that the Steam version of DCS World already started updating, but the stand alone version not yet. It's the first time in all my gaming years that Steam actually was faster with updating a game than the stand alone version.

When I run the DCS it says that we have a new version, 1.2.7, but it doesn`t auto update...

ok, quick Q. I updated 1.2.7 and removed 1.2.6

Do I have to download the entire 1.2.7 allover again?

When I run the DCS it says that we have a new version, 1.2.7, but it doesn`t auto update...

Auto-updater for DCSW V1.2.6 is not working yet.

open beta 1.2.7u2 = release 1.2.7 .... wtf??

The release version of 1.2.7 is the same as the last open beta version 1.2.7u2.

What about the still existing, not really insignificant bugs? I.e. I can't really fly the A-10C as I am still unable to save the control settings (or at least, the MFD settings for the Thrustmaster MFDs can't be set). Some AI bugs that could be potentially mission breaking (i.e. unresponsive ground units). And some more?

Wasn't the goal to release a version that does not introduce new (significant) bugs? :huh:

edit:

correction. there are differencies between the version. for example, the "floating huey cockpit" seems to be fixed (ty!). But .LUA wise, they are identical (except 1 change - maybe related to the "saving FFB settings"-bug)

mmmm .... strange.

Nothing updating for 1.2.6

Got an auto updater upgrade for 1.2.7 OB, followed by a 268 MB update for 1.2.7 OB,which has just crashed due to "server overload."

Auto-updater works here. But the version number is not 1.2.7, but 1.2.6.99999.3.

LOL

i got the weird version number too, then lost connection with a server overload message.

i got the weird version number too, then lost connection with a server overload message.

Same here...

Auto-updater works here. But the version number is not 1.2.7, but 1.2.6.99999.3.

 

LOL

Wow, indeed.

I'm going to wait with auto-updating my 1.2.6 installation to 1.2.6.99999.3 to see what this is about :huh:

Ok then... I`ll wait...

It looks like the actual official release isn't on the download servers just yet, ? Hopefully an announcement is made once it is.

You mean control setting saves whilst inflight? Just do it the standard way. No problems here with the standard way on thrustmaster MFD controllers.

Waiting for official announcement when downloads can begin... :(

Downloading update!

Wow, indeed.

 

I'm going to wait with auto-updating my 1.2.6 installation to 1.2.6.99999.3 to see what this is about :huh:

It seems that it's an updater change. After clicking OK a few times it asked me again to go from 1.2.6.99999.3 to 1.2.7.something.

All good :)

Yup, all good. 1.2.6.<lots of nines> seemed merely an Auto Updater - update. After updating, the thing asks to update to 1.2.7.

It looks like the actual official release isn't on the download servers just yet, ? Hopefully an announcement is made once it is.

You mean control setting saves whilst inflight? Just do it the standard way. No problems here with the standard way on thrustmaster MFD controllers.

Don't know about the official autoupdate for 1.2.6, but even the change log is just a combination of the open beta change logs up to 1.2.7u2 ob.

As for the MFDs - as reported in the open beta bug forums: when hitting "Ok" after I made changes, the .lua config files for the MFDs are not saved correctly, the resulting .lua files are broken/crippled and thus losing any button assignments. This happens from within a mission as well as from the menu Options->Controls.

ok, what version number are we supposed to see? I have 1.2.7.23094.

Something smallish downloaded but i'm not sure what it was!

Yesterday ED announced that DCS: FC3 will be availible in the first quarter of 2014. But the changelog today state that:

"With DCS version 1.2.7 an installation of Lock On: Modern Air Combat is no longer required for FC3 installation"

Does this really mean, that I can buy FC3 now and it will be fully integrated into DCS: World?

The main goals of v1.2.7 were to squash many existing bugs with a huge focus on multiplayer stability and to provide a platform for the UH-1H Release version. The purpose of the Open Beta was to provide updates in stages to be mass-tested, before issuing a release patch that may have potentially introduced more show stopping crashes than fixes.

The MFD bug you refer to has been fixed in our internal version (as stated at the end of your open beta bug report thread), but unfortunately was not integrated into v1.2.7 before feature lock. It will be included in a future update.

Rest assured all of the other reported issues are being looked at and dealt with. It cannot reasonably be expected that every single outstanding issue to be fixed before the release of a new patch, otherwise patches would never be released. :)

It is, of course, a balance of how severe a problem is, the time required to identify and fix it, and how likely it is to break the current stable version of the program. We're getting there!

As for the change logs being identical between Open Beta and Final ... that is the nature of an Open Beta. You release, test, make fixes, and update the beta product. Once the beta product is stable you release that stable version as-is, without introducing any major additional changes between Stable Open Beta and Release. Then you move on to the next round of updates. A release patch change log is rarely much different from the most recent beta change log in any development environment I've ever dealt with.

Onward we go! :pilotfly:

We'll need to setup every aircraft again or can we just copy and paste the settings from DCS 1.2.7 beta to the final version? Please, tell me that it's possible.:noexpression:

I do miss the engine smoke effects on the latest beta. I can't see them any more on the F15 and Su27. According to the changelog they have just been adjusted but i cant see a trace of them. I know there were those who felt they were not realistic but I loved them. Perhaps they will be more apparent on the actual 1.2.7 release?

The main goals of v1.2.7 were to squash many existing bugs with a huge focus on multiplayer stability and to provide a platform for the UH-1H Release version. The purpose of the Open Beta was to provide updates in stages to be mass-tested, before issuing a release patch that may have potentially introduced more show stopping crashes than fixes.

 

The MFD bug you refer to has been fixed in our internal version (as stated at the end of your open beta bug report thread), but unfortunately was not integrated into v1.2.7 before feature lock. It will be included in a future update.

 

Rest assured all of the other reported issues are being looked at and dealt with. It cannot reasonably be expected that every single outstanding issue to be fixed before the release of a new patch, otherwise patches would never be released. :)

 

It is, of course, a balance of how severe a problem is, the time required to identify and fix it, and how likely it is to break the current stable version of the program. We're getting there!

 

As for the change logs being identical between Open Beta and Final ... that is the nature of an Open Beta. You release, test, make fixes, and update the beta product. Once the beta product is stable you release that stable version as-is, without introducing any major additional changes between Stable Open Beta and Release. Then you move on to the next round of updates. A release patch change log is rarely much different from the most recent beta change log in any development environment I've ever dealt with.

 

Onward we go! :pilotfly:

Allright, I am calming down already ... :o)

Ofc I did not expect that every single, small bug would be corrected before the official release. But there are at least a few that should not be present in the release version, imho (again, that CA AI bug for example). I just hoped/expected that this, 1.2.7u3, would have dealt with some more of those bugs (and thus, resulting in another change log).

But anyhow, at least quite a few bugs were discovered and documented.

Oh, and tbh, as I just found out, it actually seems that there might be a little more under the hood that the (not extended) change log suggests. Like the Huey floating cockpit bug and even the Huey throttle non-proportionality bug seems to be fixed (hint: turn off GOV AUTO)