Is it possible to have Mig-21 activated in DCS 1.2.16, 1.5.8 & 2.5.2?

Hello,

I was wandering if it possible (single PC, Win 10 x64 Pro) with 3 installs of DCS

- DCS 1.2.16

- DCS 1.5.8

- DCS 2.5.2

to have Mig-21 activated in all 3 instances? At the moment it is fine in 1.5 and 2.5 but in DCS 1.2 module gives me an error:

"Unable to run the application due to integrity fault of the Activation Key"

Thank you for your help.

You need to update to version number 1.2.10.32095 - first release for the MiG-21Bis.

Last version of 1.2. is 1.2.16.43180.

https://forums.eagle.ru/showpost.php?p=2346597&postcount=3

Hello mdw2,

Thank you for your reply. That is exactly the 1.2 DCS version I am running.

I am just worried that in my DCS 1.5 and 2.5 versions, Mig-21 is activated and all good, but DCS 1.2 on the same PC gives error "Unable to run the application due to integrity fault of the Activation Key".

If I activate Mig-21 in version 1.2, will it mess up other 2 DCS Mig-21 activations?

I have read here on this forum many posts people having quite a grief activating Mig-21.

If anyone could answer this, I would be most grateful.

Reading again, do I need to downgrade from DCS 1.2.16.43180 to 1.2.10.32095 to fly Mig-21 in DCS 1.2?

Solution for anyone wanting to fly their copy of Mig-21 Bis on the same PC in DCS 1.2.x, 1.5.4, and 1.5.8 and up - may help someone in the future: (Mig-21 Bis is the only module giving grief with activation on different versions of DCS on a single machine. All other modules once activated are fine in all versions of DCS.)

Mig-21 key is stored in:

[HKEY_LOCAL_MACHINE\SOFTWARE\Leatherneck Simulations\DCS:MiG-21 BiS]

You can save this key and import back - your Mig-21 key will need to be activated 3 times:

Separate activation for DCS 1.2.x

Separate activation for DCS 1.5.4

Separate activation for DCS 1.5.8 and up

The good news is after that key works all the way to OpenBeta.

You can do the following:

Activate Mig-21 in DCS 1.2.x

Export the registry key [HKEY_LOCAL_MACHINE\SOFTWARE\Leatherneck Simulations\DCS:MiG-21 BiS]

keep the export file

copy export file and name it something descriptive and unique, e.g.: reg-mig-21-dcs-1.2.reg

modify paths in the new copy of the reg file e.g.: [HKEY_LOCAL_MACHINE\SOFTWARE\Leatherneck Simulations\DCS:MiG-21 BiS DCS 1.2]

Import into registry

repeat for DCS 1.5.4

repeat for DCS 1.5.8 and above

you should end up with the following reg entries:

[HKEY_LOCAL_MACHINE\SOFTWARE\Leatherneck Simulations\DCS:MiG-21 BiS]

[HKEY_LOCAL_MACHINE\SOFTWARE\Leatherneck Simulations\DCS:MiG-21 BiS DCS 1.2]

[HKEY_LOCAL_MACHINE\SOFTWARE\Leatherneck Simulations\DCS:MiG-21 BiS DCS 1.5.4]

[HKEY_LOCAL_MACHINE\SOFTWARE\Leatherneck Simulations\DCS:MiG-21 BiS DCS 1.5 8 up]

Example of script which puts correct reg info into the registry store for the corresponding copy of DCS. For example, if you want to fly DCS 1.2.x Mig-21 Bis, you may want to run vbscript like this:

- code start

'Script to change registry activation information to suit DCS 1.2x Mig-21 Bis

set WshShell = CreateObject("WScript.Shell")

'Change registry activation information to suit DCS 1.2x Mig-21 Bis

strComputer = "."

'msgbox "Setting registry keys for DCS World Mig-21 Bis DCS 1.2x module..."

wscript.sleep 1000

WshShell.Run("reg copy ""HKEY_LOCAL_MACHINE\SOFTWARE\Leatherneck Simulations\DCS:MiG-21 BiS DCS 1.2"" ""HKEY_LOCAL_MACHINE\SOFTWARE\Leatherneck Simulations\DCS:MiG-21 BiS"" /s /f")

msgbox "Registry keys now set for DCS 1.2x Mig-21 Bis ..."

' Cleaning up...

Set Wshshell = Nothing

-code end

Thank you

I mean, do whatever you want to do, but exactly WHY are you running these jurassic versions of DCS in the first place?

I mean, do whatever you want to do, but exactly WHY are you running these jurassic versions of DCS in the first place?

Because they look, feel and fly better than the latest ones on my rig.

:)

Old game does not equal bad game. Cool graphics do not make a good game. Jursassic versions of DCS rule!!!

DCS 2.5x has awful light effects at night and it takes a long time to load.

Over and out.