Thrustmaster weirdness
-
Hello,
I posted a few weeks ago having trouble with the initial setup on my Thrustmaster T16000M and TWCS throttle. I mostly figured out the stuff I was stuck on, and was off and running for a bit. Now having some inexplicably weird behavior: some of my buttons don’t do anything in the cockpit, even though they are properly set up to do so (in TARGET).
Specifically, I have a joystick button for MSL Step/NWS. Mainly to switch from CCRP to CCIP without reaching for the mouse. The BMS UI (outside cockpit, on the control config screen) recognizes this - when I press that button, it displays that MSL Step was entered, on the control config UI. But in the cockpit it does nothing. Similarly, my DMS down does not switch the SOI like it’s supposed to. The control UI sees it, but in the cockpit, it causes the sim to emit a click/pop sound, but does nothing else. If I press the keyboard command for that function, it works (the Thrustmaster button is programmed to simulate that same key press).
A possibly related issue I haven’t been able to solve is that I can’t get the gun trigger to work right. If I set the TARGET software for it to mimic a ‘press,’ it fires a momentary burst for each trigger pull of any length, but if I set it to ‘hold,’ tapping the trigger fires continuously until ammo is gone.
Is the TARGET software just glitchy and weird, or am I doing something wrong? Would really appreciate any help with this.
-
Both. Using the TARGET software IMO constitutes doing something wrong XD
More seriously, if you remap the keyfile and profile to not use shift, ctrl or alt modifiers, that should solve your issues. TARGET is probably getting a modifier stuck somewhere which will screw up all your keypresses through there.
Alternatively, eschew TARGET entirely and map the DX buttons of the stick directly to BMS callbacks in setup. That way, no modifiers to get stuck in the first place.
-
Alternatively, eschew TARGET entirely and map the DX buttons of the stick directly to BMS callbacks in setup. That way, no modifiers to get stuck in the first place.
+1, whenever possible use DX. Saved me no end of heartache.
-
I use Target for anything that is not dx friendly, and dx for all the main functions, that is with the warthog though. you can set the dx command within target.
-
First instinct is to avoid the keyboard emulation method entirely. If you must emulate keyboard presses make all efforts for them to be simple key presses (e.g. “A” instead of “Shift-A”) as joystick profiling software doesn’t reliably get the timing of the sequence of press and release on the two-or-more keys right. The trigger wants a “press” type action as hold is just the key down input and those keys would stay in the down state until explicitly put in the up state.
-
i’ve tried both methods, combine through TARGET creates discrepancies, EX: rotation X, and X axis, throttle seen as duplicate as X axis of t.16000m…So I tried direct, but axis assignments in advanced get screwed up when switching, are not registering at all.
I guess I’ll wait on it, any insight would be greatly appreciated, really want to whet my teeth. ARRRR
-
As I know TARGET “combine” means to create a virtual controller replacing (and hiding) the existing 1, 2, 3, 4, etc. logical controllers. “Direct” would be TARGET not doing that and the same behavior as if TARGET was not running at all. TARGET also has the ability to selectively combine some controllers and leave others direct. E.g. in my Warthog setup my joystick device is direct and the throttle is combined (a combination of one device, laugh) and that’s how I apply programming to the throttle controller.
Can you make your joystick output something simpler (simple key or just a plain button) and then bind that, ignoring/replacing whatever crazy Crtl-Alt-Shift-PageDown default keybind comes with the supplied files, and does that work?
-
I’m tracking you and I have applied your wisdoms, thank you. Got the HOTAS set, working out an IR theatre occulus rift pov tracking quandary now. Looks promising! Much appreciated
