IMPORTANT MiG-21bis StarForce PATCH - MARCH 2017

[Decibel dB]

SOOOOOOOOO much lost in translation, I just gonna sit and wait until it come in a normal update.

[klem]

SOOOOOOOOO much lost in translation, I just gonna sit and wait until it come in a normal update.

 

This!

[Weegie]

Is that your key number? You should probably edit this image.

 

The minute I posted that image up I thought GOD!! is that my key.

 

So I checked and its not, it's probably some encrypted variation on it that enable Starforce to determine the key but it's defo not my key

 

Thank's a lot though for the advice and concern, it's appreciated

Edited April 2, 2017 by Weegie

[Dolphin887]

I'm down to 0 keys now what?

 

 

Please send an e-mail to support@leatherneck-sim.com

 

- Please tell us which DCS version you are using (open DCS and look at the bottom-right).

 

- Please do this for each DCS version you might have installed.

 

- Please send you serial (key) for StarForce server side check.

 

 

Don't post this data here, send in e-mail.

[scotth6]

Please disable the MiG module in Alpha and Public to avoid SF spamming you when you use those DCS versions.

 

Both mentioned version will be patched, and MiG will become available for those.

 

We have to wait for the patch release. You wont need any further activations provided nothing changes on your current setup.

 

OK. Thanks for the response.

 

Cheers,

[scotth6]

You've got it sorted allright. It's just Your MiG will not work in stable and Alpha versions for the time being, as these haven't been updated yet. Click through the pop-up screens when trying to play them, or, as Dolphin suggests, disable the MiG in them, 'cause it won't work anyway.

 

Thanks mate!

 

Cheers,

[hughlb]

Hi Dolphin887

 

I have sent a ticket to you with attached error file. I wasn't aware of this activation/deactivation process, and installed the update to 1.5 without deactivating. I now get the following error message:

 

"Unable to run the application due to integrity fault of the Activation Key. Re-enter a valid Activation Key or re-activate the application.

If the error recurs, click "Error report" and send the report to product technical support."

 

When I re-enter the activation key, it keeps coming back with this message. I can't deactivate or bypass this message.

[Wolf8312]

I have the same problem updated to 1.5.6 obviously without any idea this would be a problem! This is a very bizzare thing to be locked out of a module that I long since paid for! Really wish I'd just stayed on 1.5!

 

So what do I do now guys?

[razo+r]

I have the same problem updated to 1.5.6 obviously without any idea this would be a problem! This is a very bizzare thing to be locked out of a module that I long since paid for! Really wish I'd just stayed on 1.5!

 

So what do I do now guys?

 

Either follow the instructions in some pages before this page here or use the stable version

[nebuluski]

MIG 21-Bis Licensing error Public Release 1.5.6

 

This really has me pissed off now! I deactivated as requested in OpenBeta, saw I had three activations left. Updated OpenBeta, reinstalled Mig21-Bis, reactivated when asked and now when I start the Public release it says there is an error with Mig21-Bis licensing! I have three installs Public release, OpenBeta and OpenAlpha.

 

:mad:

 

I have asked you guys to sort my activations out on numerous occasions (23 Feb 16 and 23 Jul 16) in the past by email and no response back! Your customer service could be improved.

 

Moderators - I am being very, very restrained at the moment!

 

Guys sort your licensing out for the Mig21-Bis for Christs sake! I know you are trying, but as a loyal ED/DCS customer I am struggling to maintain my temper at the moment, I have every DCS Module there is, some I even have two licenses for!

 

No Further Comments will be made by me on this subject here!

 

Rant Over!

[Esac_mirmidon]

Keep flying the Mig-21 ONLY in Open Beta until Release and Open Alpha get patched.

 

Info over ¡¡

[Wolf8312]

This really has me pissed off now! I deactivated as requested in OpenBeta, saw I had three activations left. Updated OpenBeta, reinstalled Mig21-Bis, reactivated when asked and now when I start the Public release it says there is an error with Mig21-Bis licensing! I have three installs Public release, OpenBeta and OpenAlpha.

 

:mad:

 

I have asked you guys to sort my activations out on numerous occasions (23 Feb 16 and 23 Jul 16) in the past by email and no response back! Your customer service could be improved.

 

Moderators - I am being very, very restrained at the moment!

 

Guys sort your licensing out for the Mig21-Bis for Christs sake! I know you are trying, but as a loyal ED/DCS customer I am struggling to maintain my temper at the moment, I have every DCS Module there is, some I even have two licenses for!

 

No Further Comments will be made by me on this subject here!

 

Rant Over!

 

You have every right to complain!

[Redglyph]

This really has me pissed off now! I deactivated as requested in OpenBeta, saw I had three activations left. Updated OpenBeta, reinstalled Mig21-Bis, reactivated when asked and now when I start the Public release it says there is an error with Mig21-Bis licensing! I have three installs Public release, OpenBeta and OpenAlpha.

 

:mad:

 

I have asked you guys to sort my activations out on numerous occasions (23 Feb 16 and 23 Jul 16) in the past by email and no response back! Your customer service could be improved.

 

Moderators - I am being very, very restrained at the moment!

 

Guys sort your licensing out for the Mig21-Bis for Christs sake! I know you are trying, but as a loyal ED/DCS customer I am struggling to maintain my temper at the moment, I have every DCS Module there is, some I even have two licenses for!

 

No Further Comments will be made by me on this subject here!

 

Rant Over!

 

I don't know who you contacted back then, but things have changed since Leatherneck / Magnitude and Heatblur have reorganized. Have you tried to contact the support of Leatherneck directly (see first post)? They're very responsive and helpful.

 

