Jump to content

Recommended Posts

Posted (edited)

Just updated to version 2.5.4.28615 tonight

 

I have tried deleting the config lua files in the following directory:

C:\Users\...\Saved Games\DCS.openbeta\Config\Input\FA-18C_hornet\joystick

 

The files are auto-generated once again. I re-set the axis to the correct ones but when I start the free flight instant action (or any mission for that matter) and attempt to use my throttles, I can see from the cockpit that the throttles do not move but the rudder pedals start to wiggle. The stick and pedals appear to actuate the correct controls but any axis bound to the throttle controls do not function.

 

This is easily reproducible from any mission. I have also seen this problem with the F-5E module

 

I use the TM Warthog stick and throttle, and Saitek rudder pedals.

 

If I jump into the F-14 module everything works normally. I also tried the F-15, A-10C, M-2000C module and they also work normally.

Edited by Maulkin

--Maulkin

 

 

Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars

Posted (edited)

Hello

 

 

I once had this problem with the warthog setup, I was told to make sure you are running DCS as administrator. I cleaned out all my joystick throttle pedals assignments including axis but NOT the KB assignments. Then I started over with fresh assignments and it was corrected.

 

 

Also make sure you are running you hotas male USB connectors on your system USBs rather than on stand alone USB extension.

 

Also I would get this Smart Utility that helps you see what devices are connected to your USB port within Windows Clean up old connections streamline your connections

 

 

https://downloads.tomsguide.com/USBDeview,0301-13254.html

 

 

 

I hope this helps

Edited by Phoenix_VMF257
Posted (edited)

I just tested the release version of DCS (version 2.5.4.27430) and I am not seeing this issue on any module there at all. So that eliminates the possibility that it is my hardware.

 

I cleaned out all my joystick throttle pedals assignments including axis but NOT the KB assignments. Then I started over with fresh assignments and it was corrected.

 

That is what happens when you delete all of the lua files I mentioned.

 

I also noted that some modules appear to be stuck in "game flight mode" where I have those arcade-like GUI elements on the screen even though that is turned off in my Options->Gameplay->Difficulties settings. But I am trying to only mention one issue at a time in this thread so I didn't bring it up. :)

Edited by Maulkin

--Maulkin

 

 

Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars

Posted

My issue was running DCS as administrator. If I didn't run DCS as an administrator and then delete Lua files or in my case clear out JStick assignments then I would be recreating the same issue over and over which I did until....:music_whistling: Also cleaning up USB assignments at the same time worked wonders for me...pilotfly.gif

Posted

To fix it I completely uninstalled the beta version, deleted the both the game folder as well as the saved game folder which contains configuration files.

 

Reinstalled.

 

Now everything appears to be working normally.

--Maulkin

 

 

Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars

  • Recently Browsing   0 members

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