Gaming controller and Rudder issue?

[StreetMagus]

Is there a way to set up the Rudder to be pressure sensitive for the triggers?
Under Controller Sensitivity, the game seems to recognize that the trigger buttons are variable and I can set the sensitivity, however, in-game the rudders are either fully ON or OFF.

[Moga CMDR]

i hear ya. not for me. its all or nothing. you have to be super soft to get less than 100%

lets hope they add sensitivity settings

some say use the auto rudder option for take off. but i refuse. maybe try that?

[opjose]

OP you have the same issue as this.... substitute Rudder for Throttle below...

---- SNIP ----

Make sure that there are absolutely no other throttle assignments before you do the Thrustmaster assignments.

Then make sure you assign the Thrustmaster Throttle AXIS to the game's AXIS input.

The latter is a bit confusing as there are also button inputs in game for the throttle.

That means you can assign a joystick linear function to a ON/OFF type input producing results like what the OP mentions.... e.g. the curves and stick inputs look fine but in game things don't work properly.

The same is true of other axis too... e.g. search for "Yaw" and you'll see multiple inputs but only one labeled "Yaw Axis". The latter is the only one you want to assign to a rudder pedal axis.

All the more confusing because "Axis" in game really should be labeled "Linear input" or something like that to avoid confusion.

[StreetMagus]

I figured what the problem is. RUDDER LEFT (YAW LEFT) and RUDDER RIGHT (YAW RIGHT) are settings in Flight Simulator that are not considered AXIS or Linear inputs. It is fully on for that setting.
RUDDER AXIS is another setting that allows you to assign a Linear input, in this case for the controller, the L and R triggers are linear. HOWEVER, these trigger buttons are each a separate linear input (think, two separate joysticks). You can't assign two "joysticks" to the RUDDER AXIS function, since they will interfere with one another.
Assigning one trigger (L or R) to the RUDDER AXIS function works, now you have a linear control of the rudder. BUT, the one button controls both left and right..so you will have to constantly hold down the trigger button in the middle point to keep the rudder neutral. LOL
Microsoft needs to allow RUDDER AXIS LEFT and RUDDER AXIS RIGHT in order for this to work correctly.

[opjose]

Publicado originalmente por Streetmagus:

I figured what the problem is. RUDDER LEFT (YAW LEFT) and RUDDER RIGHT (YAW RIGHT) are settings in Flight Simulator that are not considered AXIS or Linear inputs. It is fully on for that setting.
RUDDER AXIS is another setting that allows you to assign a Linear input, in this case for the controller, the L and R triggers are linear. HOWEVER, these trigger buttons are each a separate linear input (think, two separate joysticks). You can't assign two "joysticks" to the RUDDER AXIS function, since they will interfere with one another.
Assigning one trigger (L or R) to the RUDDER AXIS function works, now you have a linear control of the rudder. BUT, the one button controls both left and right..so you will have to constantly hold down the trigger button in the middle point to keep the rudder neutral. LOL
Microsoft needs to allow RUDDER AXIS LEFT and RUDDER AXIS RIGHT in order for this to work correctly.

Yes exactly.

You are better off assigning rudder to the controller's sticks if possible.

[StreetMagus]

Not ideal but as of now I am just using rudder controls with Right joystick, and clearing all the camera movements with the joystick left and right control so as to not interfere.
I enabled the camera movement controls with right joystick, but made it so I have to hold down the Right trigger button in order to move the camera. So its Right trigger button + Joystick = Camera movements.

[Freed]

Publicado originalmente por Streetmagus:

Not ideal but as of now I am just using rudder controls with Right joystick, and clearing all the camera movements with the joystick left and right control so as to not interfere.
I enabled the camera movement controls with right joystick, but made it so I have to hold down the Right trigger button in order to move the camera. So its Right trigger button + Joystick = Camera movements.

I did the same but even when I hold RT rudder moves too

[StreetMagus]

