Mw5 Joystick Workarounds Thread (2024)

Member

• 
• Knight Errant
• 
• 22 posts

I trust (hope) the full joystick control will be in at release of MW5m!

Member

• 
• The Defiant
• 
• 377 posts

My Microsoft Sidewinder Precision 2 Joystick is still useless. No ability to set base buttons/throttle....Does MW5 intend to support HOTAS/Stick setups or not?

Gee I really miss MW4's plug and play joystick control. I guess high fidelity joystick support is not even on the agenda outside of flight simulation games (like DCS) nowadays.

Yay!!! Someone is at least trying. MW5 link: https://static.mw5me...mentation.pdf

However still no luck trying to get the Microsoft Sidewinder Precision Pro 2 working with this game.... buttons do not bind and throttle and Z rotation are screwed up.

Edited by FireDog, 28 December 2019 - 09:30 PM.

Member

• 
• Ace Of Spades
• 
• 16,772 posts

now you have to edit HOTASMappings.remap.

working profile for my ch throttle,pedals, and fighterstick:

START_BINDNAME: CH Control Manager Device 1VID: 0x068EPID: 0xC010AXIS: InAxis=HOTAS_XAxis, OutAxis=Joystick_Axis1, Invert=FALSE, Offset=-0.5, DeadZoneMin=-0.02, DeadZoneMax=0.02, MapToDeadZone=TRUEAXIS: InAxis=HOTAS_YAxis, OutAxis=Joystick_Axis2, Invert=TRUE, Offset=0.5, DeadZoneMin=-0.02, DeadZoneMax=0.02, MapToDeadZone=TRUEAXIS: InAxis=HOTAS_ZAxis, OutAxis=Throttle_Axis1, Invert=TRUE, Offset=0.5, DeadZoneMin=-0.10, DeadZoneMax=0.10, MapToDeadZone=TRUEAXIS: InAxis=HOTAS_RZAxis, OutAxis=Joystick_Axis3, Invert=FALSE, Offset=-0.5, DeadZoneMin=-0.08, DeadZoneMax=0.08, MapToDeadZone=TRUE

requires the sticks be combined in ch control manager. maps to x,y,z,and r axes. i also mapped the buttons directly to the keystrokes for the default keyboard commands, which saves a lot of steps.

important stuff is the name, pid and vid numbers, which can be obtained from either the device manager or the input tab of dxdiag. dont forget the 0x prefix because it is hex. my axis configuration assumes a standard 4-axis controller (x,y,z,r). the out axis is the one you map in game, the in axis idk where it gets those names from, it took some trial and error. i also noticed that if you use invert=true, then offset needs to be positive, weird stuff happens if you don't do that. deadzone min and max should be the same with the min negative. i assume that 0.1 is 10 percent, which is a bit high, 0.02 worked for my stick, i like a broader dead zone in the throttle to make it easier to stop, and the pedals have a huge fuzzy center so i gave it a full 0.1. i still haven't figured out what map to deadzone does yet, so i turned it off. if you want buttons just copy the button lines from one of the other examples and stick it between pid and axis. one line for each button, and increment the numbers. i got it to work without messing with input.ini (which i cleared).

its not perfect but it is working with more sticks and virtual drivers.

also:

LordNothing, on 17 December 2019 - 11:31 AM, said:

Edited by LordNothing, 17 December 2019 - 11:33 AM.

Member

• 
• Bad Company
• 
• 6,610 posts

• LocationOlympus Mons

Using just the Thrustmaster T16000m in the Beta MW5 everything worked except the throttle which had no defined axis in MW5 game options and the game couldn't see the throttle. If I turned on the T16000m's profiler software, "TARGET", the game could no longer see the joystick, weird because MW3 can. Anyway, my MW5 download completes tomorrow as I installed to a new folder to make sure I get a clean install.

I bugged this on the Discord Bug reports and general about 5 times as did others. Suggest a Beta Forum for bug reporting instead next time.

Member

• 
• Ace Of Spades
• 
• 16,772 posts

Lightfoot, on 10 December 2019 - 08:01 PM, said:

i noticed that the default tm160000 profile doesnt have an axis binding for the throttle for some reason idk why. for my ch hotas i just used this, as z is usually the axis assigned for throttle:

AXIS: InAxis=HOTAS_ZAxis, OutAxis=Throttle_Axis1, Invert=TRUE, Offset=0.5, DeadZoneMin=-0.10, DeadZoneMax=0.10, MapToDeadZone=FALSE

i bet target is using a virtual controller to combine axes, like what ch has. ch creates a virtual device, with different name/vid/pid values from the actual hardware. so if you could find that data you might be able to get it to work. i dont have a thrustmaster so idk how that works in their software. browse the device manager (or dxdiag -> input) and see if you can find any hid/joystick/game controller/thrustmaster/target devices you cant account for.

Edited by LordNothing, 10 December 2019 - 09:06 PM.

Member

• 
• Ace Of Spades
• 
• 16,772 posts

seems pgi has released an official joystick configuration manual.
https://static.mw5me...cumentation.pdf

Member

• 
• Bad Company
• 
• 22,783 posts

• LocationClassified

