The “Warning” Macro does not create

[GiankMustang]

Dear Mr. Dowson
I can't create the "Warning" Macro (other Macros don't give me problems).
I follow the procedure exactly as per the FSUIPC User Guide 6.1 manual, but the area where to enter the Macro Name doesn't appear, so it's impossible to finish the Macro.
I should point out that "Message Text" is enabled by default.
I use FSUIPC 6.2, P3D 5.4, Citation Mustang 2.1 by Flight1, Win10 (obviously all licensed).
Can you help me?

[John Dowson]

First, when pasting text, please paste as plain text so that I don't see those annoying scroll bars...

21 hours ago, GiankMustang said:

I can't create the "Warning" Macro (other Macros don't give me problems).

A macro is a macro....

If you have instructed FSUIPC to start the macro making process and the multiline simconnect message window does not appear when you click in the area that you want to create the macro for, then either the aircraft does not support macros (not all aircraft do) or there is no macro (i.e. mouse rectangle) available in the area that you clicked.

John

[GiankMustang]

Thank you for your reply. 

I clarify that other Macros work, and that “Master Warning” with the mouse click works. 

However, I note that for “Warning” (and perhaps for other commands) there are no Offsets, Events or Macros.

As far as you know, is there any SW that makes up for these shortcomings? 

I tried KeyToMouse but… it is not suitable for the purpose. 

I have completed the my HomeCockpit, but due to some commands I cannot get the best out of it. 

Regarding the “annoying scroll bars”, I clarify that I pasted the translation exactly as “plain text” (the alternative was “rich text”). 

Thanks Giancarlo

[John Dowson]

1 minute ago, GiankMustang said:

I clarify that other Macros work, and that “Master Warning” with the mouse click works. 

However, I note that for “Warning” (and perhaps for other commands) there are no Offsets, Events or Macros.

If mouse-macros work for other switches, it seems strange that there is not one for this. But what exactly is "Warning"?
If you log Events, do you not see anything when you click this in the VC? If anything is logged, then you can use that.

I don't have this aircraft so I cannot look into this, sorry. You can check to see if there are any lvars available for this - try listing the available lvars and see if any look applicable (there is an FSUIPC-added control to log available lvars).
Otherwise, ask on the aircraft support forums to see if / how this can be controlled.

5 minutes ago, GiankMustang said:

Regarding the “annoying scroll bars”, I clarify that I pasted the translation exactly as “plain text” (the alternative was “rich text”). 

Well, that last message was good - no scroll bars!

John

[GiankMustang]

“Master Warning” and “Master Caution” are two big Lights that signal Anomalies, fundamental in real and simulated flight. 
In the attached photo I circled them in Red. You press them to turn them off.

I opened the Sim, clicked with the mouse on “Master Warning” and immediately closed the Sim.
Examining Events (FSUIPC6.log that I attach), I note the lines “16953 KEYDOWN: VK=17…” and “17391 KEYDOWN: VK=67...”, 
I think that the second of the two is “him”, but… it does not create the Macro.

About the LVars I have not found any reference on the PC about it.
Searching online, I read that Installing FSUIPC also installs WASM which includes HVars and LVars.
Is this what I have to do?

Regarding Mustang Flight1 Support, I have to say that unfortunately some time ago, after my in-depth question, 
the next day they stated on the site that the Mustang is no longer supported! There is nothing about it in the pre-existing forum.

.~lock.2 Mail a FSUIPC - La Macro “Warning” non si crea.doc#

[GiankMustang]

Error. Here is the file.

FSUIPC6.log

[John Dowson]

38 minutes ago, GiankMustang said:

I note the lines “16953 KEYDOWN: VK=17…” and “17391 KEYDOWN: VK=67...”, I think that the second of the two is “him”, but… it does not create the Macro.

No - those log lines indicate keypresses from the keyboard (KEYDOWN).

40 minutes ago, GiankMustang said:

About the LVars I have not found any reference on the PC about it.

See the section Gauge local variable access (L:vars), by macro  in the FSUIPC6 Advanced User guide, page 39.

42 minutes ago, GiankMustang said:

Searching online, I read that Installing FSUIPC also installs WASM which includes HVars and LVars. Is this what I have to do?

No. That is for FSUIPC7 and MSFS2020 / MSFS2024 only.

43 minutes ago, GiankMustang said:

Regarding Mustang Flight1 Support, I have to say that unfortunately some time ago, after my in-depth question, the next day they stated on the site that the Mustang is no longer supported! There is nothing about it in the pre-existing forum.

What is logged when you press that button in the VC? It is not the KEYDOWN. Your log seems to contain many PANEL_ID_OPEN and PANEL_ID_CLOSE events logged with different parameters - maybe these have been repurposed. But I cannot tell from just looking at the log file. You need to do this with the logging console window open so that you can see what is logged when you press the switches in the VC in real time. No point posting the log file - look yourself!

Or look into lvars to see if any are available.

I know what the master warning and caution switches and lights are - its just helpful to me if you tell me in detail what you want to do - sometimes the warning/caution lights are independent from the switches, and I am not familiar with the aircraft you are using.

