1.5.3 Re-Activation

Pikey · February 18, 2016

I don't think people should get their knickers in a twist. LNS have always been up front about how they will help people through this issue that has admittedly been long standing. There seems to be a long standing misunderstanding how the activation system works that sends people into blind panic as if they just lost a finger.

Does anyone here really believe they will lose access to the Mig-21 moduleas a result of this error? If so, read more about what Cobra has done previously in these situations and Keep Calm.

Cobra847 · February 18, 2016

This issue should now be solved internally.

For those of you who decided to fly in 1.5.3 BETA-- run the registry fix here:

http://forums.eagle.ru/showthread.php?t=136153

And then re-activate as usual in either 2.0 or 1.5.3 Stable.

We will comp 2 activations instead of one.

Apologies for the inconvenience,

Thanks,

LS

Cobra847 · February 18, 2016

Attached below are hotfix binaries for those of you who wish to run 1.5.3 Beta today.

These are identical to the ones you'll see with 1.5.3 Stable.

Thanks,

Nick

x86_64.rar

Maulkin · February 18, 2016

Attached below are hotfix binaries for those of you who wish to run 1.5.3 Beta today.
These are identical to the ones you'll see with 1.5.3 Stable.

Thanks,
Nick

Where do I put them?

EDIT: Nm I figured it out :) :

C:\DCS World OpenBeta\Mods\aircraft\MIG-21BIS\bin

Edited February 18, 2016 by Maulkin

grunf · February 18, 2016

Attached below are hotfix binaries for those of you who wish to run 1.5.3 Beta today.
These are identical to the ones you'll see with 1.5.3 Stable.

Thanks,
Nick

Thank you! :thumbup:

Can I use this after I already activated the module in 1.5.3, to be able to run 2.0?

If yes, what's the procedure? Run the registry fix, then this hotfix and activate the Mig?

Cobra847 · February 18, 2016

Thank you! :thumbup:

Can I use this after I already activated the module in 1.5.3, to be able to run 2.0?

If yes, what's the procedure? Run the registry fix, then this hotfix and activate the Mig?

1.5.3 and 2.0 binaries should have parity with this hotfix.

So as long as you activated with these binaries active, the MiG-21 will work in both 2.0 and 1.5.X.

If you have activated on 1.5.2 or 2.0, you do not have to reactivate with this hotfix.

It's recommended you clean .reg before re-activation but it's not a must.

grunf · February 18, 2016

Works fine, thank you! :pilotfly:

fjacobsen · February 18, 2016

I re-installed the Mig-21 in 1.5.3 Beta, but will wait until after friday to activate the Mig-21 in 1.5.3 Release version and 2.0.

FinnJ

DieHard · February 19, 2016

Right, just started 1.5 beta after update, it wanted me to reactivate Mig21, ok no issue.
Closed beta down, started up 1.5, and that wanted me to reactivate Mig21, fair enough.
Closed it down and restarted 1.5 beta again to check something and it asks me to reactivate it again, slightly worrying.
Now after further checking whichever version of DCS 1.5 I open its asking me to reactivate Mig21 every time.
Used 3 activations already.
Its stopped asking me to activate it for 1.5 live version.

Ok so after further testing, if if I use Beta after 1.5 it asks me to reactivate Mig21. Then each time I use Beta as long as I dont start 1.5 live version it remains activated.
If I then start 1.5 live version I have to reactivate it, then it stays activated until I start 1.5 beta, and so on and so forth. Down to 6 activations from 10 now.
Can I have them back please.

Me, too! Same situation in the OpenBeta 1.5.3.50355 I think I used up two activations.

2.0 OpenAlpha did the process one time, seems to be OK, today, just the one time reactivating has sufficed. I used one activation.

I seem to be OK, currently 1.5.2.49392

