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.

FFX P180 input events appear broken

Featured Replies

Hello all, 

I am pulling my hair out trying to figure out how to get the new P180's IE's working with my X-Touch mini. 

When I select anything from the MSFS IE menu under the "ffx" section, for example the engine start L function, no matter what I do nothing happens when I assign a button for it. If I select a different IE outside of the ffx grouping like the landing gear for example I can get it to work no problem. 

Does anyone have the P180 FFX IE's working? Am I missing something?

Thank you so much for hopefully someone taking a look. 

P

  • Commercial Member
2 hours ago, pilatuz said:

Am I missing something?

In most cases it is about the value being sent (the little numerical box to the right). IE are not just existing, you have to send the correct numerical value with it (0,1,whatever). This is best evaluated on the event observer dialog with the script editor open, so one can try out the IEs.

Alternatively you can write nearly every IE as a BVar, that is often more convenient.

(>IE:somename) can in most cases also be addressed as 
(>B:somename_Set)
(>B:somename_Inc)
(>B:somename_Dec)
(>B:somename_Toggle)
etc. 

This can be seen in the behavior code too - which would be my recommendation. 

LORBY-SI

  • Author

Thank you very much for the reply good sir. 

After your suggestions and trying to grasp the MSFS behavior dialog I think I have it figured out, and would like to share my findings in case others are having issues with this particular aircraft. 

So FFX has it set up where their Input Events are actually seemingly opposite what you would expect, which is why I had a hard time figuring it out. 

For example: an IE like IE:ffx_Example needs to be used as a Bvar: B:ffx_Example and then the tricky thing is let's say it's a switch you want to turn ON, it is actually written this way: 0 (>B:ffx_Example_DEC), and turning the switch OFF would be: 0 (>B:ffx_Example_INC). This seems to be consistent with most of their IE's so hopefully this can save someone headache in the future! 

Thanks again for AAO.

 

P

  • Commercial Member
9 hours ago, pilatuz said:

For example: an IE like IE:ffx_Example needs to be used as a Bvar: B:ffx_Example and then the tricky thing is let's say it's a switch you want to turn ON, it is actually written this way: 0 (>B:ffx_Example_DEC), and turning the switch OFF would be: 0 (>B:ffx_Example_INC). This seems to be consistent with most of their IE's so hopefully this can save someone headache in the future! 

Just for the record, you don't have to use scripts. You can enter BVars on the button assignment dialogs using the MAN setting. The value goes in to the little box to the right.

I would also try

0 (>ÎE:ffx_Example)
1 (>IE:ffx_Example)

or

1 (>B:ffx_Example_On)
1 (>B:ffx_Example_Off)

 

 

LORBY-SI

Create an account or sign in to comment

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.