I REPEAT, MACROS DO NOT WORK

[GiankMustang]

I REPEAT THIS EMAIL WHICH I CAN'T FIND IN THE FORUM, MAYBE DUE TO SOME MISTAKES OF MY OWN.

Greetings.
I finished building a Home Cockpit of the Citation Mustang. 
I have FSUIPC 6.2 running with P3D 5.4, Citation Mustang 2.1 (Flight1), MobiFlight 7.8 and Win 10 Home. All declared mutually compatible (and obviously all licensed).

I read the instructions on Macros in the “FSUIPC User Guide for 6.1”, but it is incomplete.
In fact I apply it all, but in the end it is not explained how to assign that Macro to a Cockpit Button. 

Can you please tell me how I should proceed, or point me to a tutorial?
Thank you.

[John Dowson]

11 minutes ago, GiankMustang said:

I REPEAT THIS EMAIL WHICH I CAN'T FIND IN THE FORUM, MAYBE DUE TO SOME MISTAKES OF MY OWN.

No need to shout...

14 minutes ago, GiankMustang said:

I read the instructions on Macros in the “FSUIPC User Guide for 6.1”, but it is incomplete. In fact I apply it all, but in the end it is not explained how to assign that Macro to a Cockpit Button. Can you please tell me how I should proceed, or point me to a tutorial?

Once a  macro is created, you would assign to the macro as you would any FS control, as stated in the User guide (relevant part in bold):

Quote

Mouse Macros

In addition to all of the available FS controls, and the specially provided FSUIPC4 additions, you can easily make your own controls, naming them yourself, to operate any Panel switches, knobs and buttons and knobs for which possibly otherwise you would have to use the mouse.

These “mouse macros” do not actually use the mouse at all, but use a set of “mousetraps” to identify what your own mouse operation does, and records, in a “macro” file (type mcro) the details so that the same action can be performed subsequently without using the mouse at all.

This is done once for each mouse action you want to replace with a button or keypress operation, and it merely involves running in a special “mousetrap” mode. The macro file needed is created for you, with your filename and your individual and assignable control names. Once you’ve created some, the drop-down lists of controls in both the Keys and Buttons tabs of FSUIPC will include them for you to assign as you wish. Macros appear in the list with the full name:

    file: macro

If you generated a series of mouse macros for, say, a 767, you might call the file “767”, with, perhaps, the APU switch called “APU”. The control would then be listed as:

   767: APU

Since all of the listed controls are sorted into alphanumeric order, all of the 767: ... controls would be there together, easy to find and assign.

Is that not clear enough?

Regards,

John