Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Saitek rudder brake pedals

Featured Replies

  • Author

Hi Oliver

I think that you are correct in saying that it is not hardware related.

I have tried replacing my Saitek pedals with my CH ones with the same result.

Tried disabling the Community folder, disabling FSUIPC etc. to no avail.

I don't think that AAO is part of the 'problem' and sorry for getting you involved.

Anyway, I have no idea how to track down the culprit, so I will just have to live with it.

As I previously said 'no big deal'

Thanks again.

Al

I had similar problems. It was always because I had other assignments for the same control surface or lever made in the MSFS Controls window. Like the AAO assignment for throttle or rudder would not work because those controls were already assigned by MSFS itself. Also had similar issue with the brakes.

I made new profiles in MSFS that nothing assigned to axis at all and had them selected as being the profiles in use. Then all AAO assignments I made would work instead of nothing happening.

Also in the later updates to MSFS I sometimes have to close down AAO, then start a flight on the runway, and then boot up AAO in order for my controllers to do anything. Otherwise sometimes for instance the rudder surface won't move in the sim when I press the pedals. This happens even though AAO up on the top info bar is showing the correct plane connected by Simconnect. But there is no connection until I close and then restart AAO and then it works fine.

 

5800X3D, RTX4070, 600 Watt, one or two 1440p 32" screens, 64 GB RAM, 4 TB  PCle 3 NVMe, Warthog throttle, VKB NXT EVO stick, Honeycomb Alpha yoke, CH quad, 3 Logitech panels, 2 StreamDecks, Desktop Aviator Trim Panel. Crystal Light VR.

 

AAO was working. But just now loaded a flight and AAO came up automatically but no throttle input. Closed AAO, rebooted AAO and all was well. By the way when the throttle would not work, the rudder worked fine (it is also controlled by AAO). The cure is just closing AAO and then rebooting it, with no need to apply any templates or anything.

5800X3D, RTX4070, 600 Watt, one or two 1440p 32" screens, 64 GB RAM, 4 TB  PCle 3 NVMe, Warthog throttle, VKB NXT EVO stick, Honeycomb Alpha yoke, CH quad, 3 Logitech panels, 2 StreamDecks, Desktop Aviator Trim Panel. Crystal Light VR.

 

  • 3 weeks later...

Hmm, this is interesting. I was just about to post a searate thread until I came across this post. I too cannot assign brakes to my MFG pedals via the Assigned Axis panel. I have spent over an hour trying everything, but with no success. I have checked and found no other conflicting assignments in MSFS. There is neither movement on the animated pedals themselves or any movement to the actual aircraft while taxiing. I am a little confused when AXIS_LEFT_BRAKE_SET and AXIS_RIGHT_BRAKE_SET is referred to?? What is this referencing? In the assigned axis panel you simply select what axis you want to assign. What am I missing?  :huh: EDIT: Just found a workaround by configuring the brakes only in MSFS. Not ideal, for obvious reasons, but it works.

Edited by Rockliffe

Howard
MSI Mag B650 Tomahawk MB, Ryzen7-7800X3D CPU@5ghz, Arctic AIO II 360 cooler, Nvidia RTX4090 GPU, 32gb DDR5@6000Mhz, SSD/2Tb+SSD/500Gb+OS, Corsair 1000W PSU, LG Ultragear 48"4K, MFG Crosswinds, TQ6 Throttle, Fulcrum One Yoke
My FlightSim YouTube Channel: https://www.youtube.com/@skyhigh776

  • Commercial Member
3 hours ago, Rockliffe said:

I am a little confused when AXIS_LEFT_BRAKE_SET and AXIS_RIGHT_BRAKE_SET is referred to??

Aircraft controls can happen either through simulator variables (that is the selector box at the top of the dialog) or by sending simulator events (second box from the top). And that second one is where the "AXIS_.._SET" events live. Which one works depends on how the aircraft has been made, it is always one or the other.

Recently a bug has been discovered where AAO 2.21 would read the AXIS_ events as trigger events in some cases. That would also lead to the behavior that you are seeing. This has been fixed in version 2.22, which is currently being tested. Until then, assigning event axis in the sim is the best option. Or sending an email with your proof of purchase to the support address on the last page of the manual with your proof of purchase, then you can have the fixed version 2.22 to try it.

Edited by Lorby_SI

LORBY-SI

  • 2 weeks later...

I was having the exact same issue and the most recent version solved it. 

Thanks

Kael Oswald

9950X3D/ 64GB DDR5 6200 @ CL30 / Custom Water Loop / RTX 5090 / 3 x 48" LG C4 OLEDs

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.