jetski

I have noticed this as well, but additionally, if you are only using the single wheel brake toggle button, (and the rudder pedal axis for differential braking), the visual pedals work but differential braking does not. I mapped the left & right toe-brakes to separate joystick buttons and this works much better.

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.