John

[GiankMustang]

 

[QUOTE]: “No - those log lines (16953 KEYDOWN: VK=17... and 17391 KEYDOWN: VK=67...) indicate keypresses from the keyboard (KEYDOWN).” 

I see that those two lines are the Keyboard Keys (Ctrl+C) that I use to close the Sim and P3D. 

[QUOTE]: “See the section Gauge local variable access (L:vars), by macro in the FSUIPC6 Advanced User guide, page 39.” 

I translated that Guide, it says: 

… can now be listed in the Log, written to via Macros, and manipulated with both reads and writes through extensions to the ipc Lua Library. 

The log listing is obtained for the currently loaded aircraft panels by a new assignable control in the drop-down lists called “List local panel variables” ... 

There are various Lua Library files in Documents / FSUIPC, but I don't understand how to see the Lvars: 

1 Is the Log meant FSUIPC.log ? 

2 How to install the ipc Lua Library ? 

3 What are the drop-down lists ? 

4 How to assign “List local panel variables” ? 

[QUOTE]: “Your log seems to contain many PANEL_ID_OPEN and PANEL_ID_CLOSE events logged with different parameters” 

I see that those Events are cycled every four lines (Param 231 240 250 260). I don't know what they are. 

When I click on the monitor to turn off Master Warning, in FSUIPC.log it is recorded as EVENT: Cntrl= 65568 (0x00010020), Param= 0 (0x00000000) 

HEADING_GYRO_SET and frankly I don't see the connection between Master Warning that I clicked and HEADING_GYRO_SET. 

[QUOTE]: “Warning / Caution ... its just helpful to me if you tell me in detail what you want to do” 

These lights turn on by themselves, and I should be able to turn them off with Macros. 

Thanks again for anything you can tell me. Giancarlo.

[John Dowson]

19 minutes ago, GiankMustang said:

1 Is the Log meant FSUIPC.log ? 

Yes (the FSUIPC6.log file)

19 minutes ago, GiankMustang said:

2 How to install the ipc Lua Library ? 

You don't install it. All lua facilities are always available.

19 minutes ago, GiankMustang said:

3 What are the drop-down lists ? 

4 How to assign “List local panel variables” ? 

Here (in key assignments):

34 minutes ago, GiankMustang said:

When I click on the monitor to turn off Master Warning, in FSUIPC.log it is recorded as EVENT: Cntrl= 65568 (0x00010020), Param= 0 (0x00000000) 

HEADING_GYRO_SET and frankly I don't see the connection between Master Warning that I clicked and HEADING_GYRO_SET. 

Sometimes aircraft developers re-purpose controls that are not used for other purposes (usually the ROTOR_BRAKE control as this is never used in airplanes). You can try assigning to that to see if it works, but that may be just a coincidence or a side-effect.

36 minutes ago, GiankMustang said:

These lights turn on by themselves, and I should be able to turn them off with Macros. 

Mouse macros are only available where provided by the aircraft developer. If you are trying to create a mouse macro in an area that is not supported, then that is because the developers have not allowed this and FSUIPC cannot create a mouse macro where no support for this is provided.

John

[John Dowson]

@GiankMustang Posting empty posts again....I will delete those last two....

[GiankMustang]

I don't know why some of my emails are blank.

As always, I copy and paste from Google Translate.

[GiankMustang]

[QUOTE]: You can try assigning to that to see if it works (MASTER WARNING → HEADING_GYRO_SET)
Unfortunately it doesn't work.

[QUOTE]: Mouse macros are only available where provided by the aircraft developer. 
Bad news! 
Ultimately I can only turn off those Warning Lights with the Mouse.
I tried Key2Mouse which simulates the mouse click, but unfortunately it only works on the active window (= which has the Focus). 
The owner of K2M, Mr. Luciano Napolitano, confirmed this to me.
My Cockpit panel has various instruments and therefore various windows, only one of which is active, and it is not the MASTER WARNING one.

I tried with AutoHotKey, but it is a programming language that is rather difficult for me.
As far as you know, is there any SW capable of clicking on the coordinates even without the active window?

Thanks again for your availability. Giancarlo

[John Dowson]

3 hours ago, GiankMustang said:

As far as you know, is there any SW capable of clicking on the coordinates even without the active window?

No, and I don't think this is even possible. Windows itself receives mouse-clicks and then
  1. If the mouse-click is in the window that has the focus, then it will send the mouse-click to the application that owns the window with the focus
  2. If the mouse-click is in the window without the focus, it gives the application/window the focus
Therefore for the FS to receive the mouse-click, it will need the focus first.

If the place you want to send a mouse-click to is always in the same position or same relative position, you could write a small lua scrip to do this for you.
The lua script should:
   1. First ensure that the FS has the focus by calling ext.focus()
   2. Move the mouse cursor to the correct position using mouse.move(x, y, method)
   3. Send the mouse-click using mouse.click(button)

You can then assign a button or key to activate the lua script.

See the FSUIPC Lua Library documentation for details on these functions, and the FSUIPC Lua Plug-Ins document if not familiar with lua scripts.

John