Publicado originalmente por Lybchikfreed:

Publicado originalmente por Streetmagus:

Not ideal but as of now I am just using rudder controls with Right joystick, and clearing all the camera movements with the joystick left and right control so as to not interfere.
I enabled the camera movement controls with right joystick, but made it so I have to hold down the Right trigger button in order to move the camera. So its Right trigger button + Joystick = Camera movements.

I did the same but even when I hold RT rudder moves too

Did you make sure that the RT isn't assigned to anything else? Perhaps Rudder Right?

[Freed]

Publicado originalmente por Streetmagus:

Publicado originalmente por Lybchikfreed:

I did the same but even when I hold RT rudder moves too

Did you make sure that the RT isn't assigned to anything else? Perhaps Rudder Right?

I'm sure

[WaterFowl]

WHY ISN'T THIS FIXED YET??? It makes it completely unplayable with a controller that has analogue output for the triggers. The rudder is simply unusable. And sending an analogue output into the regular binding makes it go completely haywire as it erroneously interprets it.

EITHER ADD ANALOGUE DETECTION TO TRIGGER/YAW OR GIVE US AN AXIS FOR EACH YAW DIRECTION

PLEASE FIX THIS

[WaterFowl]

I have to bump this every day until the developers acknowledge it, it's such a game breaking bug that is easily overlooked if you aren't using certain controllers.

[StreetMagus]

Publicado originalmente por WaterFowl:

WHY ISN'T THIS FIXED YET??? It makes it completely unplayable with a controller that has analogue output for the triggers. The rudder is simply unusable. And sending an analogue output into the regular binding makes it go completely haywire as it erroneously interprets it.

EITHER ADD ANALOGUE DETECTION TO TRIGGER/YAW OR GIVE US AN AXIS FOR EACH YAW DIRECTION

PLEASE FIX THIS

I agree, we need AXIS support for each rudder direction, then the triggers will finally be fixed.

[BluesyMoo]

Publicado originalmente por Streetmagus:

Publicado originalmente por WaterFowl:

WHY ISN'T THIS FIXED YET??? It makes it completely unplayable with a controller that has analogue output for the triggers. The rudder is simply unusable. And sending an analogue output into the regular binding makes it go completely haywire as it erroneously interprets it.

EITHER ADD ANALOGUE DETECTION TO TRIGGER/YAW OR GIVE US AN AXIS FOR EACH YAW DIRECTION

PLEASE FIX THIS

I agree, we need AXIS support for each rudder direction, then the triggers will finally be fixed.

I would really like that support for using the pedals from a steering wheel set as rudder. Say, set gas to rudder right and clutch to rudder left. How hard is it really?

[WaterFowl]

Publicado originalmente por MarleyMoo:

Publicado originalmente por Streetmagus:

I agree, we need AXIS support for each rudder direction, then the triggers will finally be fixed.

I would really like that support for using the pedals from a steering wheel set as rudder. Say, set gas to rudder right and clutch to rudder left. How hard is it really?

Not very. All they'd have to do is allow the yaw bindings to take analogue values, or add Yaw left and Yaw right axis bindings. The latter option would take all of 5 minutes to implement. I submitted a bug report on the official website but I have a feeling nobody looks at those

example of how easy the latter option is to add:
current Yaw axis binding works by looking at the analogue value; if the number is negative, turn right, if positive, turn left at the magnitude of the number. All they'd have to do is take the positive analogue value from the right axis binding (since our peripherals output a positive value) and set it negative and apply it to the yaw axis. That's literally it. It's probably not even 5 minutes of work.

That's why this bug is so infuriating to me, it's so easy to fix, and if they used a variety of controllers to test their game it would have stuck out like a sore thumb

[Calumniate]

agreed - i'm trying to use my g27 pedals for rudder action (yes no 'real' rudder pedals but i mean come on, should work). going to be an active subscriber to this thread!

[WaterFowl]

Not going to let this go until devs acknowledge