I bought a Thrustmaster Pedal

Joystick CFG

[joystick_slew {72be98a0-4d89-11e5-8001-444553540000}]
locked=0
axis_event_00=axis_slew_sideways_set
axis_scale_00=64
axis_null_00=36
axis_event_01=axis_slew_ahead_set
axis_scale_01=64
axis_null_01=36
axis_event_05=axis_slew_heading_set
axis_scale_05=64
axis_null_05=36
button_down_event_00=slew_reset
button_down_event_01=pan_reset
button_down_event_02=slew_altit_plus
button_down_event_03=slew_altit_minus
button_down_event_04=slew_pitch_plus
button_down_event_05=slew_pitch_minus
button_down_event_06=slew_bank_minus
button_down_event_07=slew_bank_plus
pov_move_event_00=pan_view
pov_move_repeat_00=1


[joystick_main {53e14210-2116-11ea-8001-444553540000}]
locked=0
axis_event_00=axis_ailerons_set
axis_scale_00=64
axis_null_00=36
axis_event_01=axis_elevator_set
axis_scale_01=64
axis_null_01=36
axis_event_02=axis_throttle_set
axis_scale_02=127
axis_null_02=1
button_down_event_00=fire_primary_guns
button_down_repeat_00=1
button_up_event_00=stop_primary_guns
button_down_event_01=fire_secondary_guns
button_down_repeat_01=1
button_up_event_01=stop_secondary_guns
button_down_event_02=select_next_target
button_down_event_03=select_previous_target
button_down_event_07=toggle_padlock
button_down_event_08=numpad7
button_down_event_09=numpad1
pov_move_event_00=pan_view
pov_move_repeat_00=1




[joystick_main {bc4ccd00-7a9f-11ea-8001-444553540000}]
locked=0
axis_event_00=axis_ailerons_set
axis_scale_00=64
axis_null_00=36
axis_event_01=axis_elevator_set
axis_scale_01=64
axis_null_01=36
axis_event_02=axis_throttle_set
axis_scale_02=127
axis_null_02=1
button_down_event_00=fire_primary_guns
button_down_repeat_00=1
button_up_event_00=stop_primary_guns
button_down_event_01=fire_secondary_guns
button_down_repeat_01=1
button_up_event_01=stop_secondary_guns
button_down_event_02=ordnance_cycle
button_down_event_03=ordnance_release
button_down_event_06=war_emergency_power
pov_move_event_00=pan_view
pov_move_repeat_00=1
 
In my experiences I've found that Thrustmaster products suck in CFS2 with no clear reasons. Its really hard to successfully map the controller assignments to work consistently. Even when you do get it working the assignments just randomly drop out like gremlins are at work. I can only imagine your headache trying to get the unit to work in conjunction with another controller.

Get your refund and try the CH Pro Pedals. I don't own this one but the reviews have always been 4.5 and 5 stars. Seems that this one is also good for driving sims.
 
Pepe,

I've been using Thrustmaster products for years and never had an issue like this. They are not plug-and-play products like many others. Did you set up the controller axis assignments? Go to the controller axis assignments, open the dropdown menu and select the Thrustmaster pedals. Then, assign the axis' for what you need them for (left, right rudder and toe brakes if supplied). Also, if your rudder functions were assigned to your joystick, delete those assignments after the pedals have been setup to take them over. sorry, I don't have access to my simpit right now so I can't provide pics of the menus.
 
Thrustmaster Pedals

I use the Thrustmaster HOTAS set up for the A-10, together with Thrustmaster rudder pedals. Sometimes when I decide to change a key or switch function I get a problem when the Thrustmaster; Microsoft and Dawson's FSUIPC all start to conflict.
I find that if I clear all Axis actions from the Microsoft side and re-set all Axis in FSUIPC then things come together again.
Hope this helps.
Mal
 
vonernsk said:
I use the Thrustmaster HOTAS set up for the A-10, together with Thrustmaster rudder pedals. Sometimes when I decide to change a key or switch function I get a problem when the Thrustmaster; Microsoft and Dawson's FSUIPC all start to conflict.
I find that if I clear all Axis actions from the Microsoft side and re-set all Axis in FSUIPC then things come together again.
Hope this helps.
Mal
Click to expand...

Thank you!
 
You must log in or register to reply here.
Back
Top