Mig 21 Issues

mig 21 does not load since newest patch dated 2017-03-31

Skate:

It would have been helpful if these instructions would have been included in release notes

I am not amused! Now i got a licence for OB and not for Branche. Zero activations left. Wait for 30 days?

The activations around the module Mig 21 is giving me problems from the start!

When is this problem ever fixed!! :cry:

mig 21 does not load since newest patch dated 2017-03-31

Ditto!

Did this the last time (June 16, 2015) to fix it: https://forums.eagle.ru/showthread.php?t=136153

HERE : http://en.wiki.eagle.ru/w/images/f/f4/Mig-21_delete_activation_data.reg

http://en.wiki.eagle.ru/wiki/Problem_with_Activation

http://en.wiki.eagle.ru/wiki/Main_Page

Has this changed? Will this fix work? Or is it a new problem?

-+-

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

See Message #167 and #169, here : https://forums.eagle.ru/showthread.php?t=185325&page=17

-+-

UPDATE : April 7, 2017 StarForce Patch

=========================

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

concerning DCS April 7, 2014 Updates : https://forums.eagle.ru/showthread.php?p=3103700#post3103700

-+-

April 9, 2017

========

All 3 versions , Mig-21 updated nicely. See Message #11, this thread.

Same for me Updated Open Beta 1.5 then get presented with a dialog referring to an integrity issue with the activation key for the MIG21. Attempted retry and get presented with a second dialog box with my MIG21 activation key. Attempt to activate and I am returned to the original dialog box.

So then find the link above that talks about Deactivation. Attempted to deactivate wouldn't let me do it ... since it says I can only deactivate a valid activation key !!! .... since I guess I performed the update before deactivating the module ?

Next will try and do the offline deactivation. .... groan might be easier just to delete the module and be done with it.

This has occurred before with updates and the MIG21 module. Having to be aware of this issue BEFORE doing an update is not really acceptable. Asking for registry edits is not acceptable for an end user either.

@IvanK:

I had this exact same issue. What I would advise you to do is to go through the pdf guide attached in the first post of this thread: https://forums.eagle.ru/showthread.php?t=185325

The step I didn't do was the one called "Deleting product registry entries (skip in case of successful deactivation)". Failing to do this step caused a mismatch between starforce and my registry file.

I thought I could skip it since I assumed my deactivation was successful. WRONG. I think the "skip in case of..." part should be mandatory. Apparently, you have to do it no matter what (at least for me). Once I deleted the registry manually, I was finally able to re-activate my module for Open Beta 1.5. Follow steps 2a) through 2d) and you should be able to reactivate your license properly.

Moral of the story: When writing "you can skip this step if..." in a guide, one should assume that the user will inevitably go "har har I'm lazy, therefore I shall skip this step anyway". Even for experienced users like me.

It should not be nessesary to have to mess with regedit to make modules work for us users. Hope they will come up with a patch that will fix this automatic soon.

So I go into the registry and delete the Leatherneck entries as indicated in the PDF. All good reboot the PC then start the Open Beta. It requires me to activate my MIG21 module. Ok re activate. Then I can fly the Open Beta MIG21 all good.

Jump into the DCS World 2 Open Alpha ... during loading I get the integrity error message .... exactly as before.

Jump into the current release version of DCS same thing during loading I get the integrity error message for he MIG21 again.

So I can now run the MIG21 in the updated Open Beta but not in Open Alpha or the release version. I cannot deactivate it in the Open Alpha or Release version either.

Shambles Leatherneck what to do so I can fly the MIG21 in all 3 versions of the Sim ?

So I go into the registry and delete the Leatherneck entries as indicated in the PDF. All good reboot the PC then start the Open Beta. It requires me to activate my MIG21 module. Ok re activate. Then I can fly the Open Beta MIG21 all good.

 

Jump into the DCS World 2 Open Alpha ... during loading I get the integrity error message .... exactly as before.

 

Jump into the current release version of DCS same thing during loading I get the integrity error message for he MIG21 again.

 

So I can now run the MIG21 in the updated Open Beta but not in Open Alpha or the release version. I cannot deactivate it in the Open Alpha or Release version either.

 

Shambles Leatherneck what to do so I can fly the MIG21 in all 3 versions of the Sim ?

The update for Open alpha and release is coming today, you should then be able to fly the Mig in all versions.

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

It's easy...

1st - don't update anything yet.

2nd - download the reg file found in the post that grunf gave the link to.

3rd - merge the reg file that you downloaded from the link that grunf gave.

4th - start updating the versions you are running. Don't activate Mig 21 until all versions are updated

The first version you update will ask to validate the Mig 21, don't allow activation (you will probably have to exit that dialogue box twice)

The rest of the versions you have can be updated, but again don't allow the Mig 21 to be activated.

Once you have updated all of you installed versions (not allowing the Mig 21 to be activated)

THEN you can open a version up and activate the Mig 21, when you run the rest of your versions, you will probably find that they all have activated Mig 21's

It's easy...

1st - don't update anything yet.

 

2nd - download the reg file found in the post that grunf gave the link to.

 

3rd - merge the reg file that you downloaded from the link that grunf gave.

 

4th - start updating the versions you are running. Don't activate Mig 21 until all versions are updated

 

The first version you update will ask to validate the Mig 21, don't allow activation (you will probably have to exit that dialogue box twice)

 

The rest of the versions you have can be updated, but again don't allow the Mig 21 to be activated.

 

Once you have updated all of you installed versions (not allowing the Mig 21 to be activated)

THEN you can open a version up and activate the Mig 21, when you run the rest of your versions, you will probably find that they all have activated Mig 21's

I think the issue most people are having is that they didn't know they needed to deactivate MiG 21 before updating. Since I believe most of us probably run the auto-updater that launches every time we launch the game to stay up to date there is a pretty solid chance that the next time we play that is exactly what is going to happen. It seems there should be an easy way to either know before we update to deactivate MiG 21 or an easy way to get it to work after we update. I'm honestly not sure what goes into making this stuff work so I hesitate to get too critical or propose "sure thing" solutions. However, I will say that I have a fairly large stack of games that gather the virtual dust not due to how good (or bad) they are but due to how much work goes into getting them to run and keeping them running. I play games to relax, not get more stressed out. That's what work is for. I just really don't want to see any DCS modules winding up in that stack.

Agreed. Too many hoops to jump through, and the assumption that everyone reads every post in this forum before running the game each time.