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

[GiankMustang]

Dear Mr John Dowson, yes it is now “clear enough” to me. A hasty reading and the automatic translator had led me astray. I made a Macro (STANDBY INSTRUMENTS), but when I start the Sim I find the STBY INSTRs always On, whether the Switch is Off or On. Then it works, that is, it turns the STBY INSTRs On and Off, but always regardless of the initial On/Off position of the Switch. I did lots of alternative tests, with FSUIPC and MobiFlight, but I didn't find a way to start the Sim with the STBY INSTRs disabled. Can you help me eliminate this hateful problem. Thank you.

[John Dowson]

Can you please show me / attach both your macro file and your FSUIPC6.ini file.

 

[GiankMustang]

Here are the two files attached. 

Thank you.

1SK CLOCHE.MCRO FSUIPC6.ini

[John Dowson]

3 hours ago, GiankMustang said:

when I start the Sim I find the STBY INSTRs always On, whether the Switch is Off or On.

Then that must be the default value that it has when started. All aircraft switched/buttons/knobs will be in a pre-defined state on start-up, and this may not match the state/positions of your buttons/switches. The state of your physical buttons/switches are not read at start-up and the aircraft but in the same state - you have to start the aircraft with your buttons/switches in the correct position to match the state of the aircraft when started.

You may be able to change the default state somehow but I don't know about this - you would have to ask on the aircraft support forums. Otherwise, you could just send the command to turn standby off when you start, for example by just running that macro, e.g.

[Auto]
1=1SK CLOCHE:StbyInstrum

 

[GiankMustang]

Hello John. 

I apologize because I only now realize that I missed something to say. 

If I DO NOT load MobiFlight before the Sim, the STBY INSTRs are Off (and the Mouse allows you to control them). 

So I deduce that it is the FSUIPC-MobiFlight Macro that forces them On, and not a Default setting of the Plane. 

I hope this will help resolve the problem. 

Thank you. Giancarlo

[John Dowson]

1 minute ago, GiankMustang said:

So I deduce that it is the FSUIPC-MobiFlight Macro that forces them On, and not a Default setting of the Plane. 

But the macro does nothing unless you run it. So, if something is running the macro when you start FSUIPC or MobiFlight, then stop/disable that.
A macro file does nothing by itself - something needs to trigger it to be ran. You can use FSUIPC's logging facilities to determine what,

[GiankMustang]

I used Logging but didn't find anything that seemed abnormal to me. 

Then I loaded the Sim without MobiFlight (i.e. without FSUIPC and Macro) and the two Logging files are practically identical (except for the time). 

I don't know how to go on anymore...

[John Dowson]

Is there a simvar or lvar that holds the current state of this button? If so, log that...
And also please at least activate logging for Events, and attach your log file here (as well as your ini) and I can take a look.

Just defining a macro cannot affect the aircraft state on start-up. Something must be triggering this.

[GiankMustang]

I attach the FSUIPC6.ini file and the FSUIPC6.log file (which I obtained by activating in Logging "Button and Key operations", "Event non-Axis controls" and "Log Lua Plugins separately", as well as "Debug/Trace Lua plugins" which is active by default). 

Regarding Simvar and Ivar, I'm desolate, but unfortunately I don't know what they are and I haven't found anything online. 

Could you please tell me how to record it? Thank you. 

Giancarlo.

FSUIPC6.ini FSUIPC6.log

[John Dowson]

The log file you attached was attached when FSUIPC was still running and also stops after 30 seconds.

You are also using an old an unsupported version of FSUIPC. Only the latest version is supported - please update.

And your ini file shows that you are not actually using FSUIPC for anything. You only have one (strange) button assignment, you have profiles but they are empty, and you [MacroFiles] section is very weird...

Are you assigning in MobiFlight? i cannot support mobiflight - please use their support channels (discord) for issues with MF.

[GiankMustang]

Ok, here are the final clarifications. 

I bought FSUIPC 6,2,0 after reading on the site that it is compatible with P3D 4 5 and 6 (I now read that the latest version is 6,2,2). 

I do FSUIPC assignments through MobiFlight. I create the Macros with FSUIPC and assign them through MF. 

The [MacroFiles] section contains old tests that I deleted some time ago. 

From your words I deduce that the problems depend on MF, and I will address them. 

Thanks again for your availability.