All modules asking for activation codes after update to 1.2.3

[Thrakazog]

Hey all,

 

So, 1.2.2 would not update to 1.2.3 for me. I posted a thread on the problem, and the answers I got to fix the issue was to download 1.2.3 and all modules, uninstall 1.2.2, and install 1.2.3 in it's place.

 

My concern was having to use up activations, since after a few more updates, I would have to buy everything again. I was told it would not be a problem, and at first that seemed to be the case.

 

But every time I start one of modules (A-10c, P-51d, etc.), I get the window asking for my activation code. If I hit exit, the module continues to load, and everything appears to work so far.

 

I'm wondering if I just have to put up with the activation windows hounding me after the 1.2.3 update, or will using up my activations be the only way to stop it, eventually leading to having to re-purchase everything after a few more updates ?

 

Thank you for any suggestions on how to fix this.

[NoJoe]

Y'know, that happened to me too, and I had the same concern. But when I hit the activate button it said something about it using the previous activation or something like that.

 

Long story short, it didn't use up one of my activations, so you should be good to go to "re-activate". :thumbup:

 

--NoJoe

[Thrakazog]

Thank you for responding, NoJoe. I went ahead and entered my activation keys for all the modules, since I didn't see any other options to stop the windows from popping up. It actually didn't end up saying anything about activations used, one way or the other, so I'll just be happy the activation window no longer hounds me. Hopefully future updates go a little smoother. Looking forward to all the new goodies coming *cough* MI-24 *cough*, they all look great. :)

[crazyeddie]

Same problem, just returned to FC3 after a long break and every time I update from the server I loose an activation. Have no choice, the game will not run if I do not use one of my activations up.

 

Only been on DCS World a few weeks and I am now down to 7 already, and I'm not very happy with that.

[wess24m]

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

[EtherealN]

My concern was having to use up activations, since after a few more updates, I would have to buy everything again. I was told it would not be a problem, and at first that seemed to be the case.

 

Even if you were to run out of activations, all DCS World modules automatically get one activation back 30 days after the last one was used. Thus there will never be a need to repurchase, even if you do spend all activations. (And for older products, like BS1 and FC2, that do not have this automatic reimbursement, new keys can be issued free of charge through customer support if you run out.)

 

But every time I start one of modules (A-10c, P-51d, etc.), I get the window asking for my activation code. If I hit exit, the module continues to load, and everything appears to work so far.

 

I'm wondering if I just have to put up with the activation windows hounding me after the 1.2.3 update, or will using up my activations be the only way to stop it, eventually leading to having to re-purchase everything after a few more updates ?

 

Thank you for any suggestions on how to fix this.

 

Have you made any other changes to your system concurrent (roughly) with the update? For example, some antivirus suites implement "sandboxes" for programs they do not recognize, causing the simulator to see a "new computer" every time you start the game. In this case, it is also possible that the update to 1.2.3 caused said AV suite to no longer recognize the program and thus start sandboxing it. The fix for both is to tell the AV suite to not use it's sandboxing feature. Some suites indicate sandboxes through changing the border of a windowed program, but not everyone does so.

 

You can detect that the latter is happening through investigating your serial numbers(s) on this site: https://proactive.star-force.com/2.0/activate.php

 

Enter the serial number and then click the "Serial Number parameters" link. If the activation requests are actually listed there as "full" activations, this might be what is happening and I would suggest opening a support ticket so we can investigate and fix the problem. If they're not showing, then you're fine.