Jump to content

Recommended Posts

Posted

This probably isn't an ED F-16 bug (hence not for this sub-forum), as my Cougar throttle axis are still working.

Are the axis working/recognized in Windows?

Perhaps too obvious, but did you check the F-16 axis controls to see if you can (re-)bind the axis?

You might want to check or ask in this thread:

 

System specs:

 

i7-8700K @stock speed - GTX 1080TI @ stock speed - AsRock Extreme4 Z370 - 32GB DDR4 @3GHz- 500GB SSD - 2TB nvme - 650W PSU

HP Reverb G1 v2 - Saitek Pro pedals - TM Warthog HOTAS - TM F/A-18 Grip - TM Cougar HOTAS (NN-Dan mod) & (throttle standalone mod) - VIRPIL VPC Rotor TCS Plus with ALPHA-L grip - Pointctrl & aux banks <-- must have for VR users!! - Andre's SimShaker Jetpad - Fully adjustable DIY playseat - VA+VAICOM - Realsimulator FSSB-R3

 

~ That nuke might not have been the best of ideas, Sir... the enemy is furious ~ GUMMBAH

Posted

Check of all hardware is properly connected, I’ve had the same problem with the Thrustmaster F22 Pro and the problem there was that the cables were not properly connected. Another problem can be that the potentiometers are worn.

Ryzen 5 5600X, RTX 3070, Corsair RGB PRO 32gb DDR4 3600mhz, MSI B550 Tomahawk, Samsung 980 EVO 1TB, Meta Quest 2, F-16 HOTAS, Windows 11 Pro

  • Recently Browsing   0 members

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