MobiFlight Community Support

Sebastian,

Do you have any idea if or when a Event ID support will be added?
It really helps with controlling the PMDG NGX (Or there is a way to convert the Event ID to offsets).

Thanks,
Yuval

Basically you can send EventID via Offset 0x3110. But currently the UI does not provide you the possibility to easily set an additional parameter - these exist for several IDs.
You can see an example in the example config file that ships with MobiFlight Connector in the examples-folder (see the increment of Squawk Code)

I will think about having a special config dialogue to support EventIDs better.

In the meantime you do the following workaround:
* Create a configuration for your switch / button
* Use FSUIPC Offset as input-type
* Use offset 0x3110 and 4 byte to trigger the EventID - as value you can send the decimal value of the EventID (instead of the text) - I think you find the values in the addons documentation or in FSUIPC SDK

In the need of setting an additional parameter as "argument"
* Duplicate the previous config item
* Use offset 0x3114, 4byte for the parameter

I cannot assure 100% that this works but it might work.

Sebastian,

Your method works great, when using one switch at the time,
but when using more than one at the same time, of course it fails to toggle both.
That's why EVENT ID support is needed..

Appreciate your help,
Yuval.

What's the reason to toggle more than one switch at the same time? Do you have one switch which shall toggle two functions or two switches which you use at the same time?

For example, 4 landing lights switches, 2 apu bleed , 4 window heat etc.

Und es wär halt einfach super komfortabel und easy so schnell Schalter und damit eine ganze PMDG-Maschine mittels Event-IDs zuzuweisen.

Würde mich sehr freuen wenn das klappt! Und danke für die prima Arbeit bisher.

LG
Tom

For example, 4 landing lights switches, 2 apu bleed , 4 window heat etc.

you want to trigger each group by a single switch?

For example, 4 landing lights switches, 2 apu bleed , 4 window heat etc.

you want to trigger each group by a single switch?

The opposite, i'm building a 737 OH and i want to put 4 switches for the landing lights.
If i will use your method i will have to touch 1 switch at the time. But off course i would like the push all 4 (or just 2) at the same time (with my hand) like the reality, and it wont work.

Yuval.

Decrease the fsuipc polling interval to 100ms in the settings section and try again. Another workaround would be to try the normal "landing light"-offset and assign this to all four switches. It might work for you, because one always want to set all on or not.

Regarding APU bleed, you might also acostume to use both switches individually... 100ms is quite fast.

Integration of SimConnect really is a bigger task - i would have to put all this new stuff in, since we are talking about an FSUIPC restriction here. I am using an Overhead panel for B737 and it never bothered me. Actually I like to have to switch all 4 switches for window heat one by one and it is actually authentic... doing this faster than 100ms per switch is not necessary nor possible for me.

Tested again with 100ms interval, still same results, there is no way to acces Event ID's from fsuipc without using the offsets?
How does it works in the Buttons + Switches tab in the FSUIPC sim menu? I was able to access these Event ID's with my joystick from there.

Yuval.

So maybe it helps when you are able to send keyboard strokes with the next version 6.0. You could make the assignment for these switches through FSUIPC then. I don't know how FSUIPC internally handles event ids, maybe it uses SimConnect. However the FSUIPC api does not permit the setting better than currently implemented in MobiFlight Connector.

Is there any option to create fictional key storkes, more than the ones on the keyboard? this will allow unlimited inputs.

BTW, LINDA provides good EventID support and works with FSUIPC

Sebastian,
Ive done some research about using controls with FSUIPC and LUA, and found that this function works well in lua:
ipc.control(control number, parameter) .
Maybe there is some way to implement this function to your software.

Yuval.

I will see if there is a way to improve this. LINDA interfaces differently with FSUIPC.