1.2.6.20768.297 00005.813 dcs update

[BIGNEWY]

My dcs is updating anyone else ?

Edited November 25, 2013 by BIGNEWY

[TurboHog]

Yes... 108.8 Mb for me.

 

It's unannounced so maybe just a compatibility thing? (There have been unannounced patches before and they usually weren't anything special...)

[BIGNEWY]

http://forums.eagle.ru/showpost.php?p=1934309&postcount=6

 

Right now we have good progress with 1.2.7 version but have decided to release small update 1.2.6 with 2 noticeable fixes.

Fixed StarForce protection bug with false virtual machine error.

The bug which prevented with normal work on the PC with Nvidia Optimus technology is fixed.

[Rhinox]

Changelog:

 

"...Fixed StarForce protection bug with false virtual machine error..."

 

Could you ED please be more specific? Right now I do not understand what you mean by "false error":

 

a) that VM-error was reported when running DCS on VirtualBox? or

b) that VM-error was not reported when running DCS on VMware?

[towsim]

VHF frequency bug seems to be solved. I observe the correct values if I manually change the frequency on all digits in box1.

 

Edit:

I was too enthusiastic. After I removed my small correction patch, the frequencies are still messed up when crossing a 10th boundary.

Sorry

Edited November 25, 2013 by towsim

[Nirvi]

Any word about AA refueling? Is the tanker still bugged?

[Cibit]

Getting it now:)

Wonder if the new skins for Mi-8 are included:music_whistling:

 

167Mb guess all my mods are being replaced:doh:

[Silver_Dragon]

Any word about AA refueling? Is the tanker still bugged?

 

No included on that patch, wait to 1.2.7 or after.

[Nirvi]

No included on that patch, wait to 1.2.7 or after.

 

Really disappointing...:(

[sobek]

It is just a small bugfix.

[Robin_Hood]

Changelog:

 

"...Fixed StarForce protection bug with false virtual machine error..."

 

Could you ED please be more specific? Right now I do not understand what you mean by "false error":

 

a) that VM-error was reported when running DCS on VirtualBox? or

b) that VM-error was not reported when running DCS on VMware?

 

Will check if the issue is still present with Hyper-V, and will report back

[MTFDarkEagle]

"Noticable fixes".

 

So, are there unnoticable fixes?

[Rhinox]

So, are there unnoticable fixes?

You mean new bugs? Sure as hell are! Just waiting to be reported...

[Skulleader]

I have upgraded my DCS and the size is 738.1mb...

All my Mods are installed and work fine.

Bye, Skull.

[Silver_Dragon]

can ED get a concise changelog?

[TangoIndiaMike]

Didn´t they say that the AAR was already fixed but didn´t made it to the last update in time? And now we don't get it with this update? I'm confused and disapointed...

[Raven68]

Hopefully 1.2.7 will role out this week my friends.

[Zaz0]

Didn´t they say that the AAR was already fixed but didn´t made it to the last update in time? And now we don't get it with this update? I'm confused and disapointed...

 

+1

 

Fixed in internal version and they don't bring it to us... humm ¬¬

[TAW_Blaze]

+1

 

Fixed in internal version and they don't bring it to us... humm ¬¬

 

Just because something is "fixed" it doesn't mean it's ready for public release, nor that it didn't break other things..

[fjacobsen]

Hmm

 

Small update that hardly fixes any gameplay related.

 

I might be impatient, but updates are comming rahter slow and mostly adds new bugs.

 

Both the Huey and the Mi-8 beta progress seems to be at a standstill.

[sobek]

A little refresher to help you understand how versioning works:

 

See this image:

 

http://en.wikipedia.org/wiki/File:VersionNumbers.svg

 

The red line is the internal development. Things are constantly being changed, improved, fixed, tested in that version. That means that it is never in a state fit for release. When a release is prepared, the status quo of the internal version is frozen inside a branch (white rectangle). Ideally, no more functionality changes happen inside that branch, it is tested, bugfixed, tested, bugfixed, etc. until it is considered stable, then it is released. This branch will then only contain the functionality that existed at the point when the freeze happened (plus bugfixes). In the meantime, developers will continue to put new features/fixes/etc. into the internal version, so the internal version progress does never really stop. If something was fixed in the internal version, it will stay in that internal version until a new branch is created.

 

If something was fixed internally and is prepared for a bugfix, the released branch is taken and the new (fixed) code is merged in from the internal version, that means it has to be "stitched" into the old code. Depending on the complexity of the fix, this can be a quite arduous and time consuming procedure, because as we said, the internal version has already progressed onwards since the freeze. It can also be a matter of a few minutes, it depends. Then that fix has to be tested until it can be released.

 

The nature of having to merge code from the internal version that has often moved along quite a bit compared to an older branch dictates that this must be used sparingly, as it causes additional work for the developers that they could spend preparing features in the internal version for the next major release branch.

 

That is why sometimes patches are made to fix one thing but do not contain another.

Edited November 25, 2013 by sobek

[Zaz0]

Ok...

 

Wags reported "This has already been fixed internally, it just did not make it in time for this update." on 10-23-2013, http://forums.eagle.ru/showpost.php?p=1913075&postcount=29 (sorry I havnt seen on steam)

 

And VM error was reported on same day http://forums.eagle.ru/showthread.php?t=116021&highlight=virtual+machine

 

Hummm, If the branch has VM fix, why not AAR fix, if they hace to be frozen later? :(

 

I dont understood

[sobek]

There was no new freeze since 1.2.6 branch was created.

 

Next new branch will be 1.2.7.

 

What Wags meant was that the fix was not ready in time for the previous freeze, so it will be in the next.

Edited November 25, 2013 by sobek

[Zaz0]

thanks sobek

[cichlidfan]

This is why the autoupdater needs a third choice, "Don't bother me again until the next update!" This way I would not have to keep saying no to this update everyday for the next month or so.