I will give this a shot (see Message #1 top of this thread) :

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

http://forums.eagle.ru/showthread.php?t=136153

Edited February 19, 2016 by DieHard

Cobra847 · February 19, 2016

Right, just started 1.5 beta after update, it wanted me to reactivate Mig21, ok no issue.
Closed beta down, started up 1.5, and that wanted me to reactivate Mig21, fair enough.
Closed it down and restarted 1.5 beta again to check something and it asks me to reactivate it again, slightly worrying.
Now after further checking whichever version of DCS 1.5 I open its asking me to reactivate Mig21 every time.
Used 3 activations already.
Its stopped asking me to activate it for 1.5 live version.

Ok so after further testing, if if I use Beta after 1.5 it asks me to reactivate Mig21. Then each time I use Beta as long as I dont start 1.5 live version it remains activated.
If I then start 1.5 live version I have to reactivate it, then it stays activated until I start 1.5 beta, and so on and so forth. Down to 6 activations from 10 now.
Can I have them back please.

Down to 6 but it seems to work now...

Email at nicholas.dackard@gmail.com

Thanks,

Nick

humptydumpty · February 19, 2016

I went and updated to 1.5.3 from work as my home internet is very slow , did get an activation window but I did not activate. Now when the patch is public I will try it.

spiddx · February 19, 2016

aaaaaaand it's fixed! :)

February 19, 2016

I'm not complaining (since LNS has been really great at addressing these issues in real time), but I am just intellectually curious why the MiG-21 activation system is so different than the other modules. I have had DCS since the beginning, and only needed to burn a handful of activations with even my oldest modules. Every time I reformat my PC, I simply export the various registry keys to a file, reinstall Windows and DCS, and reimport the keys to avoid losing activations. The one module this never works for is the MiG-21, which seems to require a new activation every time (on top of the seemingly random reactivations needed for various updates/different versions).

I just don't fully understand what makes the MiG-21 system different than all the others. Again, it is not a problem given how responsive and generous LNS has been with crediting activations...

Rocky49 · February 19, 2016

so far this week I have lost 4 activations for this a/c. I really wish I did not support this developer because we keep encountering the same type of problems with activation, over and over. Not a big fan:(

Rocky49 · February 19, 2016

add another activation when going into DCSW2. This is after going through the steps to stop this crap Activation page comes up every time a open DCSW1.5 Beta

Edited February 19, 2016 by Rocky49

humptydumpty · February 19, 2016

Just updated and did not ask me for activation. All good it seems

Magot · February 19, 2016

Today updated by new patch and I was asked for NEW activation :(

Still its not fixed?

ST0RM · February 19, 2016

I'm having to activate it in both 1.5.3 and in 2.0 each time I start the sim. I'm not losing activations though. Just annoying.

IvanK · February 19, 2016

Just updated both the Open Beta and the Stable release version to 1.5.3.50487.

As soon as I started the Beta I again was asked to reactivate the MIG21 ... another activation lost (thats 2 in the last 2 days).So a recredit of 1 activation as leatherneck says is going to be added to all keys is not sufficient. Need a minimum of 2 recredits.

On updating the stable 1.5.3 the files were copied over from the Beta install. Did not have to reactivate the MIG21.

Cobra847 · February 19, 2016

Just updated both the Open Beta and the Stable release version to 1.5.3.50487.

As soon as I started the Beta I again was asked to reactivate the MIG21 ... another activation lost (thats 2 in the last 2 days).So a recredit of 1 activation as leatherneck says is going to be added to all keys is not sufficient. Need a minimum of 2 recredits.

On updating the stable 1.5.3 the files were copied over from the Beta install. Did not have to reactivate the MIG21.

We've already upped the number to 2 instead of 1.

We will implement the change tomorrow.

The persistent activation issue is not happening locally -- and may be unique to those who decided to run 1.5.3 Beta and upgrade from there.

For those of you who have this issue; can you try running 2.0 and see if you're prompted again?

Thanks,

Nick

MiG21bisFishbedL · February 19, 2016

Had reactivate, but hey I got 11 to go. That registry fix did it.

Rocky49 · February 19, 2016

Still happening in 1.5 Beta, even though mig21 module is showing installed. 2.0 is Okay now

This issue has cost me 5 activations.

Sokol1_br · February 19, 2016

Same here, other activation for 1.5.3 beta today update...

FSKRipper · February 19, 2016

Still happening in 1.5 Beta, even though mig21 module is showing installed. 2.0 is Okay now

This issue has cost me 5 activations.

Same here, other activation for 1.5.3 beta today update...

One question. Are you guys still using the Beta Client instead of the updated stable Client with 1.5.3 as I would assume from your postings?

Aufpassen · February 19, 2016

Hmm... I updated, I cleaned the registry with the reg-file, started the beta, activated and all is fine so far.

Then I fired up the alpha version. Huh??? Now I can't get into the cockpit of the Mig21.

Did a repair and still no go.

Before I bork another activation, any suggestions?

Sign In

1.5.3 Re-Activation

Recommended Posts

Pikey

Cobra847

Cobra847

Maulkin

grunf

Cobra847

grunf

fjacobsen

DieHard

Cobra847

humptydumpty

spiddx

Guest

Rocky49

Rocky49

humptydumpty

Magot

ST0RM

IvanK

Cobra847

MiG21bisFishbedL

Rocky49

Sokol1_br

FSKRipper

Aufpassen

Recently Browsing 0 members