A new Mobiflight update just came out that allows you to access events not available in Simconnect, through simply adding them in a text file. You can look up the event through the developer mode of the sim. It is working unbelievable easy!
It allows me now e.g. to control the G3X knobs through Python Simconnect. This will make creating your own button boxes far more easy and cool!
Yep, it is. Just put the mobiflight-event-module in the community folder, and then you can use the standard python simconnect interface to connect.
E.g. to set the G1000 zoom, you’ll use (so a little bit different syntax than the standard SimConnect commands):
event_to_trigger = Event(b’MobiFlight.AS1000_MFD_RANGE_INC’, sm)
event_to_trigger()
This is included standard in the Mobilflight wasm module. But now you can add additional ones in the events.txt file. E.g. for the G3X zoom, you’ll need to add AS3X_Touch_1_Knob_Inner_R_INC in the events.txt, and then in Python:
event_to_trigger = Event(b’Mobiflight.AS3X_Touch_1_Knob_Inner_R_INC’, sm)
event_to_trigger()
The correct syntax for a specific knob or button can be found in the developer mode. I don’t know the correct menu item from the top of my head, but it is not too difficult to figure out.
You don’t need to use Python to interact these new events. The WASM module is adding new SimConnect events and anything that uses SimConnect can trigger them, for example FSUIPC.
That’s great to hear, I use touch portal on a tablet and it can send simconnect events.
I guess the following needs to happen for TP to be able to send these new commands
1 Place the new mobiflight-event-module in the community folder
2 Touch portal plugin needs to be updated
I tried to figure this out the other day, but couldn’t find an option in the menu that seemed to help. I’m assuming there’s some kind of tool in developer mode that will let you click on buttons in the cockpit while displaying a log of impacted variable names and values for those buttons? If so, I’d be grateful for a little help figuring out how to access it.
Turn developer mode on, then go to Windows, Model Behaviours. Select the XML with interior in its name. And then you have to play a bit with the root components and the childs and check what comes up below that. It’s a bit a trial and error approach… (at least for me).