In any case, as said before, you have to choose between the latest beta and the other branches for the MiG. Just deactivate it in the other branches until they are updated with the new licencing scheme. That way, you won't be bothered with the activation pop-up every time (but you won't be able to fly the MiG).

 

Or, if you look back some pages, several people explained how to go back and forth between beta and the other branches.

 

Not ideal right now, but for the best if that means no more problems in the future.

Edited April 2, 2017 by Redglyph

[Wolf8312]

So after deleting registary and rentering serial number all is well for me? So was this problem already fixed and patched then? Or are some just more unlucky than others?

[Esac_mirmidon]

Yes, but ONLY in Open Beta last update.

 

The only version updated with the necessary fixes for the Starforce copy protection is the Open Beta.

 

Next week i hope we will have 2.0.5 updated with the fix, and not to long after the Release 1.5.6.

 

The PDF attached in the first post is very helpful

[Redglyph]

Apparently the number of deactivations is limited too, so DO NOT SWITCH between versions, because even if your number of activations is preserved, you'll quickly run out of deactivations.

 

That's weird.

[Spectrum Legacy]

First, I would like to thank the team for this update and Starforce issue being resolved (at least for me) at long last since the very release of Mig21. In the past, each time I updated bios, or changed some of the northbridge/cpu related features like C6 states, Iommu/svm, RAM config, etc I would get flagged by Mig21's SF for changing hardware...

 

This behaviour is finally gone in the openbeta (on steam beta branch already since yesterday) - Cheers!

 

P.S. The instructions to deactivate and thus save one activation were pretty straightforward. I'm somewhat surprised that some are having issues with couple of pages long pdf, while as a community we are used to hundred of pages long elaborate manuals in DCS I would think...

[Alicatt]

Apparently the number of deactivations is limited too, so DO NOT SWITCH between versions, because even if your number of activations is preserved, you'll quickly run out of deactivations.

 

That's weird.

 

yeah, I'm now down to 3 deactivations left :(

[grunf]

yeah, I'm now down to 3 deactivations left :(

Zero here :D. I had to delete the registry keys because it wouldn't let me deactivate...

[Dolphin887]

Zero here :D. I had to delete the registry keys because it wouldn't let me deactivate...

 

We will check deactivations problem with the StarForce team.

[Chopper1987]

integrity fault of the Activation Key Error

 

how do I fix this "integrity fault of the Activation Key" error.

[sobe]

I am not going to read 21 pages of posts to figure out what to do. I followed the PDF when updating the openbeta and everything seems to be working. However, when I went back to my stable version, I was requested to activate the mig 21 and of course, it would not do so. So now if I want to fly the mig 21, I have to use the open beta and not my stable version. Will this ever end?

[splash]

This friday probably ED will release a patch for stable and/or alpha and you'll be able to play in those versions.

[Foka1]

I am not going to read 21 pages of posts to figure out what to do. I followed the PDF when updating the openbeta and everything seems to be working. However, when I went back to my stable version, I was requested to activate the mig 21 and of course, it would not do so. So now if I want to fly the mig 21, I have to use the open beta and not my stable version. Will this ever end?

 

I use open beta and can join servers which are on stable version...

[Sporg]

I am not going to read 21 pages of posts to figure out what to do. I followed the PDF when updating the openbeta and everything seems to be working. However, when I went back to my stable version, I was requested to activate the mig 21 and of course, it would not do so. So now if I want to fly the mig 21, I have to use the open beta and not my stable version. Will this ever end?

Then just read these two posts:

https://forums.eagle.ru/showpost.php?p=3097340&postcount=5

https://forums.eagle.ru/showpost.php?p=3098365&postcount=138

 

The point is:

Magnitude needed to update the DRM protection, StarForce, in order to solve the problems people have had with it.

 

However, StarForce applies activation to the whole PC, not only the version you are working in.

That means, when you activate or deactivate in one version, you do it for all versions of DCS present on the PC.

Sadly that also means, that if Magnitude changes DRM in one version, it affects all versions.

 

When Magnitude want to update the DRM, they would like to send out updates for all versions in one go, to avoid the problems we see now.

However, they need to wait for ED to send out updates.

And ED only sends out updates for one version at a time.

Magnitude has no influence on this process.

 

So that is why we have the situation we have now:

Magnitude has to send out updates to the DRM one version at a time.

They have now sent out the update to the 1.5 Open Beta.

 

That means that the users have the following options:

 

1. Deactivate MiG-21, update 1.5 Open Beta, activate and use Mig-21 in this version only!
   (do not use MiG-21 in 1.5 release or 2.0 NTTR, deactivate it in Module Manager in both versions)
   
2. Otherwise: Do not update 1.5 Open Beta.
   Keep using MiG-21 in 1.5 release and in 2.0 NTTR in its unpatched state.
   

We will get a similar situation with updates to 1.5 release and 2.0 NTTR, which will also be updated one at a time.

 

So, until all three versions are updated, you will have to choose whether to

 

1. update DCS version by version, not using MiG-21 in the unpatched versions.
   
2. continue using unpatched MiG-21, blocking update patches to the other versions
   

I hope this clarifies it a bit.

 

IMO, Magnitude is trying to fix the problem, but it means we will have to live with a transition period until all three versions have been updated.

 

In the mean time I would recommend that both ED and Magnitude clarifies these issues better to the costumers, in release notes and also in the pdf document, so that people have a better chance of realizing what is going on.

 

EDIT:

For those that already patched their 1.5 Open Beta without deactivating MiG-21 first:

In order to get MiG-21 to work in Open Beta, use the method described in page 8 in the Magnitude pdf.

I am not sure if you can get it to work in 1.5 release or 2.0 NTTR again after this.

(thanks to Esac_mirmidon)

Edited April 4, 2017 by Sporg