Hat key not registering in control setup
-
Hi guys,
I have an issue where one specific hat on my TM Warthog throttle is not registered by the game. It is the coolie switch on the back of the right throttle, where my left index finger lies, and no matter what I try to map it to, the game doesn’t pick up any inputs. It’s a curious problem because every other input on the throttle is registered without fault. I googled the fault a little and came up dry, so if any of you know the solution I would be most grateful.
Diagram of the back of the throttle. It is the coolie switch causing me problems.
-
Only the POV on the primary controller (the one selected in the basic setup drop down menu) is available.The primary controller must be the same as contains the pitch and bank axes. Secondary controllers’ POV are either not available or defined to default action (pan view?). There is nothing you can do about it.
For me I run TARGET script for just the throttle (joystick excluded) which binds the coolie switch (CSU, CSD, CSL, CSR) to other DX buttons and not POV hat directions.
-
Have you used Targets Device Analyzer, the hat will show up as Buttons 22,23,24,25.
If you still fail to see any response then there is a chance you have a bad controller chip in the throttle.
If your running Target make shore there are no virtual keystroke inputs assigned to CSU, CSL, CSD, CSR. If there is, delete those items.
Then in your Falcon, Setup, Controller, Select “Thrustmaster Combined” (amusing Target is running) .
Now select your desired input in the Keyfile, it turns blue, then activate one of the hat switch position. ( I use it to control Bar scan, Tilt, Submodes/Azimuth ).
Best of luck.
-
Thanks for the feedback to the OP, i’m having the same issue.
It works fine if I use TARGET, but if not, as described.Kind of trying to eliminate TARGET, but maybe not at the cost of losing the throttle coolie switch…
-
Guys, try and crosscheck with available profiles (such as Morphine’s). Certainly helpd me out and indeed avoiding TARGET.
-
Guys, try and crosscheck with available profiles (such as Morphine’s). Certainly helpd me out and indeed avoiding TARGET.
Morpine’s does use TARGET. It’s a great profile, been using it for years.
-
TARGET is life. Always use TARGET.
-
Morpine’s does use TARGET. It’s a great profile, been using it for years.
True, I meant the GUI editor. I learnt to avoid keybindings through the TARGET GUI in order to avoid duplicate or overlapping binds. The more dx assignments, the better.