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.

Thrustmaster Toebrakes in SF50

Featured Replies

It's probably just me being an word not allowed, but I cannot get my toebrakes on my Thrustmaster Rudder to work with the Sf50 Vision Jet at all, no matter what I select. I have tried AXIS_LEFT_BRAKE_SET, BRAKES_LEFT events and Brake Left and Brake right axis and nothing seems to work. I don't have a problem with them assigned in FSUIPC though for some reason

  • Commercial Member

AXIS_LEFT_BRAKE_SET and AXIS_RIGHT_BRAKE_SET working fine here.

When in doubt, delete the axis assignment and create a new one. Just to make sure that Axis Min/Max are at their default settings (-16K to +16K in this case)

And make sure that you don't have a duplicate assignment, as you mentions FSUIPC. Using several apps in parallel that do essentially the same things can lead to trouble.

Edited by Lorby_SI

LORBY-SI

Along the same vein, I'm mapping my toe brakes from a TFRP via AAO to the FSW Learjet 35 and others.
Settings are default -16383 to +16383 (I can see other ranges - MSFS doesn't like that one bit).

All is working except for one thing I'm not understanding.
Looking up Simvars via the SDK (this is the simvars demo app for the SDK via visual studio that lets you spy on simvars), for some reason the toe brakes don't go back to 0 - they go to max but never come back to zero.   I checked the axis value (both raw and sent) in AAO and it is sending the correct range - no issue - and certainly no calibration.  It's sending the correct range AFAIK.

Any reason the sim would not return these simvars to 0?  The range in MSFS is 0 to 32767 as reported by the simvar app, and when the brakes are released, I get a value between 2000 and 5000 which makes zero sense to me when AAO is sending a solid -16,383 which should be 0.   The value is 0 before I press the pedal - just doesn't return there.

This is perhaps what explains why my planes slow down a bit because the brakes are always a bit applied which is strange.

Also, can you explain the difference between the regular and the _EX versions of the variables?

Thank you!

 

  • Commercial Member
9 hours ago, Muchimi said:

Also, can you explain the difference between the regular and the _EX versions of the variables?

Afraid not. That question would have to be directed at Asobo

9 hours ago, Muchimi said:

Any reason the sim would not return these simvars to 0?  The range in MSFS is 0 to 32767 as reported by the simvar app, and when the brakes are released, I get a value between 2000 and 5000 which makes zero sense to me when AAO is sending a solid -16,383 which should be 0. 

Depends. What variable where you looking at exactly and what event was used to set the value? In what aircraft?

First, don't trust in the SDK. The MSFS controller assignments themselves don't even use it IMO, that logic accesses the sim directly. So you can't compare the direct assignments in MSFS with what AAO is allowed to do using the SDK. Some names and terms sound similar, but they are not related.

Second, you never know what kind of logic is running in the aircraft, if the developer even uses default events and variables to do anything. For example, it could be that the variable you are looking at represents his attempt at simulating a certain ground friction behavior (theoretically, not saying that this has to be the case). The best example are the Autopilot AVars, that go completely haywire with the custom autopilot logic in the aircraft.

Third, if you are certain that the AVar that you are looking at is really connected to the Event that you use for setting the value, they should have the same value range. Meaning, if the AVar shows values from 0 to 32k, then the associated event used to setting that value must also go from 0 to 32k.

Last but not least, the "official" event logic for controllers are Input Events (IE:), BVars and HVars. As I understand it, develoepers should be using those for the interaction logic in their aircraft. But of course they don't have to, so every developer is effectively doing whatever they want or know.

9 hours ago, Muchimi said:

Looking up Simvars via the SDK (this is the simvars demo app for the SDK via visual studio that lets you spy on simvars)

You can do that in AAO too, in the Scripting menu.

Edited by Lorby_SI

LORBY-SI

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.