Elite vs Mechwarrior 5 - Controls

Last night I bought MechWarrior 5, I was excited since the last good mech game I played was MW4 Mercenaries in the mid 2000's. Anyway so I startup the game and begin setting up my hotas. It sees my joystick and throttle but not my rudder pedals, ok. It tells me I can directly write to the config file to add more custom controls, but not where to dig that up... thank good for google. It has up to 6 buttons for firing weapons, but no fire group switching. so the primary trigger will always fire (lasers) secondary trigger will always fire the (auto cannon) and so on. Why cant they've copied elite or any flight sim on the 2 fire button design and just tab through fire groups! my joystick (X56-Rhino) only has 2 (maybe 3 if I'm feeling silly) good fire buttons. My gripe is that Elite has such a solid key binding editor built into the game and now I'm spoiled and expect that from other hotas appropriate games. SO in the end this is an Elite appreciation post, Thanks Fdev!
 
I searched around and found a guide showing a how to add a joystick in if the game doesn't see it but it was at the edge of my skillset on controller addressing
 
Don't buy this game - yet.

The 1990s versions worked with joysticks out of the box. It is astonishing that the in game configuration menu is apparently disabled from interacting with my T1600. Crazy. That seems like such a basic functionality for piloting a mech - like 30 years ago lol!

Twisting the stick turns the mech, tilting the stick turns the torso, the throttle sometimes behaves like its centerpoint is 0 other times it doesn't. Stick targeting is awful, mouse targeting is better. Such a fail, I miss the old lan parties with Mechwarrior 2.

I remember actually paying 10$ for 10 minute sessions at a storefront mechwarrior boutique in the 90s, on a version that predated MW2. Even that joystick worked.

How could this thing get released in its current state? Such a mess.
 
I haven't been following this very closely, but it's from the makers of MechWarrior Online, which I have some experience with. That game is a glorified FPS. This is on a different engine, so the controls setup is probably not similar, but I bet they didn't pay enough attention to the more sim style controls.

I traditionally use Joystick + Mouse on mech games, but in my last months of MWO, I switched to Throttle + Mouse. I think I had the pedals too at that point.
 
I haven't been following this very closely, but it's from the makers of MechWarrior Online, which I have some experience with. That game is a glorified FPS. This is on a different engine, so the controls setup is probably not similar, but I bet they didn't pay enough attention to the more sim style controls.

I traditionally use Joystick + Mouse on mech games, but in my last months of MWO, I switched to Throttle + Mouse. I think I had the pedals too at that point.

the controls in MW5 are pretty much verbatim from the MW4, only thing I've seen missing is setting radar range.

Twisting the stick turns the mech, tilting the stick turns the torso, the throttle sometimes behaves like its centerpoint is 0 other times it doesn't. Stick targeting is awful, mouse targeting is better. Such a fail, I miss the old lan parties with Mechwarrior 2.

the input output are right in the menu, if the joystick moves anything in game than it is connected. just swap the axes until they match the movement you want. but if the center points are all off than you gotta dig through the link CMDR Harada kindly provided. It is very sloppy but all the controls are there and can support "any" joystick, just limited to how many buttons are recognized. And for the last part it has co-op multiplayer! Im excited to try that out with my brother, i just have to convince him to pick the game up.
 
the input output are right in the menu, if the joystick moves anything in game than it is connected. just swap the axes until they match the movement you want. but if the center points are all off than you gotta dig through the link CMDR Harada kindly provided. It is very sloppy but all the controls are there and can support "any" joystick, just limited to how many buttons are recognized. And for the last part it has co-op multiplayer! Im excited to try that out with my brother, i just have to convince him to pick the game up.
Yeah you're wrong. The joystick inputs on the right hand menu aren't registered for the Thrustmaster t1600, one of the most common joysticks in production. If you think that digging through the config settings is as accessible as the 1990s version of the game, you are way off base. You might be able to make it work, but for 50$ it should work out of the box through the in-game menus. It doesn't.

The generic joystick settings do not provide camera zoom, nor does it scale with increased targeting sensitivity when zoomed, and it frankly tracks like the inputs chunk out screen pixel distances. This game is trash banking on the long lost goodwill of the initial offerings in the franchise.
 
If you think that digging through the config settings is as accessible as the 1990s version of the game, you are way off base.

That's the topic of the thread. Elite has a very well done and intuitive key binding page, MW5 has a trash key binding page by comparison.

The generic joystick settings do not provide camera zoom, nor does it scale with increased targeting sensitivity when zoomed, and it frankly tracks like the inputs chunk out screen pixel distances. This game is trash banking on the long lost goodwill of the initial offerings in the franchise.

I agree the default settings don't work or barely function, but I don't expect games to hand me pre-made, hand tailored to my setup, out-the-box bindings. I always build my own binding profiles, putting priority commands in 'hand' with aux commands within reach. Part of the fun of having a HOTAS is that they aren't generic controllers and offer a lot more customization.
 
I've played ALL the MW franchise, all the way back to the original on a TRS-80/IBM 8088 with an EGA monitor.. Loved and replayed MW4 Mercs many times until I had to upgrade to Win10.

Anyway, this new version is absolute trash for anything other then mouse+KB . ED recognizes many many different joysticks and throttles natively, why MW5 can't is a mystery. I might even understand since I'm running a VKB setup.. but lots of standard rigs are having issues.

It's also almost a verbatim storyline from BattleTech. Vastly disappointed in this.

This game is trash banking on the long lost goodwill of the initial offerings in the franchise.

Sigh... gotta agree.
 
Glad for this thread. I was going to jump on this game until I saw they jumped ship from steam for epic.
So instead I just reinstalled MW 4 Vengeance with Black Knight and Mercenaries expansions instead.
Maybe in a year if all is fixed by then.
 
Wow.. I got it working, but it was a major PITA.

Had to manually look up the VID/PID, insert it into the remap file, and then hand edit for the rest of the buttons and joystick axis. All in all took a few hours, with restarts, reloads, and all that.

Makes me appreciate Elite a little bit more.

This file helped me a lot :


Thank you for the great document. I'm still having an issue getting MW5 to see my MKIV. If it's not too much trouble, what did your entry look like?

Currently what I have (not working):

START_BIND
NAME: TRunner MKIV Rudder Pedals
VID: 0x231D
PID: 0x011F
AXIS: InAxis=GenericUSBController_Axis1, OutAxis=Throttle_Axis5, Invert=FALSE, Offset=-0.5, DeadZoneMin=-0.1, DeadZoneMax=0.1, MapToDeadZone=TRUE

Thanks in advance!
 
If your VID and PID are correct, I'd just bind every axis type, and keep the out axes in groups so you can test and round it down to which ones your device actually uses. doing it this way is a lot of work but i was able to figure out my rudder by process of elimination. BACK UP YOU BINDINGS BEFORE HAND

AXIS: InAxis=HOTAS_XAxis, OutAxis=Throttle_Axis1, Invert=FALSE, Offset=-0.5, DeadZoneMin=-0.1, DeadZoneMax=0.1, MapToDeadZone=TRUE
AXIS: InAxis=HOTAS_YAxis, OutAxis=Throttle_Axis1, Invert=FALSE, Offset=-0.5, DeadZoneMin=-0.1, DeadZoneMax=0.1, MapToDeadZone=TRUE
AXIS: InAxis=HOTAS_ZAxis, OutAxis=Throttle_Axis1, Invert=FALSE, Offset=-0.5, DeadZoneMin=-0.1, DeadZoneMax=0.1, MapToDeadZone=TRUE
AXIS: InAxis=HOTAS_RZAxis, OutAxis=Throttle_Axis1, Invert=FALSE, Offset=-0.5, DeadZoneMin=-0.1, DeadZoneMax=0.1, MapToDeadZone=TRUE

AXIS: InAxis=GenericUSBController_Axis1, OutAxis=Throttle_Axis2, Invert=FALSE, Offset=-0.5, DeadZoneMin=-0.1, DeadZoneMax=0.1, MapToDeadZone=TRUE
AXIS: InAxis=GenericUSBController_Axis2, OutAxis=Throttle_Axis2, Invert=FALSE, Offset=-0.5, DeadZoneMin=-0.1, DeadZoneMax=0.1, MapToDeadZone=TRUE
AXIS: InAxis=GenericUSBController_Axis3, OutAxis=Throttle_Axis2, Invert=FALSE, Offset=-0.5, DeadZoneMin=-0.1, DeadZoneMax=0.1, MapToDeadZone=TRUE
AXIS: InAxis=GenericUSBController_Axis4, OutAxis=Throttle_Axis3, Invert=FALSE, Offset=-0.5, DeadZoneMin=-0.1, DeadZoneMax=0.1, MapToDeadZone=TRUE
AXIS: InAxis=GenericUSBController_Axis5, OutAxis=Throttle_Axis3, Invert=FALSE, Offset=-0.5, DeadZoneMin=-0.1, DeadZoneMax=0.1, MapToDeadZone=TRUE
...
...
 
Thank you! Very good idea on how to quickly figure out which axis. Here is the MechWarrior 5 HOTASMappings.Remap entry for the TRudder MK4 mapped to throttle axis 2 (for the next poor soul):

START_BIND
NAME: VKB-Slim T-Rudder
VID: 0x231D
PID: 0x011F
AXIS: InAxis=GenericUSBController_Axis7, OutAxis=Throttle_Axis2, Invert=FALSE, Offset=-0.5, DeadZoneMin=-0.1, DeadZoneMax=0.1, MapToDeadZone=TRUE
 
Thank you! Very good idea on how to quickly figure out which axis. Here is the MechWarrior 5 HOTASMappings.Remap entry for the TRudder MK4 mapped to throttle axis 2 (for the next poor soul):

I did it the same way AdmiralXanos did it. I mapped them all and then removed the ones that didn't register. It was a major PIT-backside, since it would occasionally refuse to read beyond a certain line, and I would have to revert back a previously know 'good' file. I ended up doing the "It didn't work, was it the file or did it really not work" dance. I was going to use the VKB software to map my extra buttons to emulate keyboard keys as a way around the config file issues, but I lost interest. It was turning into a job and the game play wasn't that compelling.

Anyway, I'm not a huge fan and have considered deleting it ( $60 wasted ). I don't like KB+mouse, which is what I ended up using. If I adjusted the HOTAS to be sensitive enough to get off steady long shots with zoom, it was pretty jumpy when I was trying to hit small mechs close in.

I'll consider giving it another shot when I have time to goof around with it.
 
Top Bottom