Jump to content

Recommended Posts

Posted (edited)

Solution:

  • Avoid having buttons with an 'off' variant, it will bug out your controls

Report:

 

Bug:

  • There is an issue where my buttons just completely lock, including my HOTAS and keyboard, the only thing I could do was pause the game. This allows me to rescan the devices, which made it work again.
  • This only happens when I use a control on the HOTAS itself - nothing bad happens if I simply use my mouse and keyboard. This shouldn't be a lack of power issue, as this only happens when I use the F-14.

Reproductability:

  • Sometimes, it works just fine, but other times, it just does the bug. I'd say a 9/10 chance.

 

Other people say they have no issues with their HOTAS, so I'm assuming it's just either a bug with the F-14 or an incompatibility with my HOTAS. Here are my specs if you are interested:

Ryzen 9 5900x

2x Corsair Vengeance 32GB RAM (3600MHZ)

RTX 4080

Thrustmaster Hotas X (plugged into motherboard)

750W Gigabyte power supply

DCS installation on an SSD

 

  • Note - I have even tried to remap the controls entirely for the F-14 to ensure there were no conflicts, but it keeps happening. The RIO settings seem fine, but it only happens when I'm the pilot. I am also on the latest openbeta branch - 2.8.2.3579 (at the time of writing).

 

Thank you for your time.

- Ell

 

 

 

 

Edited by Elliot
Posted

Interesting. This has been happening to my Winwing throttle lately. I upgraded my PC recently, so I assumed it was an issue with a USB port or my USB HUB, but now you've got me wondering.

Rescanning devices works for me as well.

Posted

Silly thought.
You haven't by chance dedicated a switch/button incorrectly as a modifier, and have HOTAS sync enabled in the core settings?

Cheers!

Sent from my MAR-LX1A using Tapatalk

Posted
9 hours ago, MAXsenna said:

Silly thought.
You haven't by chance dedicated a switch/button incorrectly as a modifier, and have HOTAS sync enabled in the core settings?

I have dedicated 2 modifiers, but like I said, I've remapped the controls entirely to ensure no conflicts, and plus, it only happens in the F-14; no issues anywhere else.

IIRC, the synchronised setting is off for me, but I'll double check tomorrow; thanks for the heads up though. 

  • Like 1
Posted

Some USB conflict ?

In my case, when I have the Joystick USB plugged into the computer, the WIN 10 screen saver doesn't activate at all, just an example.

  • Like 1

          Jets                                                                         Helis                                                Maps

  • FC 3                              JA 37                               Ka-50                                             Caucasus
  • F-14 A/B                       MiG-23                            Mi-8 MTV2                                     Nevada
  • F-16 C                           MiG-29                      
  • F/A-18 C                       Mirage III E                                                         
  • MiG-21 bis                    
  • Mirage 2000 C

         i7-4790 K , 16 GB DDR3 , GTX 1660 Ti 6GB , Samsung 860 QVO 1TB

Posted (edited)
16 hours ago, Top Jockey said:

Some USB conflict ? 

Not that I know of, I double checked my controls and it has no conflicts, and the issue only happens in the F-14, not in the F-18 or SU-33 for me. 

 

Edit: I've noticed it seems to happen when I use the L2 (10) button on my HOTAS, I'll see if there's a conflict with that button.
Edit 2: It seems to have fixed; I had another modifier for the same button (off). Seems to be that was causing the issue.
 

           Moral of the story: avoid having 'off' variants of the same button, the only time you use it is with a switch.

Edited by Elliot
  • Like 1
  • Elliot changed the title to F-14 Control Issue (ISSUE RESOLVED)
  • Recently Browsing   0 members

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