LordNothing, on 10 December 2019 - 09:42 PM, said:

Wow! PGI actually expects people to do that in this day and age?

Member

• 
• Ace Of Spades
• 
• 16,772 posts

Mystere, on 10 December 2019 - 09:55 PM, said:

well for me editing game config files is pretty much tradition.

in ye old days of yore you could just query your api for a list of joysticks on the system. then you could get data about any one of those joysticks like number of axes, buttons, hats, balls (yes balls as in the track variety). i usually use sdl for this kind of thing as it is pretty much the lightweight cross platform equivalent of directx (minus direct3d as you usually use it with opengl or possibly vulkan).

Edited by LordNothing, 10 December 2019 - 10:03 PM.

Member

• 
• The Grizzly
• 
• 131 posts

LordNothing, on 10 December 2019 - 09:42 PM, said:

I found that. Added the throttle to the config. The only thing working with my joystick is the torso twist and turn. None of the buttons work, the throttle doesn't work. I've opened up a case with Thrustmaster because when I use their T.A.R.G.E.T. software to map my joystick it gets an error while loading and my joystick disappears completely. I have to go into device manager, look for hidden HID devices, find the one that shows and error, uninstall it and restart Windows to get the joystick back.

Here is the HOTAS mapping I'm using in the HOTASMappings.Remap file (note that I added the throttle axis at the bottom):

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_XAxis, OutAxis=Joystick_Axis2, Invert=FALSE, Offset=-0.498039, DeadZoneMin=-0.1, DeadZoneMax=0.1, MapToDeadZone=FALSE
AXIS: InAxis=HOTAS_RZAxis, OutAxis=Joystick_Axis3, Invert=FALSE, Offset=-0.5, DeadZoneMin=-0.2, DeadZoneMax=0.2, MapToDeadZone=TRUE
AXIS: InAxis=HOTAS_YAxis, OutAxis=Joystick_Axis1, Invert=FALSE, Offset=-0.498039, DeadZoneMin=-0.3, DeadZoneMax=0.3, MapToDeadZone=TRUE
AXIS: InAxis=HOTAS_ZAxis, OutAxis=Throttle_Axis1, Invert=TRUE,
Offset=0.5

Member

• 
• Ace Of Spades
• 
• 17 posts

For those with a TFlight HOTAS X and looking to map the rudder slider to left/right turn, I found a key mapping workaround on reddit. Not ideal, but at least it works on a rudimentary level:

Quote

From: https://www.reddit.c...s6fw/mw5_hotas/

Edited by InsiderGamer, 11 December 2019 - 07:17 AM.

Member

• 
• Ace Of Spades
• 
• 16,772 posts

InsiderGamer, on 11 December 2019 - 07:17 AM, said:

ughh, that sounds janky. thats worse than the xinput wrapper i was using with the beta.

Member

• 
• Ace Of Spades
• 
• 17 posts

LordNothing, on 11 December 2019 - 07:33 AM, said:

It's not ideal, but should I use the xinput wrapper? How is it better? If it's better and worth it for me to switch, I will.

Member

• 
• Ace Of Spades
• 
• 16,772 posts

InsiderGamer, on 11 December 2019 - 08:36 AM, said:

you can try it but i found it rather difficult to get it installed. if you can make it work, it does give you all four axes.

if i had one of these thrustmaster sticks i could probably get it to work without it. been wanting a warthog since i saw one, but that's got a hefty price tag. and i really cant justify replacing a stick that has served me well for over a decade and still works well.

Member

• 
• 368 posts

I have been waiting for the final release of the game to get some actual player feedback before actually purchasing.
There are mixed reviews but all things considered, it seems like I will enjoy this.
However, this topic caught my attention.
Standard joystick support is something I would expect in any modern game of this type.
Going to hold on to my cash until I see the developers step up and do the right thing here.
Peace

Member

• 
• Ace Of Spades
• 1,325 posts

Peace2U, on 11 December 2019 - 07:32 PM, said:

X52 and X56 are notionally supported. Makes me happy, I bought an X52 pro specifically for MW5. Just waiting for a review specifically of the X52 to make sure it works well.

Member

• 
• Legendary Founder
• 3,625 posts

Thank microsoft for your ****** nerfing of the peripheral API

Rookie

• The Phoenix
• 
• 3 posts

seriously.. a game should be plug 'n Play. Just because I *can* comprehend configurations doesn't mean I should have to. disappointing.

Member

• 
• Ace Of Spades
• 
• 16,772 posts

OZHomerOZ, on 12 December 2019 - 03:43 AM, said:

to be fair direct input was really messy, but at least it supported sticks with more stuff than the standard gamepad that xinput forces on you. a new api is needed. sdl works wonders though.

Edited by LordNothing, 12 December 2019 - 03:55 PM.

Rookie

• The Hunter
• 
• 5 posts

hello, it is possible to use a g27 pedals as rudder?

Member

• 
• Ace Of Spades
• 
• 16,772 posts

Joaostorfe, on 12 December 2019 - 05:08 PM, said:

maybe. i use my ch pedals but yours should work. problem is its hard to make a profile for somone without having the device on hand to test.

Edited by LordNothing, 12 December 2019 - 06:23 PM.