Having Activation or Re-Activation Issues? Read This!

[Airway]

Thank you very much. Very kind!

[Yurgon]

Thanks Cobra, great service! :thumbup:

[cichlidfan]

Thanks Cobra!

[Justificus]

5 New Activations have now been added to every serial number regardless of previous level.

 

The final fix for this issue will eventually require you to re-activate one final time. More information on that later.

 

Thank you sir! :thumbup::beer:

[FishDoctor]

THIS is great service! Thank you very much!

[mrmach]

Thank you but it's not enough...today I wake up with 7

Doesn't matter, evrytime I alternate between standard and beta it asks me for a new reactivation, so today I burn 5 activations... remaining 2 and not activated.

I have 6 more modules purchased and I haven't had any problem...:helpsmilie:

Cobra please, check your e-mail

[splash]

I uninstalled the module from 1.2.16 and, despite the mess I have in the registry, it is working flawlessly in 1.5.1 and it didn't request any more activation. So by the moment I have no problems to play MiG-21.

[mrmach]

export key reactivation mig 21 bis from . regedit :pilotfly:

Solved

I exported both activated reg keys, when I want to use either beta or normal versión I import the correspondent key and voilà...No more stupid activation inquires.

Thanks!

Edited November 16, 2015 by mrmach

[Esac_mirmidon]

Please, could you elaborate a little more to use this regedit fix?

 

Thanks

Edited November 16, 2015 by Esac_mirmidon

[mrmach]

Please, colud you elaborate a little more to use this regedit fix?

 

Thanks

It depends on your problem.

a.- If you are not able to actívate it.

b.- You can actívate it but when you change version to play (beta or normal) the game asks you for a reactivation...

[Esac_mirmidon]

Option b.

 

Thanks again.

[mrmach]

Option b.

 

Thanks again.

Go to this post http://forums.eagle.ru/showpost.php?p=2519855&postcount=102

It explains where to find de reg keys...

 

Ensure the version you have to backup (1.2.26 or 1.5.1b) is actually working.

Go to REGEDIT.exe export it and call it e.g Mig-21Bis_1.5.1.reg

 

Now go to the version which is not running and activate it via starforce.

After that, do the exportation again with REGEDIT. call it Mig-21Bis_1.2.26.reg or viceversa.

 

You will have two working reg keys , everytime the game asks you for a re-activation import the correspondent key and it will work fine.

Edited November 17, 2015 by mrmach

[jvanhoog]

Thanks for the extra activations LN!

[Esac_mirmidon]

Thanks mrmach, it works perfect now. Goo tip.

[openfalcon68]

Used the delete activation trick and key provided earlier by Nick to activate and get the MiG-21bis working in 1.5.1. Now left with 6 activations and no additional activations recieved.

 

But not an issue as you folks have rock solid tech support.

 

Thanks much

 

Manish

[sobe]

I am totally frustrated. I normally run 1.2 and 1.5 side by side. In the latest up for the Mig 21, I followed there special update procedure and now I have the following:

 

1. DCS 1.5 seems to work fine

 

2. DCS 1.2 will not start. All I get is the little box and then nothing. I have uninstalled 1.2 and just now reinstalled it with still the same results.

 

3. Some how I believe that the Mig 21 special program to delete lines in the registry must have screwed things up.

 

4. The end result is that I can only play on DCS 1.5. I guess that is better than nothing.

 

5. I do put some blame on the Mig 21 update procedure as that is the only thing I did to to 1.5 before 1.2 stopped working. I followed the below:

DCS MiG-21Bis

Note: It is recommended to manually update and follow these steps:

Cancel any automatic update prompt.

Deactivate module.

Delete all Leatherneck Simulations’ MiG-21Bis Windows Registry entries.

Execute manual update.

Restart Windows, and activate module.

If successful, users should not be asked to reactivate after future updates.

I am going to post this on the DCS forum in the hopes that someone has a good idea as to what I should do.

[tomcatter]

Did the update today following the instructions given by Cobra, all right on my side, the product is working, the activation process done and I have all my activations as it they should.

 

Thank you for your work, and for the fast response on the forums, awsome as always.

[Paco]

Lost activations on mig 21

 

