Jump to content

Activation issues following Latest update


Crowman

Recommended Posts

Hi All

I recently followed the advice regarding the latest update for DCS world 1.5.6 regarding deactivation and reactivation of the Mig 21 module, this I did successfully on V1.5.6 unfortunately v2.0.5 now has issues regarding the Mig 21 now even though it had just be sorted prior to this 1.5.6 update. Any advice would be appreciated, I have several saved versions of DCS now following the recent problems.

Chilliblast, ASUS P8-Z77-V Pro, I7 3770K@3-5GHz, 16GB Corsair PC-3 12800 DDR3 @1600MHz, MSi GTX 1080 8GB, Creative SBZ, Logitech LT Z906 5.1, ASUS 24"Monitor 1080 60Hz,120GB SSD, 1TB SSD, 2TB HDD, 4TB HDD, Corsair CX 750W PSu, Win 10 Home Prem 64bit, TM Warthog, TM T Flight Pedals. Track IR, Occulus Rift S, Black Shark SA, DCS A-10C SA, All DCS Current Aircraft Modules, DCS 2.5 Stable and Beta.

Link to comment
Share on other sites

I'm not affiliated in anyway with M3 so take this for what it's worth... not much.

 

I assume that the fix has to be patched into the other versions.

 

So open beta got patched and is now fixed. After 2.0 is patched it will be fixed, and so on.

Link to comment
Share on other sites

Hi all

Quick update it affects release version as well, Oh well more testing to do!!

Chilliblast, ASUS P8-Z77-V Pro, I7 3770K@3-5GHz, 16GB Corsair PC-3 12800 DDR3 @1600MHz, MSi GTX 1080 8GB, Creative SBZ, Logitech LT Z906 5.1, ASUS 24"Monitor 1080 60Hz,120GB SSD, 1TB SSD, 2TB HDD, 4TB HDD, Corsair CX 750W PSu, Win 10 Home Prem 64bit, TM Warthog, TM T Flight Pedals. Track IR, Occulus Rift S, Black Shark SA, DCS A-10C SA, All DCS Current Aircraft Modules, DCS 2.5 Stable and Beta.

Link to comment
Share on other sites

Please, don't use MiG in unpatched versions (Alpha and Public) to avoid possible SF conflicts:

 

- once you deactivated MiG in Beta, it will deactivate in all the DCSs you have,

- patch the Beta, activate and use MiG in Beta.

- don't attempt to activate/deactivate again in Public and Alpha: They are ready to receive new patched MiG binaries once they are released.

 

We will attempt to arrange 2.0.5 MiG patch distribution next week. If we succeed, Public is next.

 

We apologize for this complication; we believe things will work much better concerning the SF once we are through the process.

 

Regards.

Power through superb knowledge, training and teamwork.

 

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

Okay my Mig-21 is totally broken, cannot activate cannot deactivate and all this due to curse word called Starforce? Back to times when DRM caused more problems than anything else for paying customers?

 

Thanks.

 

Which DCS version you are using?

 

Please send me PM for further instructions.

Power through superb knowledge, training and teamwork.

 

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

I've deactivated and reactivated it in ob, still says the key is invalid...

 

Provided that the procedure is correct, you probably have more than one failed deactivation in your registry.

 

Please delete the "Leatherneck Simulations" registry entry, and activate patched MiG in Beta.

 

You will get one extra activation.

Power through superb knowledge, training and teamwork.

 

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

Provided that the procedure is correct, you probably have more than one failed deactivation in your registry.

 

Please delete the "Leatherneck Simulations" registry entry, and activate patched MiG in Beta.

 

You will get one extra activation.

 

...

 

what i did:

 

patched ob

 

run ob -> mig invalid key

 

deactivated it in ob

 

activated it in ob -> didn't work

 

deleted the LNS in the regedit

 

activate mig in ob -> not working

 

anything i've missed?


Edited by razo+r
Link to comment
Share on other sites

You were suppose to deactivate first, before patching.

 

Run the command prompt and run dcs_updater.exe update 1.5.6.1938 to get the 1.5.6.1938 bin files.

 

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

 

Next, delete the registry entry, update DCS again and reactivate.

https://magnitude-3.com/

https://www.facebook.com/magnitude3llc

https://www.youtube.com/@magnitude_3

i9 13900K, 128GB RAM, RTX 4090, Win10Pro, 2 x 2TB SSD

i9 10980XE, 128GB RAM, RTX 3090Ti, Win10 Pro, 2 x 256GB SSD, 4 x 512GB SSD RAID 0, 6 x 4TB HDD RAID 6, 9361-8i RAID Controller

i7 4960X, 64GB RAM, GTX Titan X Black, Win10 Pro, 512GB PCIe SSD, 2 x 256GB SSD

Link to comment
Share on other sites

Have the same problem and downloading the 1938 files again.

Would be nice if this sort of info would also be stated in the ED patch notes. And even better if this would be triggered as a warning at the start of the DCS update: "Please deactivate your MiG21 first before proceeding with this update".

Link to comment
Share on other sites

nice, the info about that was in a hidden thread that i just found now...

 

but thanks for the effort...

 

also, When i start ob, the updater comes first, before i'm able to deactivate it in ob so... might also be a factor to consider

