I have spent hundreds of dollars in Star Citizen and a lot of money in Elite Dangerous because I'm able to use my Thrustmaster Warthog, MFD's, dual t1600m's, pedals, and stands. Mechwarrior doesn't even identify the T.A.R.G.E.T. software. It's so janky. I preordered this game and now i never play it. Do you think I want to pilot a mech with a keyboard like I'm some ****? I'm a grown man.

No amount of HUD mods or enemy spawn fixes are going to fix your lack of joystick support. I don't even think I can edit your files to support the Thrustmaster software and anyways why would I even try since I can just go play games with actual, legit support for HOTAS, etc.

I think I'm going to try to set all my axis to throttle 5 and then see if I can use T.A.R.G.E.T. to bind to pure keyboard keybinds. The goal is to have dual sticks. If I want to use a HOTAS, it will let me. But if I want to use all custom buttons with dual sticks, then it won't. It combines the sticks on the same axis, even if T.A.R.G.E.T. has them setup on different axis. I'm going to see if I can use T.A.R.G.E.T. to simply press keys on the keyboard and drive the mech the way I want: left stick for the legs, right for the body. I think that might actually work. I'll have to see. I'll try to report back with something positive if it does work.

Now for more negative: this game doesn't support Track IR? And obviously no VR. Yikes. These things should be standard on modern triple simulator-type games from publishers.

I still don't see how to get MW5 to recognize the T16000m's axes once TARGET is active. Activating TARGET makes MW5 blind to the stick's axis movements. You want TARGET because it has response curve editing for your joystick which in turn makes mech piloting easy as pie.

I still don't see how to get MW5 to recognize the T16000m's axes once TARGET is active. Activating TARGET makes MW5 blind to the stick's axis movements. You want TARGET because it has response curve editing for your joystick which in turn makes mech piloting easy as pie.

does target use a virtual driver like ch control manager does? i know to get the ch virtual sticks to show up, i need to use a different device id than the actual hardware (vid is the same though). i figure you can try to activate a target profile and then check the device manager for target devices. if you find one see if the device ids match the hotas.remap profile. if it doesn't a new profile could be created for that device. ive never used target before so idk.

does target use a virtual driver like ch control manager does? i know to get the ch virtual sticks to show up, i need to use a different device id than the actual hardware (vid is the same though). i figure you can try to activate a target profile and then check the device manager for target devices. if you find one see if the device ids match the hotas.remap profile. if it doesn't a new profile could be created for that device. ive never used target before so idk.

I'll fiddle around with it when I can get to it. Would be nice if PGI fixed it, then everyone would get the fix.

Does the Remap file look like the below?
Vid and Pid are important.
The PID is located under the joystick on the tag or plate.

Notes:
◾The Thrustmaster T.16000M FCS has a default configuration that works with no additional editing, but not all axes are mapped.
◾Dead zones were reduced dramatically in this config to facilitate more precise aiming.
◾If you have the flight pack, you can simply add this and the TWCS Throttle with pedals config to the same file.
◾For HOSAS configurations, you can use Thrustmaster's T.A.R.G.E.T software to combine two sticks into one.