Stonehouse Posted October 1, 2015 Posted October 1, 2015 (edited) Hoping for a solution or some assistance. I've just got the latest 1.2.16 beta of DCS world installed and wanted to get it all the modules up and running ready for 1.5. However I've run into a problem with the Mig21 in that my module manager lists this as "No key". I understand this to be because I got the Mig21 through the original kickstarter and not via Eagle Dynamics. Therefore I cannot use module manager to update the beta install. I have downloaded the latest exe from the ED store however when I try to run it against the beta install I get a version mismatch error. Any workarounds or solutions please? Thanks, Stonehouse PS Confusingly the versions of the two installs match 1.2.6.43180 which is also what the installer for the new d/l of Mig21 is asking for Edited October 1, 2015 by Stonehouse
Vitesse2l Posted October 1, 2015 Posted October 1, 2015 Daft question - Do you have the key in your main DCS module manager? There is a choice to enter the key manually in the Starforce activation. I just reinstalled DCS (kickstarter backer too) and it picked up my key for the main release ok. There I was frantically looking for my email from cobra but I didn't need it. Good job 'cos I had a motherboard die and jiggered my win 7 install trying to resurrect it.
Stonehouse Posted October 1, 2015 Author Posted October 1, 2015 (edited) No in the main DCS module manager it appears as "No Key" but it is activated. I also just for the hell of it ran the copy of the Mig21 module I just downloaded hoping to fix the beta against my main install and it went in fine and didn't ask to be activated - so assume there is no key related issues in my main install. I just cannot run the installer against the beta because it says it requires 1.2.16.43180 - which is what is there according to the beta splash screen. <edit> ok I just saw another person post that they are going through the same exercise but that when updating their beta via module manager they had some sort of issue with A10C so they downloaded the module from the store and tried to manually install it and got the version error message I got. So there must be something subtly different beyond version number between a beta install and a normal one that the modules check for. If that is so then the kickstarter Mig21 owners might need help to install it under the beta. Edited October 1, 2015 by Stonehouse
Vitesse2l Posted October 1, 2015 Posted October 1, 2015 (edited) I see... Have you tried to deactivate (may not be a good idea!)? edit - meaning deactivate and reactivate through the starforce dialog which *may* display the key for you. Sounds like there's an issue, though, if others have the problem too. Edited October 1, 2015 by Vitesse2l
Stonehouse Posted October 1, 2015 Author Posted October 1, 2015 Hmmm think I see where you are heading although it would probably mean I would need to reinstall the beta and modules again to "pick up" the fact that Mig21 had a key if it does work like that. Not sure I want to do it yet as I had trouble getting the Mig21 activated at the beginning and had to get some assistance from Cobra at the time.
Vitesse2l Posted October 1, 2015 Posted October 1, 2015 Perfectly understood. It's probably best to wait a while, really. I always have the urge to try stuff (which is how I tend to learn) but it's usually better to be patient. Cobra is pretty good with helping. I'm sure he'll sort out any problems.
Stonehouse Posted October 1, 2015 Author Posted October 1, 2015 OK had success thanks to the info on the other post. This thread is worth subscribing to http://forums.eagle.ru/showthread.php?t=114030
Vitesse2l Posted October 1, 2015 Posted October 1, 2015 Good news. Reading that thread reminds me that once upon a time I used to get excited about a new MS DOS release!
Stonehouse Posted October 1, 2015 Author Posted October 1, 2015 Yeah I can remember Win3.11 coming out too.......doesn't time fly by
Recommended Posts