Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
For your info, currently i have connected.
ThrustMaster Warthog Hotas
Thrustmaster MFDs x 2
Crosswind Rudder Pedals
Jetseat
TrackIR
I have disconnected all instruments which were all the Saitek flight panels.
I think the Issue may be the X axis with the Crosswind Rudder pedals, as i can control which direction the cursor scrolls by different pressures on the pedals
The MFG Crosswind rudder pedals (like most current rudder pedals) feature 3 DirectX axes: yaw, left toe brake, right toe brake.
The toe brakes rest in the maximum (or minimum) position, so that's likely a culprit. However, the TM Warthog throttle also features two throttle (aka thrust) axes and a slider axis, all of which may have a resting position well outside of the center position.
Devices like the TM Warthog throttle also have 2- and 3-position switches that may have a resting position outside of center, so they would keep on sending the DirectX "button 1 is pressed" event all the time, even though the player doesn't actually depress the button.
It's quite common, and quite unfortunate, for video games to accept each and any HID controller plugged into the PC and accept one or all axes as input for the game.
There are probably many ways to skin the cat. Some ideas:
- check controller device names and ignore everything besides a few select ones, that is: only accept "Xbox controller", "Steam controller", "PS4 controller" and so on as valid input devices
- ignore every axis that is not centered while the game starts up
- ignore every button that is already depressed while the game starts up
- add menu options to enable/disable individual controllers
I'll be glad to provide additional information to help you guys find a solution.
Then again, most games don't have this problem, so I'm sure there will be solutions by other game developers, possibly also for the tools/platforms that you're using, and they're probably all smarter than the above list of ideas. ;)