1.2.6.20768.297 00005.813 dcs update

[Raven68]

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.

 

:megalol:

[SkateZilla]

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?

 

 

See Here:

http://forums.eagle.ru/showthread.php?t=116021

[Cibit]

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, as i said, 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.

 

Very enlightening Thanks Sobek:)

[Frostie]

A little refresher to help you understand how versioning works:

 

See this image:

 

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

Thanks for explanation.

 

Roll on v2.2 :D

[Pepec9124]

1.2.6.20768.297 00005.813 dcs update

 

You are weird people, just wait for 1.2.7. Have you uninstalled your Real Life Module ?

[Robin_Hood]

Virtual machine error is indeed fixed :thumbup: http://forums.eagle.ru/showthread.php?p=1934701#post1934701

[sobek]

Oh dear, how did this happen? :music_whistling:

 

OT moved to http://forums.eagle.ru/showthread.php?p=1934739

[Lao Fei Mao]

Did Wag mentioned the new su-33 will be released in 1.2.7? I'm dyeing for it.

Edited November 26, 2013 by Lao Fei Mao

[Lao Fei Mao]

Wow, good to hear that :pilotfly: