MobiFlight Community Support

Hello,

Is it possible to give a mouse MACRO an EVENT ID code?

I'm trying to set mobiflight to work with the F1 ATR72.
Now some of the default EVENTIDs do work, but some doesn't' for example HDG BUG INC/DEC and most of the MCP and Overhead switches.
So I created mouse MACROS to use with the key option in mobiflight, it's working, but I was wondering if it is possible to tell the fsuipc to trigger MACRO using random EVENTID, it's more practical for me than to find out now which keyboard keys P3D doesn't use......

Thanks. Jonathan.

Hi Jonathan.

1. Logging Tool.
When you use Macros i think you got a registred FSUIPC..... So You got the Logging Console Window tool.
If you like you can test if there are EventID´s instead of the standard list. Just Scan for "Events" and push the Virtual Button in Simulator.
The Logging will show you what Event is started.... MABY you find out and can use THIS Event direct in Mobiflight !


2. Individual self generating EventID
Sorry. I don´t know.... But i don´t think so. The Events are fix in FSUIPC or FSX. Shure you can do this but not on normal ways. If you got high skills in programming you need to rewrite the original files of the Sim to make this working i think ! .... But keep Cool.... Next Points will help you !


3. Macro Run.
Sebastian and me just think about that some time ago, but have technical Problems to get this working. Solution would be the Offset 0D6C and 0D70.
This is the Interface to run specifc Lua Scripts or Macros via a external Software !
But again... We can´t get it running until now. This is on ToDo List already. At the moment the LCD have Priority.... But we try to impliment this in the future !


4. Alternate ways
Instead of the Key Binds you can use Joystickbuttons to run Lua Macros. If you wan´t to use a Gamecontroller or maby a Controller like LeoBodnar or Arkaze you can set this stuff external of Mobiflight !
BUT
Theres a easy way to do this with Mobiflight too if you not like to use a different Controller in Cokpit.....
You can set "Virtual Joystickbuttons" Via Mobiflight..... AND Then Set to this Buttons in FSUIPC the Macros you like.
Please look to Offset 3340

This area is used for externally signalled “joystick button”
control, a set of 288 "virtual buttons". Each DWORD or 32 bits
represents one “joystick” with 32 buttons. If an external program
sets or clears a bit in any of these 9 DWORDS the “Buttons”
page in FSUIPC will register the change as a button operation on
one of Joystick numbers 64 to 73 (corresponding to the 9
DWORDs). So, FSUIPC can be used to program whatever
actions the user wants.

So if you push a button in youre cockpit Mobiflight will send a Data BIT to a specific offset and simulate a button Push of this Virtual Joystick.
For FSUIPC it looks like a real Joystickbutton is pushed. Now you simply set this Virtual Joystick Button to the Macro !
I think this is self explaned.... If you need help here... Let me know !

*********
So.... I know it´s not perfect at the moment....But it workes ( even its difficult) . Please stay patient. We try to implement better elements for this in the future !

Thank you for your answer.

The virtual joystick buttons is a good solution for now,
Where can I find more information about how to practically do it ? (im using only mobiflight right now).

Thank you for your answer.

The virtual joystick buttons is a good solution for now,
Where can I find more information about how to practically do it ? (im using only mobiflight right now).

This was already discussed in the german board section....
i hoped youre skill is advanced enough to check this youreself.. So now i try to explane it in short words....

The offset Section on 3340 is a 36 Byte Area... This include nine D-Words.... this means 9 Blocks of 4 Byte Offsets.
Every 4 Byte Offset inclode 4x8=32 BITS..... And Every BIT represent 1 Joystickbutton.
For Example Offset 3340 4 Byte ... BIT 0 means Joystick nr. 64, Button 0 ........... Bit 23 for example means Button 23 of same Joystick nr 64 .
If you like to set Joystick 65 then you need the SECOND Dword 4 Byte Block. this start on Offset 3344 ( 4 Byte more then 3340 )

Now simply write this Bits ( Bitmask in Mobiflight) with "1" for a Button Push... or "0" for a release .
With Push buttons its simple.... Use ON PRESS and write "1" to the BIT..... On Release to write "0" ...
Then a momentary Push to the button is for FSUIPC the same like a Joystick Button Aktion ( you push it and release it short after ).

Please Note... A verry short pushing can occure in issues... Please just hold the button for 0,5 sec befor release it to get shure both commands arrive the Simulator !

Hope this expaning is ok.... If not ask again for more details!

Thank you very much pizman82,

I didn't know about that and while doing my 757 project, I was wondering about how I can manage to assign all these buttons for keyboards. This helped me very very much. Now it is much more easier than finding an unassigned keyboard key and make it work with mobi (with all the steps you know)...

Best regards...

Just for information....

Normaly all advanced Cockpitbuilders delete all keybindings in FSX before they start.

Note that 90% of the Standard Keys are not needed in a type specific simulator like a B737.... AND for more tidy logic you can set the real needed things in FSUIPC direct again
On Top are the AddOn Keys... For Example PMDG use own Key Bindings for some special elements.

So i would recommend to delete the FSX Keys or maby to delete all 100% Not needed Keys.... After that you got hundrets of free Keys for youre Inputs !