15 replies to this topic

[tanjodang]

You should probably patch this.

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.

Fix this ****......

[9erRed]

Greetings,

Just a note here.

Listed on the MW5 home page.
https://mw5mercs.com...heral-resources


Supported Joysticks and Throttles

List of currently supported joystick and throttle peripherals. These make and model types should be configurable out of the box.
ThrustMaster

• ThrustMaster T.16000M Joystick
  
• ThrustMaster TWCS Throttle
  
• ThrustMaster T.Flight Hotas X
  
• ThrustMaster HOTAS Warthog

Logitech

• Logitech Extreme 3D pro Joystick

Saitech

• Saitek X52
  
• Saitek X52 Pro
  
• Saitek Pro Flight Rudder Pedals
  
• Saitek Pro Flight X-56 Rhino Stick
  
• Saitek Pro Flight X-56 Rhino Throttle

Look here for the setting for all these and more joysticks.
https://docs.google....=h.cbf8bd3oa0al

Configure other Joysticks and Throttles

Download Instructions on how to configure an un-supported joystick.

• You can download the Joystick Setup Support Manual here
  
• This will allow you to have the game recognize the hardware and its inputs
  
• Once you have followed the setup manual you will still need to map the inputs to game actions in the Game Settings Screen

9erRed
Aim True and Run Cool

[LordNothing]

see the joystick thread, somone might have posted a config for your stick.

Edited by LordNothing, 27 February 2020 - 04:21 PM.

[tanjodang]

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.

Edited by tanjodang, 27 February 2020 - 06:43 PM.

[SVK Puskin]

I am grown man too and i do not use joystick! Do not think that using your prefered gear is the only way! You just showed keyboard + mouse players how you disrespect them!

[Mystere]

No T.A.R.G.E.T., no MW5. <shrugs>

[LordNothing]

others have been able to get the game working with T.A.R.G.E.T. and have posted their configs.

[Mystere]

LordNothing, on 29 February 2020 - 08:40 PM, said:

others have been able to get the game working with T.A.R.G.E.T. and have posted their configs.

Which posts? I seem to have missed them.

[LordNothing]

Mystere, on 01 March 2020 - 07:46 PM, said:

Which posts? I seem to have missed them.

i was going to link to my old joystick workarounds thread but it looks like 9erRed's post has some newer information.

[Lightfoot]

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.

Edited by Lightfoot, 08 March 2020 - 11:38 PM.

[Vellron2005]

tanjodang, on 27 February 2020 - 01:09 PM, said:

Do you think I want to pilot a mech with a keyboard like I'm some ****? I'm a grown man.

Fix this ****......

Personally, I'm inclined to say "please don't fix it" just because of the absurd amount of attitude displayed here.

And also, what's wrong with mouse and keyboard? Best shooters are played that way.. take your console peasantry back to nintendo or something like that..

For a grown man, you sure act surprisingly childish..

Now, in all seriousness, PGI should fix many things, including controller support, and other things.. but not because you ordered them to do your bidding like they are your own minions or something..

Geez.. the nerve on some people..

[LordNothing]

Lightfoot, on 08 March 2020 - 11:35 PM, said:

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.

Edited by LordNothing, 10 March 2020 - 03:48 PM.

[Mystere]

Vellron2005, on 10 March 2020 - 01:35 AM, said:

And also, what's wrong with mouse and keyboard?

Play War Thunder as a fighter or heli pilot with mouse and keyboard and you'll get the idea.

[Lightfoot]

LordNothing, on 10 March 2020 - 03:45 PM, said:

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.

------------------------------------------------------------------------------------------------------------------------------------


I looked at the ID that TARGET adds to the T16000m's ID, but that didn't do anything in the .remap.

Edited by Lightfoot, 14 March 2020 - 11:50 PM.

[9erRed]

Greetings,

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.


In-game mappings:
◾Joystick Axis 1 - Joystick Y axis
◾Joystick Axis 2 - Joystick X axis
◾Joystick Axis 3 - Joystick Z (rotating) axis
◾Joystick Axis 4 - Joystick slider


HOTASMappings.Remap:

START_BIND
NAME: THRUSTMASTER T.16000M Joystick
VID: 0x044F
PID: 0xB10A
BUTTON: InButton=GenericUSBController_Button1, OutButtons=Joystick_Button1
BUTTON: InButton=GenericUSBController_Button2, OutButtons=Joystick_Button2
BUTTON: InButton=GenericUSBController_Button3, OutButtons=Joystick_Button3
BUTTON: InButton=GenericUSBController_Button4, OutButtons=Joystick_Button4
BUTTON: InButton=GenericUSBController_Button5, OutButtons=Joystick_Button5
BUTTON: InButton=GenericUSBController_Button6, OutButtons=Joystick_Button6
BUTTON: InButton=GenericUSBController_Button7, OutButtons=Joystick_Button7
BUTTON: InButton=GenericUSBController_Button8, OutButtons=Joystick_Button8
BUTTON: InButton=GenericUSBController_Button9, OutButtons=Joystick_Button9
BUTTON: InButton=GenericUSBController_Button10, OutButtons=Joystick_Button10
BUTTON: InButton=GenericUSBController_Button11, OutButtons=Joystick_Button11
BUTTON: InButton=GenericUSBController_Button12, OutButtons=Joystick_Button12
BUTTON: InButton=GenericUSBController_Button13, OutButtons=Joystick_Button13
BUTTON: InButton=GenericUSBController_Button14, OutButtons=Joystick_Button14
BUTTON: InButton=GenericUSBController_Button15, OutButtons=Joystick_Button15
BUTTON: InButton=GenericUSBController_Button16, OutButtons=Joystick_Button16
BUTTON: InButton=GenericUSBController_Hat1, OutButtons=Joystick_Hat_1
BUTTON: InButton=GenericUSBController_Hat2, OutButtons=Joystick_Hat_2
BUTTON: InButton=GenericUSBController_Hat3, OutButtons=Joystick_Hat_3
BUTTON: InButton=GenericUSBController_Hat4, OutButtons=Joystick_Hat_4
BUTTON: InButton=GenericUSBController_Hat5, OutButtons=Joystick_Hat_5
BUTTON: InButton=GenericUSBController_Hat6, OutButtons=Joystick_Hat_6
BUTTON: InButton=GenericUSBController_Hat7, OutButtons=Joystick_Hat_7
BUTTON: InButton=GenericUSBController_Hat8, OutButtons=Joystick_Hat_8
AXIS: InAxis=HOTAS_YAxis, OutAxis=Joystick_Axis1, Invert=FALSE, Offset=-0.5, DeadZoneMin=-0.03, DeadZoneMax=0.03, MapToDeadZone=FALSE
AXIS: InAxis=HOTAS_XAxis, OutAxis=Joystick_Axis2, Invert=FALSE, Offset=-0.5, DeadZoneMin=-0.03, DeadZoneMax=0.03, MapToDeadZone=FALSE
AXIS: InAxis=HOTAS_RZAxis, OutAxis=Joystick_Axis3, Invert=FALSE, Offset=-0.5, DeadZoneMin=-0.1, DeadZoneMax=0.1, MapToDeadZone=FALSE
AXIS: InAxis=GenericUSBController_Axis4, OutAxis=Joystick_Axis4, Invert=TRUE, Offset=0.5, DeadZoneMin=-0.05, DeadZoneMax=0.05, MapToDeadZone=TRUE




9erRed

Edited by 9erRed, 22 March 2020 - 12:40 PM.

[_INFIDEL_]

know this is an old anyone make any head way?