#WINCTRL Throttle MobiFlight Configuration for FENIX

1 messages · Page 1 of 1 (latest)

gilded spade
#

Hi. I downloaded a MobiFlight Community configuration for the Fenix A320 from Flightsim.to. I have the problem that my thrust lever for the URSA MINOR Metal Throttle is not working. So I started making my own config, and I am still trying to understand how to do that.

I am now familiar with Developer Mode and Behaviour Debug, and I know how to read it. But I still do not understand where the component and the preset in MobiFlight come together.

For example: thrust levers.

In Mobiflight Im scanning for the input of the left thrust lever. The device is Axis Rotation X. But the system or root component, which is Throttles, is not available in the systems, and the component FNX32X_Throttle_Engine_Lever is also not available in the preset list.

So I do not understand the interaction between the preset in MobiFlight and the components shown in the Behaviour Debug mode of MSFS 2020.

hybrid lagoon
#

the presets named FNX320 THROTTLE LEFT LEVER SET

#

are the ones. However, they are configured to work with an Arduino connected potentiometer.

#

A Windows HID axis will typically have a range 0 to 65535, so the math of the event needs to be adjusted accordingly

#

There is a tool in Hubhop to calculate potentiometer calibration parameters which is very easy to use.

#

try this variation

@ 65535 / 3 * 2 + 2 max 5 min (>L:A_FC_THROTTLE_LEFT_INPUT)
#

this limits the action to the full thrust range. No reverse here.

gilded spade
#

@hybrid lagoon thx for your answer. How do I find the correct MobiFlight preset or event for a component that I see in the MSFS Behaviour Debug window? And how are the Behaviour Debug components connected to MobiFlight presets?

I am confused because the component names shown in Developer Mode do not seem to appear directly in the MobiFlight preset list.

For me, it is not self-explanatory how the components shown in MSFS Behaviour Debug are connected to the presets in MobiFlight.

hybrid lagoon
#

Search for sensible names

#

I mean, the preset is named FNX320 THROTTLE LEFT LEVER SET. What else could this be for?

#

and it is categorized under Fenix vendor, A320 aircraft, Engine System and Input (Potentiometer) for type of device

#

You can enter specific text in the search filter to narro down the selection.

#

I used Hubhop and just set the filters accordingly

#

The names are selected by whoever made the contribution, but in general they make sense without having to see anything in Dev Mode Behaviors

#

Also names used in the sim, not necessarily will make sense to anyone but a computer.

#

like for PMDG everything is a switch plus a number. Figure that out.

#

My approach to naming presets has more to do with how the control or display is named in the virtual cockpit and its location.

gilded spade
#

@hybrid lagoon thanks for help so there is no self-explanatory have to find out name and preset etc. But i have still Problems to get the registered Presets in Developer Mode as orientation

#

i only have this to input events

hybrid lagoon
#

Fenix does not make much use of the Sim input events structure

blissful elmBOT
hybrid lagoon
#

For Fenix you will need to search in the Behaviors tab. However, for this aircraft, most, if not all events, are already cataloged as Mobiflight presets

gilded spade
#

cool thanks so i will look for them in Hubhop i thinl

hybrid lagoon
#

If you need help with the thrust levers, please be more specific about what you are doing and what is not working.

gilded spade
#

Hey Jaime the question how to find the presets etc with thrust lever just was a example... but now im using the Hubhop presets .... for FNX Throttle lever for example you wrote the Code @ 65535 / 3 * 2 + 2 max 5 min (>L:A_FC_THROTTLE_LEFT_INPUT) ... in hubhop it says @ 1023 / 3 * 2 + 2 max 5 min (>L:A_FC_THROTTLE_LEFT_INPUT) is the value 65535 which i can find for example in the simproapp ? also for flaps and speed brakes?

hybrid lagoon
#

HID joystick axes typically have a range of 0 to 65535 which is quite different to the Arduino axis range (0 to 1023).