upgrade my cpu and now cant play :(

[blackturbo]

Hi all,

Iam so sad, I didnt know a simple CPU upgrade would cause all my modules not to load. Iam not too technical when it comes to the registry either so i dont understand what to do.

 

when i try to load dcs multiplayer, it comes up with each of my modules having errors, then gives me a chance to reactive them, then i do, and then after my dcs crashes.

 

somewon help please .

[blackturbo]

so, am I gonna have to put my old cpu back in lol, then deactivate all my modules, then put my new cpu in and reactivate them. i kinda dont wanna mess with that again.

[Psyrixx]

Have you tried opening up DCS Singleplayer? Does it still crash when reactivating modules?

[blackturbo]

yes it crashes in dcs world single player, when i try to play that module, it gives error saying i must retry, then i do, and it activates, then dcs crashes.

i guess i have to put in my old cpu huh. this is a nightmare

[Paganus]

I think there is a way to deactivate outside of the sim. Do a few searches you may find it. I'll take a look to see if I can also.

 

Look at the PDF attached to this post.

 

http://forums.eagle.ru/showpost.php?p=2536071&postcount=2

 

 

Good luck!

Edited November 12, 2015 by Paganus

[blackturbo]

ok ty, thats alot to go thru just for this, iam so mad now, iam just gonna put in my old cpu. iam cant find protect.exe

[Meiz]

I had a similar situation a few months ago. I don't think the protect.exe will work properly if you do it after a hardware change, but the A10c's for example is located at:

 

C:\Program Files\Eagle Dynamics\DCS World\Mods\aircraft\A-10C\bin

 

2 of my modules wouldn't reactivate after i put in my new CPU so what i was told to do is to go to here. These files basically delete the entries in the registry.

 

I couldn't save them properly so what i did was click into each one i needed and copied out the text, the a10c for example is:

 

Windows Registry Editor Version 5.00

 

[-HKEY_CURRENT_USER\Software\Eagle Dynamics\Warthog\Keys]

 

 

I then pasted the text into a new notepad file ( important to use notepad, i don't think other programs like word will work) and saved it as A-10.reg (important to include .reg after the name otherwise it saves as a text file that you can't run) . After saving it as a .reg file you can just double click on it and it will delete the registry entry for you (Would be best to make sure you have a list of your cd keys before doing this).

 

I would advise testing it out on 1 of your least played modules first then do the rest if it works for you.

Try at your own risk though, the best thing you could do is start a support ticket at the main DCS website.

Edited November 12, 2015 by Meiz

[cichlidfan]

Putting your old CPU back is not the solution. Reactivation all of your modules, before you try to enter multiplayer should work.

 

A CPU change exceeds the maximum number of points for a hardware change.

 

This should be covered in the installation guide for any of your modules.

[blackturbo]

ok well your right, puttin back in my old cpu didnt work. i put back in the new, deactivated every module, and reinstalled them. but its still not working

i guess what now, reinstall the whole game?

[blackturbo]

ok ty meiz for your instructions i will try them

[Meiz]

It was what the support guys at the DCS website told me to do after a new cpu + motherboard, hopefully it works for you as well.

 

At first i was getting the pop up boxes asking to activate the products every time i started DCS and i was unable to use them. After cleaning the registry with those files the activation actually worked for me the next time i started DCS.

 

But from memory i had to re enter the cd keys, so just make sure you know the CD keys first!

[blackturbo]

ok, Meiz had the info i was looking for, i didnt originally understand what do do with those files. all working good now xD TY for all who responded .

[Call911]

I had reactivation issue with the mig 21(nvr a crash) though manually copy n pasting the cd key after the initial failure an than clicking retry seemed to somewhat solve it. You might take a look at this thread might help..

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