jetski

I have now found another way of fixing this (probably better). that is to de-activate the module, then detlete it n the module manger, then go to the C:\Program Files\Eagle Dynamics\DCS World\Mods\aircraft folder and delete the remaining folder (and the faluty .dll.crypt files. When you re-install the module they are all cerated correcly and you can enter the cockpit.

I have found another way of fixing this (probably better). that is to de-activate the module, then detlete it n the module manger, then go to the C:\Program Files\Eagle Dynamics\DCS World\Mods\aircraft folder and delete the remaining folder (and the faluty .dll.crypt files. When you re-install the module they are all cerated correcly and you can enter the cockpit.

That made no difference. I am using Windows Defender and have never had any issues.

One thing to note with my fix (renaming the .dll.crypt files) is that to work, before renaming, the module must be "active". If not, then renaming the .dll.crypt files causes DCS to hang when launched (at the initial splash screen, before the main menue is reached). A possible cause of the issue is that I changed my account password at about the time that this problem surfaced, and if the DRM is insome ways linked to your username AND password then that could be a factor. I installed the AJS37 after I changed my password) and that has continued to bew flyable throughout.

one thing to note with my fix (renaming the .dll.crypt files) is that to work, before renaming, the module must be "active". If not, then renaming the .dll.crypt files causes DCS to hang when launched (at the initial splash screen, before the main menue is reached). A possible cause of the issue is that I changed my account password at about the time that this problem surfaced, and if the DRM is insome ways linked to your username AND password then that could be a factor. I installed the AJS37 after I changed my password) and that has continued to bew flyable throughout.

notably both repairing and un-installing and re-installing the modules does not affect the .dll.crypt files which seem to be causing the problem. Uninstalling a module leaves those files behind (I have not tried deleting them befor re-installing).

I had tried reparing, and un-installing and re-installing the relevent modules. it did not cure the issue.

I am using 'stable' 2.5.6.49798

I think that I have found a solution but don't know why it works.. also posted on the other thread. With faulty modules installed & enabled*, goto C:\Program Files\Eagle Dynamics\DCS World\Mods\aircraft\<module name>\bin and you should see both .dll files and .dll.crypt files rename the .dll.crypt files. e.g. "old_CockpitMi8.dll.crypt" and "old_Mi8.dll.crypt" The module in question should now be flyable...

I don't think AV is the problem. I think that I have found a solution but don't know why it works.. With faulty modules installed & enabled*, goto C:\Program Files\Eagle Dynamics\DCS World\Mods\aircraft\<module name>\bin and you should see both .dll files and .dll.crypt files rename the .dll.crypt files. e.g. "old_CockpitMi8.dll.crypt" and "old_Mi8.dll.crypt" The module in question should now be flyable...

I have this problem as well. After updating the stable relase to 2.5.6.49798, I found that I can ONLY access modules that have the old-style DRM (and the AJS37. I posted this https://forums.eagle.ru/showpost.php?p=4416922&postcount=5 So far, I have not found a solution either.

After comparing the errors in the log file with the installed modules, it seems that all modules without DRM have become unusable. (except the AJS37)Disabling and enabling the Mi-8 did not cure it and neither did deleting it an re-installing it. The same applies to the Mig-21. I have only disabled the other non-DRM modules except for the FW180-D and the Gazelle. this line in dcs.log looks suspicious: ALERT SECURITYCONTROL: Manifest 'mods/tech/combinedarms/dcs_manifest.x86_64' is from a different buildThe modules tab is now blank in the module manager. I think that this is linked to my previous post https://forums.eagle.ru/showpost.php?p=4360312&postcount=8 BUT what is weird is that I was able to fly the Mi-8 after that post until I installed the AJS37... dcs.log

dcs.log attached dcs.log

I recently purchased the AJS37 Viggen and have started the training missions, but when I tried The Mi-8MTV2 instant action mission I could not get into the cockpit of the Mi-8MTV2. When the mission had loaded I was presented with the Map view and could not take control, F1 did not work at all. The unit was listed as "player" RAlt + J did not allow me to take control. This seems to be the case for ALL non-AJS37 missions including training missions. Some missions seem to be in spectator mode with the player aircraft under AI control. The VR goggles option is un-ticked and there are no obvious settings. I have the non-beta version 2.5.6, and a "repair" has not fixed the issue.

After updating to 2.5.6 today, the modules page shows all are installed, however I have had to re-install almost all modules before I can see their missions and training lessons. Initially the modules were not showing as installable in the modules list in module manger, but they eventually all turned up and were installable. Thankfully the activations were not lost. This sim requires dedication - somtimes it asks for a little too much!!

I guess everyone is affected. It took me a while to work out as I first noticed it at Groom Lake with an FC3 plane, so had to see if it was the whole map (it was) or just the plane I was using (it wasn't) before I came here and found this thread.

I have had an issue with Track IR becoming disconnected in 1.5 for a while now. I cannot get it to re-connect except by restarting DCS. This is now happening in 2.1.1.9459 and is becoming very frustrating. All my USB hubs have the power "controlled by computer" setting disabled - no noticable improvement. I have a TrackIR 4 with TrackIR software version 5.4.2.27545. I don't get this issue with any other game (IL2 BOS, Rise of Flight, Cliffs of Dover)

If you choose a ramp start, you spawn inside one of the hangars and if you are a helecopter, that is bad as the KA 50 can only clear the doors if you get absolutely dead centre (that I didn't do on this occasion) Please can the ramp start spawn outside?

I have the "TrackIR unplugged" issue as well. I have experienced in DCS 1.5.x & 2.0.4 in many planes (including planes without the folders mentioned by SkateZilla). the only way of reconnecting trackIR is to restart DCS (Alt-Tab ing back and forth never restores) TrackIR is always still running OK. I have a Track IR4 with the TrackIR 5 software, a TM HOTAS Cougar and Saitek pedals and these carry on after TrackIR unplugs. This usualy happens about 12 - 20 minutes into a mission. I also have IL2 BOS and have not experienced this in that game.

So I can give it to my mate who has always been a Mac-head but might possibly be getting a PC this christmas and then will be able to enjoy 'proper' flight sims!

I have the same issue with thw A10 only (KA50 is OK) the problem seems to be the default zoom level - made worse by constantly resteeing to the defeult even after I have adjusted the zoom to something usable. playing with Track IR might cure the symptoms but not the causw wich seems to be a change since the latest patch. I can't identify which files might be the problem as all the obvious ones predate the latest patch.

Worked for my Win7 64bit Home Premium. I was getting the STTubeDevice203.dll not found error, and re-installing normally failed. but it was fixed when I used the Vista SP1 compatibility mode, and ran as administrator. JETSKI

In Options, Choose controls tab. Save the original control set as sometinh you can identify later. in categories, select axes commands (note this option is the ONLY place you can control axes asignation) make sure that any mouse axes WITHOUT key modifiers are deleted. (in my original set-up this was the absolute camera views) now all should be fine.... (and the mouse cursor still works in cockpit) Jetski

Hi Mugatu Sorted! The problem seems to have been my old version of MD5 summer...( http://www.md5summer.org/ ) the new 1.2011 beta calculates the proper values, as does the MS utility you recommended. (so the files WERE good all along!) Many Thanks, Jetski

Ok, after a manual virus check, I bit the bullet and tried to install, and... it workes fine! I have just gone through the first training missions! So I guess ED did update the files?? - or they are using a different MD5 calculation?! (endian-wise?)