Link to comment
Share on other sites

Please, don't use MiG in unpatched versions (Alpha and Public) to avoid possible SF conflicts:

 

- once you deactivated MiG in Beta, it will deactivate in all the DCSs you have,

- patch the Beta, activate and use MiG in Beta.

- don't attempt to activate/deactivate again in Public and Alpha: They are ready to receive new patched MiG binaries once they are released.

 

We will attempt to arrange 2.0.5 MiG patch distribution next week. If we succeed, Public is next.

 

We apologize for this complication; we believe things will work much better concerning the SF once we are through the process.

 

Regards.

 

I just tried reactivating the mig 21 in alpha prior to reading this warning. Will that mess things up once alpha gets patched?

Link to comment
Share on other sites

What happened? I had to uninstall and reinstall it completely? Why the name change from Leatherneck to Magnitude 3 LLC? Leatherneck was way cooler. Also is the F-14 dead?? I thought it was going to be done by Leatherneck.

Link to comment
Share on other sites

OMG, I did not know there was a problem and updated my DCS now I cannot deactivate the Mig 21. It shows errors when I start DCS.

This is really bad for me. I am like a total noob with the command line. If I reinstall windows from scratch and reinstall all DCS from scratch will that fix it?

 

Update

I did the cmd line and de activation did not work. I removed it from the registry. restarted the computer. started DCS ran the activation without updating DCS and it worked. After I tested it for a while I rean the de activation and that worked. I am just leaving it deactivated until I hear more on the patch or whatever. It is way to confusing to me.


Edited by tusler

Ask Jesus for Forgiveness before you takeoff :pilotfly:!

PC=Win 10 HP 64 bit, Gigabyte Z390, Intel I5-9600k, 32 gig ram, Nvidia 2060 Super 8gig video. TM HOTAS WARTHOG with Saitek Pedals

Link to comment
Share on other sites

Update

I did the cmd line and de activation did not work...

 

What exactly did you do in the command line?

https://magnitude-3.com/

https://www.facebook.com/magnitude3llc

https://www.youtube.com/@magnitude_3

i9 13900K, 128GB RAM, RTX 4090, Win10Pro, 2 x 2TB SSD

i9 10980XE, 128GB RAM, RTX 3090Ti, Win10 Pro, 2 x 256GB SSD, 4 x 512GB SSD RAID 0, 6 x 4TB HDD RAID 6, 9361-8i RAID Controller

i7 4960X, 64GB RAM, GTX Titan X Black, Win10 Pro, 512GB PCIe SSD, 2 x 256GB SSD

Link to comment
Share on other sites

Since I updated DCS before I knew there was a problem I found this post and did this from:

https://forums.eagle.ru/showthread.php?t=185396&page=2

-Rudel-

 

You were suppose to deactivate first, before patching.

 

Run the command prompt and run dcs_updater.exe update 1.5.6.1938 to get the 1.5.6.1938 bin files.

 

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

 

Next, delete the registry entry, update DCS again and reactivate.

 

Only when I went to update DCS again it said I have the latest update installed. I think from searching the forums I have the release version? any way I went through the activation and it worked, I tested it and de activated it incase I need to patch it ( I am clueless).

When I tried to deactivate at first by following the thread from Opening a command prompt:

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

I could not get the deactivated to work so I deleted the registry entry and did it that way.

Ask Jesus for Forgiveness before you takeoff :pilotfly:!

PC=Win 10 HP 64 bit, Gigabyte Z390, Intel I5-9600k, 32 gig ram, Nvidia 2060 Super 8gig video. TM HOTAS WARTHOG with Saitek Pedals

Link to comment
Share on other sites

Go to your install directory and open up autoupdate.cfg

 

Do you see the line?

{
"WARNING": "DO NOT EDIT this file. You may break your install!",
"branch": "openbeta",
.....

 

If not, you have release version, and will need to wait for ED to push the update for Pulic Release version.

 

The patch is for openBeta

https://magnitude-3.com/

https://www.facebook.com/magnitude3llc

https://www.youtube.com/@magnitude_3

i9 13900K, 128GB RAM, RTX 4090, Win10Pro, 2 x 2TB SSD

i9 10980XE, 128GB RAM, RTX 3090Ti, Win10 Pro, 2 x 256GB SSD, 4 x 512GB SSD RAID 0, 6 x 4TB HDD RAID 6, 9361-8i RAID Controller

i7 4960X, 64GB RAM, GTX Titan X Black, Win10 Pro, 512GB PCIe SSD, 2 x 256GB SSD

Link to comment
Share on other sites

Go to your install directory and open up autoupdate.cfg

 

Do you see the line?

{
"WARNING": "DO NOT EDIT this file. You may break your install!",
"branch": "openbeta",
.....

If not, you have release version, and will need to wait for ED to push the update for Pulic Release version.

 

The patch is for openBeta

 

Yes I do have that line in the autoupdate.cfg file.

Ask Jesus for Forgiveness before you takeoff :pilotfly:!

PC=Win 10 HP 64 bit, Gigabyte Z390, Intel I5-9600k, 32 gig ram, Nvidia 2060 Super 8gig video. TM HOTAS WARTHOG with Saitek Pedals

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...