IMPORTANT MiG-21bis StarForce PATCH - MARCH 2017

[splash]

That message about "demo mode" is normal because you have your MiG-21 license deactivated. Sometimes I forgot to activate some new module and I received the same message. I simply press exit and continue.

[-Rudel-]

I dont have access to my simming pc at all which is in another country but I do have my mig-21 key. Help?

 

When you do get home, simply deactivate it, before double clicking the icon to start the game.

[Cnuke]

I checked beforehand my number of activations at the Starforce page . I deactivated the module correctly (succes) and to my suprise I lost again 1 activation instead of getting 1 back at the starforce page.

 

Can you look into this please, after patching ??? (Coz that process is faulty)

 

And ofcourse deactivations goes down 1 as well (but thats expected)

 

 

Anyway I hope the problems are solved soon after the patch. Thanks for your efforts of fixing this!

[klem]

Thank you Dolphin.

 

However I was left with 6 activations (IIRC) which will go to 8 I hope, and the deactivation told me I have only 3 de-activations left. Shouldn't they be the same number?

 

In fact why don't you just reset all activations to the full number?

 

Is there any reason why I should not deactivate in ver 2.0 now? I think all my modules activated autoimatically when I loaded ver 2.0. Doesn't 1.5 set up 2.0?

Edited March 31, 2017 by klem

[splash]

Same problem here. After deactivation I received a message saying "Deactivations left: 3".

[Esac_mirmidon]

Activations and deactivations are different things. 10 for the first 5 the last i think

[splash]

OK. I patched and activated and now I have 9 activations left. No problems flying MiG-21 in Openbeta so far.

[-Rudel-]

The latest 1.5.6 Update 1 patch is not released yet.

[absolut79]

UPDATE ALREADY STARTED. I DIDNT KNOW THAT I HAVE TO DEACTIVATE IT BEFORE

[cichlidfan]

Activations and deactivations are different things. 10 for the first 5 the last i think

 

No. You started with 10 of each.

[grunf]

The update and reactivation seems to went well, even though I had to delete the registry keys (0 deactivations left - hope that can be replenished, I've sent you guys an email to support). I still have 11 activations.

 

Hope this will solve all the activation issues once and for all. Thanks guys :thumbup:

[Reflected]

If I fail to do this, just let the updater do its job, then I'll lose one activation, but that's it, right?

[klem]

UPDATE ALREADY STARTED. I DIDNT KNOW THAT I HAVE TO DEACTIVATE IT BEFORE

 

Deleted:

 

Update not released yet

Edited March 31, 2017 by klem

[ruddy122]

Hi Guys,

 

Long story short I installed DCS 1.5.6 before deleting MiG21Bis resulting in Activation Key Issues.

 

 

I tried everything in the PDF file provided, but still having Starforce Activation Problems. I even tried to delete the key from the windows registry manually but did not work.

 

I attached the error report (It's pretty big had to somehow save it as a PDF) and deinstalled MiG21Bis from 1.5.6. Completely confident this will get resolved soon. Keep up the good work, hopefully its a simple fix

 

Cheers,

 

Lucky

Error Report.pdf

[-Rudel-]

You will need to run the command prompt and run dcs_updater.exe update 1.5.6.1938 to get the 1.5.6.1938 bin files.

 

https://forums.eagle.ru/showthread.php?t=114030

 

Next, delete the registry entry, update DCS again and reactivate.

[ruddy122]

Thank you for the quick reply

 

I updated DCS and deleted the key files

 

I'll let you know if it worked

 

So far so good

 

 

Sent from my iPhone using Tapatalk

[ruddy122]

Worked exactly like you said

Well Done!!

 

 

Sent from my iPhone using Tapatalk

[CoBlue]

In short, in order to save one activation for MiG-21Bis, you will have to deactivate the module BEFORE the DCS 1.5.6 patch is downloaded to your PC. We advise you to do this in next 24 hours.

LNS

So I don't have to do this, if I don't care about loosing 1 activation, right?

It will be taken care of automatically when 1.5.6 Stable updates?

[Redglyph]

Hum, this would have been a relevant info in today's changelog thread, too bad ED didn't mention that.

[-Rudel-]

So I don't have to do this, if I don't care about loosing 1 activation, right?

It will be taken care of automatically when 1.5.6 Stable updates?

 

You need to deactivate because of the new StarForce bindings. If you have done the procedure for openOpen, you wont have to do it again for the stable release or 2.0.5 when the next update occurs.

 

Until then, do not run the stable release or 2.0.5 if you have updated openBeta with the procedure.

[Redglyph]

You need to deactivate because of the new StarForce bindings. If you have done the procedure for openOpen, you wont have to do it again for the stable release or 2.0.5 when the next update occurs.

 

Until then, do not run the stable release or 2.0.5 if you have updated openBeta with the procedure.

 

Good to know, thanks.

 

But does it mean that, if someone has done the procedure to run 1.5.6 update 1, it has to be done again to switch back to 2.0.5, or in fact every time the user switches between 1.5.6 update 1 and 2.0.5?

[-Rudel-]

Before 2.0.5 is updated again....yes :(

[Rocky49]

This would have been more helpful if listed in release notes! I have spent too much time on the sf issues with this module over the years!!!

[R1Lawsy]

Um, so i patched before reading... got an error in the beta...

Deleted reg keys, re-activated - good to go...

Now there is an error activating in the Alpha - what do i need to do to re-activate the Mig in the Alpha?

[Jem7]

yes it wont activate in 2.0.5.3521 even with the latest Starforce Protection Malfunction Update any ideas?

 

I have it working fine in 1.5.6