Jump to content

Does anyone have a working CH Fighterstick Pro Configuration?


6 replies to this topic

#1 Wildedge

    Member

  • PipPip
  • 44 posts

Posted 01 November 2012 - 10:07 AM

I was so excited about the game I ordered a CH Fighterstick Pro Joystick and Rudder Pedals. I've been very unhappy with how it responds in game, switching back to the mouse every time. I've tried changing the Gain and Sensitivity in the user cfg file to various settings without getting any result that allows for the balance of speed and accuracy with stability that I'm looking for.

If anyone has a CFG file that works for them that they would be willing to share, I would greatly appreciate it. I'm almost ready to send the whole set up back.

#2 Strummer

    Rookie

  • 5 posts

Posted 01 November 2012 - 12:20 PM

Bumping...I'd be interested in this, too. I have CH HOTAS (throttle and stick) plus Logitech G27 pedals. I wonder if I should attempt too get the CH stuff to work via the game interface or if it's possible to do in the CH Control Manager software.

Does anyone even know if the game is fully optimised for non keyboard/mouse controllers yet, especially pilot-style sontrols (stick, rudder and throttle)?

#3 Tarrien

    Member

  • Pip
  • Legendary Founder
  • Legendary Founder
  • 14 posts
  • LocationSaylorsburg, PA

Posted 03 November 2012 - 03:34 AM

I use the Fighterstick with a mouse. It works great for me. I'm left handed so my setup may be a little wonky for a righty. I have the Joystick Forward/Back set as the Throttle because I use the mouse with my left hand to handle the torso and targeting. I use the left mouse button to select my target and the mouse wheel to toggle weapon group association. I have been running a Catapult Missile boat so I have my groups set as WG 1 = Lasers, WG 2 = 1 LRM, WG 3 = 1 LRM, WG 4 = Both LRM's. I usually leave Weapon Group 1 selected to fire with the trigger.


This is what I have in the CH Control Manager .map file:

010828=Fire Selected WG
010B28=Team Speak Push to Talk
010A28=Zoom
011128=Free Look
011228=Full Stop
011328=Toggle Power
010E28=Map Overlay
010D28=Heat Vision
010F28=Night Vision
010C28=Center Torso
011628=Alpha Strike
011528=Fire WG 3
011728=Fire WG 2
010213=Throttlel Up/Down
010113=Turn Left/Right
000003=50
000004=100
000007=8
000011=5
010101=1
010104=1
010105=1
010110=1
010111=1
010112=0 1a /\d \/NULL ||
010114=83911691
010201=1
010204=1
010205=1
010210=1
010211=2
010212=0 1w /\s \/NULL ||
010214=83911691
010301=2
010304=1
010310=1
010311=3
010314=83911689
010701=2
010704=1
010710=1
010711=7
010801=1
010804=1
010805=1
010820=f
010824=1
010825=1
010901=1
010904=1
010905=1
010920=q
010924=1
010925=2
010928=Override Shutdown
010A01=1
010A04=1
010A05=1
010A20=z
010A24=1
010A25=32
010B01=1
010B04=1
010B05=1
010B20=rctl
010B24=1
010B25=4
010C01=1
010C04=1
010C05=1
010C20=c
010C24=1
010C25=5
010D01=1
010D04=1
010D05=1
010D20=h
010D24=1
010D25=6
010E01=1
010E04=1
010E05=1
010E20=m
010E24=1
010E25=7
010F01=1
010F04=1
010F05=1
010F20=n
010F24=1
010F25=8
011001=1
011004=1
011005=1
011020=q
011024=1
011025=9
011101=1
011104=1
011105=1
011120=g
011124=1
011125=10
011201=1
011204=1
011205=1
011220=x
011224=1
011225=11
011301=1
011304=1
011305=1
011320=p
011324=1
011325=12
011401=1
011404=1

In my C:\Games\Piranha Games\MechWarrior Online\USER\Profiles\charater name\actionmap.xml file I have this:

<ActionMaps Version="10">
<actionmap name="hud">
<action name="toggle_Weapon_Group">
<rebind device="keyboard" input="u" index="0" defaultInput="rctrl"/>
<rebind device="keyboard" input="mouse3" index="2" defaultInput=""/>
</action>
</actionmap>
<actionmap name="mech">
<action name="m_show_target_overlay">
<rebind device="keyboard" input="m" index="0" defaultInput="q"/>
</action>
<action name="attack1">
<rebind device="keyboard" input="f" index="0" defaultInput="mouse1"/>
</action>
<action name="m_freelook">
<rebind device="keyboard" input="g" index="0" defaultInput="lctrl"/>
</action>
<action name="m_wg4">
<rebind device="keyboard" input="" index="2" defaultInput="mouse5"/>
</action>
<action name="m_wg3">
<rebind device="keyboard" input="" index="2" defaultInput="mouse4"/>
</action>
<action name="m_wg2">
<rebind device="keyboard" input="" index="2" defaultInput="mouse2"/>
</action>
<action name="shutdownOverride">
<rebind device="keyboard" input="q" index="0" defaultInput="o"/>
</action>
<action name="m_next_target">
<rebind device="keyboard" input="mouse1" index="2" defaultInput=""/>
</action>
<action name="m_toggle_zoom_mode">
<rebind device="keyboard" input="" index="2" defaultInput="mouse3"/>
</action>
</actionmap>
</ActionMaps>


#4 Wildedge

    Member

  • PipPip
  • 44 posts

Posted 05 November 2012 - 05:41 PM

I wish I was left handed so that I could get some use out of your file Tarrien. Thank you for posting it.

Does anyone have a right handed set up?

#5 BlackBeltJones

    Member

  • PipPipPipPipPipPip
  • 460 posts

Posted 14 November 2012 - 04:25 PM

I too am struggling with my new CH gear in MWO. The best config I have come up with so far (and I must preface that I am NOT an expert when it comes to programming the CH gear) is setting the Fighterstick to be the mouse - rather than CM Device X, scroll down in the pulldown and select 'mouse' for the X and Y axis. Additionally I set the sensitivity for both axis to 50 with no change to the gain. I have also slowed the scroll speed down considerably in Windows.
When I have tried to use the Fighterstick as a joystick rather than a mouse the response in game is far too slow. I am hoping the MWO team will make joystick support more robust as time goes on - for now Im just trying all options and using what works best for now.

#6 Taranchio

    Member

  • Pip
  • 13 posts

Posted 17 December 2012 - 03:48 AM

Actually... its not bad... just well hidden

I point you to http://mwomercs.com/...ech-saitek-fix/

You will need to set the Gain to something a bit higher than default... Im using 8, details are here http://mwomercs.com/...joystick-users/

#7 datmetal

    Rookie

  • The Paw
  • 7 posts

Posted 14 August 2023 - 06:29 PM

For those who want an aim down sights functionality.

a simple script.
it uses button 4 by default.

https://github.com/u...ighterstick.map

Edited by datmetal, 14 August 2023 - 06:44 PM.






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users