Just upgraded RAM in prep for 2.0 and now mig 21 activation thing is rearing its head. Cobra, can I have my activations back, please. Will try working the fix, I had better learn it since I'm upgrading my video card as well and will most likely have to do this again. Hope it gets fixed.

[zaelu]

The instructions in first post are useless!

 

I am really out of words. This problems continues from patch to patch. LNS is getting lower and lower in standards by simply not fixing problems that stop users using the product. This makes the delay on so called news just look natural.

 

Keep it up LNS and people will make sure are buying your products only on heavy discounts.

Edited November 25, 2015 by zaelu

[Paco]

Problem is fixed. I followed the wiki instructions about midway in this thread. Tried the instructions from Cobra, downloaded the file but my awesome windows 10 wouldn't let me extract that file to the directory. Don't ask me, I just fly airplanes not program computers. Anyway, downloaded the wiki link file and that did it. I had to use an activation but have about 12 left, so I'm good. Hope the problem gets fixed.

[zaelu]

Problem is fixed.

 

Lucky you. I can't switch from 1.2.16 to 1.51 without Mig21 asking for activation.

 

They said last patch that just one activation will be lost and the problem is finally solved... is not. It's clear that unless ED steps in to force them to fix this they will just continue to pretend it is fixed and throw some reg files and let the user solve it.

 

It needs to be solved with an update without any fuss from user. No player is payed for this work.

[splash]

I deleted MiG-21 from 1.2.16 since the last patch and I have no intention at all to install it again. In 1.5.1 it is running ok by following the steps. I understand the need of some people to run it in 1.2.16. In my Ka-50 squadon, 1.2.16 is the standard and I have to fly with it.

[Cobra847]

Lucky you. I can't switch from 1.2.16 to 1.51 without Mig21 asking for activation.

 

They said last patch that just one activation will be lost and the problem is finally solved... is not. It's clear that unless ED steps in to force them to fix this they will just continue to pretend it is fixed and throw some reg files and let the user solve it.

 

It needs to be solved with an update without any fuss from user. No player is payed for this work.

 

 

Due to upgrading the protection system (aka - fixing the issue, as you so eloquently requested)

you cannot switch between 1.5 and 1.2.16 without reactivating the product.

The next time you opt into a BETA, please understand the risks and issues associated.

 

That is the only reason you are seeing multiple activations, and we are not lying when we say you only need to re-activate once.

 

We are currently working on an alternate set of 1.2.16 binaries that we can manually (no further updates to the 1.2.16 branch) distribute that may fix this issue until 1.2.16 is deprecated.

Edited November 26, 2015 by Cobra847

[zaelu]

Due to upgrading the protection system (aka - fixing the issue, as you so eloquently requested)

you cannot switch between 1.5 and 1.2.16 without reactivating the product.

The next time you opt into a BETA, please understand the risks and issues associated.

 

That is the only reason you are seeing multiple activations, and we are not lying when we say you only need to re-activate once.

 

We are currently working on an alternate set of 1.2.16 binaries that we can manually (no further updates to the 1.2.16 branch) distribute that may fix this issue until 1.2.16 is deprecated.

 

 

Why the other modules don't do the same thing? They use the same copy protection. Maybe you should spent more time talking with the other teams how they solved the problem instead of blaming the customer (for opting for beta... is beta for DCS World not Mig21 anyway) and bashing the same customer with negative rep.

 

Where is where it is said in what patch that opting for beta results automatically in burning activations when switching between versions?

 

You have a romanian in your team. Ask him what: "Ia-ti-o frinta ca ti-am dres-o" means. Describes perfectly your fixing.

[Cobra847]

Why the other modules don't do the same thing? They use the same copy protection. Maybe you should spent more time talking with the other teams how they solved the problem instead of blaming the customer (for opting for beta... is beta for DCS World not Mig21 anyway) and bashing the same customer with negative rep.

 

Where is where it is said in what patch that opting for beta results automatically in burning activations when switching between versions?

 

You have a romanian in your team. Ask him what: "Ia-ti-o frinta ca ti-am dres-o" means. Describes perfectly your fixing.

 

Because the other modules did not have a bug to fix -- prompting their development teams to implement a fix.

 

Respect is a two way street.

Edited November 26, 2015 by Cobra847