IMPORTANT MiG-21bis StarForce PATCH - MARCH 2017

That is not a bad idea: it will spare you from being spammed with SF dialog at Public.

 

Once the Public is patched, just install MiG - it should work right away.

OK, will do, thanks Dolphin.

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

No, no worries. Error report does not contain the key in any form. Even we don't know it, only the user knows it.

OK, thanks, better safe than sorry :)

As I only have beta, and 2.0 installed at this time, can I just merely uninstall the module and wait for future patches and avoid having to mess around with the PDF attached at the first post?

As I only have beta, and 2.0 installed at this time, can I just merely uninstall the module and wait for future patches and avoid having to mess around with the PDF attached at the first post?

You have to deactivate StarForce if you want to preserve one activation. After this I would recommend registry cleaning to prepare the environment for later patching.

After this, you don't really need to uninstall the module.

Instead, go to DCS->Options->Module manager->uncheck MiG-21 (deactivate the module within DCS) so it will be ignored when you use DCS. You have to do this for both DCS versions you have.

This is what I recommend, you have few more options.

On steam the update has not dropped yet did it? I want to play the mig again. I still have to use the steam version.

On steam the update has not dropped yet did it? I want to play the mig again. I still have to use the steam version.

Correct provided you did not manually edit update configuration. Steam is Public version (by default).

Hi Dolphin887, Thanks for the feedback and the updates to the MIG 21. I have ran the latest update, so is it safe to activate the module again. I apologize for the question, if I missed the answer elsewhere.

Thanks

FredM2002

Hi Dolphin887, Thanks for the feedback and the updates to the MIG 21. I have ran the latest update, so is it safe to activate the module again. I apologize for the question, if I missed the answer elsewhere.

 

 

Thanks

 

FredM2002

In Beta, yes.

If you have any problems write to our support@leatherneck-sim.com

That helped a lot,

very well written and easy to follow, thank you.

So I patched it before I saw this and broke it... Deleted the Mig-21 files to try and just fresh install like it was a new module and now it doesn't detect that I own it and I cannot download it in the module manager in open beta 1.5.6... Totally my fault and I apologize, is it salvageable?

So I patched it before I saw this and broke it... Deleted the Mig-21 files to try and just fresh install like it was a new module and now it doesn't detect that I own it and I cannot download it in the module manager in open beta 1.5.6... Totally my fault and I apologize, is it salvageable?

Make sure your delete your Leatherneck registry key (using "regedit" commadn in windows) as instructed in the pdf file and follow the instructions in that file. That should do the trick.

For some reason I forgot to delete my registry and the mig-21 pop-up asking me for my activation/deactivation of the module would never allow me to re-activate my key. Deleting the registry manually did the trick.

So I patched it before I saw this and broke it... Deleted the Mig-21 files to try and just fresh install like it was a new module and now it doesn't detect that I own it and I cannot download it in the module manager in open beta 1.5.6... Totally my fault and I apologize, is it salvageable?

Yes.

Please send us e-mail at support@leatherneck-sim.com with following details:

- which versions of DCSs you are running (exactly),

- print-screen of your Module manager/Installed page, with your MiG key visible, so we can check StarForce server side for details.

Don't post these here, send mail please.

So yeah... I missed this and updated DCS 1.5 open beta. Now what do I do? I can't deactivate...

I got it to work by deleting the registry key (with backup of course) at

HKEY_LOCAL_MACHINE\SOFTWARE\Leatherneck Simulations

and then re-entering the key to activate from scratch. This all happened after I got the latest update without deactivating the first time like it was suggested.

Thanks for the quick & good support for an activation problem.

Steve

PS: I did find Esac_mirmidon comments a bit abrasive :-)

I got it to work by deleting the registry key (with backup of course) at

 

HKEY_LOCAL_MACHINE\SOFTWARE\Leatherneck Simulations

 

and then re-entering the key to activate from scratch. This all happened after I got the latest update without deactivating the first time like it was suggested.

Yep works exactly! :thumbup:

I'm down to 0 keys now what?

Are you guys finally going to use same starforce setup than ED and others 3rd party ?

 

Vodka Squadron, which had quite some bad time with the mig, is very enthousiast about all the mig21 fixes we are seen everyday now :) :) :)

+1

This question has not been answered, yet!

OK I thought I had it sorted, but it appears I don't.

1/ I patched V1.5 beta before I knew anything about this Starforce problem.

2/ According to instructions in PDF and on this forum, I deactivated Mig-21 from V2 Alpha, tried to from V1.5 stable (but it said it was already deactivated) and from V1.5 beta by removing the entry in the registry.

3/ I then reactivated only in V1.5 beta and everything appeared OK.

4/ Today V2 Alpha was updated, and now even though I deactivated the Mig-21 I get the error message for the Mig-21 when V2 is starting.

I get the same error message when I try to start V1.5 stable.

Could someone please explain what I should do now?

Limited activations are a ridiculous idea if we are going to have to go through these issues! So we got two extra activations; the ways it's going I will be using more than that. I have already used 2 and 1 deactivation. I will still also have to reactivate in V1.5 and 2.0.

I get the same error message when I try to start V1.5 stable.

Could someone please explain what I should do now?

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.

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.

Is it the upcoming patch to 1.5.6.3690 (that we are waiting for) before we can reactivate the MiG-21 in 1.5? It says "the first update to DCS World version 1.5.6 to Open Beta" which suggests the stable 1.5 is being updated to Beta standard.

https://forums.eagle.ru/showpost.php?p=3096788&postcount=45

It says "the first update to DCS World version 1.5.6 to Open Beta" which suggests the stable 1.5 is being updated to Beta standard.[/url]

Precisely:

"DCS 1.5.6.3690 Update 1

To Open Beta at first."

which means, open Beta is updated with this patch.

If all goes OK after some time, the patch will be distributed to Public DCS. It might contain further fixes.

And when will the mig 21 update released on the release version?

And when will the mig 21 update released on the release version?

We don't know that at the moment. ED makes such decisions.

OK I thought I had it sorted, but it appears I don't.

 

1/ I patched V1.5 beta before I knew anything about this Starforce problem.

 

2/ According to instructions in PDF and on this forum, I deactivated Mig-21 from V2 Alpha, tried to from V1.5 stable (but it said it was already deactivated) and from V1.5 beta by removing the entry in the registry.

 

3/ I then reactivated only in V1.5 beta and everything appeared OK.

 

4/ Today V2 Alpha was updated, and now even though I deactivated the Mig-21 I get the error message for the Mig-21 when V2 is starting.

 

I get the same error message when I try to start V1.5 stable.

 

Could someone please explain what I should do now?

 

Limited activations are a ridiculous idea if we are going to have to go through these stuff ups! So we got two extra activations; the ways it's going I will be using more than that.

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.