GiankMustang

[QUOTE John] Did you follow the instructions, e.g. you have to assign to the press AND release. I think YES. I've included the Assignments for the problematic ones (AVIONICS now works!). 1) STBY INSTR (Does NOT work with Mustang.LUA. It works with MACRO.) FSUIPC: KeyPress / ProfSpec / Set / Shift+Alt+F12 / Throttle4 Set / Para=0 / Confirm MobiFli: eventID / Throttle4_Set / Use / 65823 / Press Para=1 Rel Para=0 2) ENG SYNC (Does NOT work with Mustang.LUA. It works with MACRO.) FSUIPC: KeyPress / ProfSpec / Set / Ctrl+Alt+F4 / Throttle4 Set / Para=16 / Confirm MobiFli: eventID / Throttle4_Set / Use / 65823 / Press Para=326 / Rel Para=0 3) LEFT START1 (&2) (Does NOT turn on the START light with Mustang.LUA! Does NOT create the MACRO!) FSUIPC: KeyPress / ProfSpec / Set / Shift+Alt+F5 / Throttle4 Set / Para=4 / Confirm MobiFli: eventID / TOGGLE_STARTER1 / Use / 66300 Let me clarify that with the ClickMouse it works like this: I press the START button which lights up, the RPMs go from zero to IDLE in 16 seconds, the engine starts and the button loses its lighting. So since you can't create the Macro that Emulates the ClickMouse, the START Buttons never light up on the Cockpit. [QUOTE John] Last time he posted was in 2007 (The last time he posted was in 2007) He hasn't posted in almost 20 years! I don't think it's worth bothering him, assuming he's still interested in the subject. Also, since you tagged him, he might be the one to join... Thanks, as always. Giancarlo

Dear John. After many attempts, finally now THROTTLE CUTOFF also works perfectly, although unfortunately I did not understand why it did not work before. Now almost all Mustang.LUA commands work. Except AVIONICS and ENGINE-SYNC which I make work via Macro, and except the two STARTs which do not backlight when activated. For these reasons, and for other less important ones, I would like to be able to communicate directly with the programmer of Mustang.LUA, Mr. GC McMillen. Do you think you can give me his Email? [QUOTE John] No - I do not have this aircraft and cannot look onto this. Ok, even without having it you have done a lot for my understanding. Thanks again for everything. Giancarlo.

[QUOTE John] You have asked this before. Sorry, I forgot.

[QUOTE John] Why don't you try this? I tried, and I have to say... you were right. I finally tested the entire “LuaSet F1MustangSwCtl.lua” package, which is a big step forward compared to Mustang Flight1, however I found some obstacles: 1- THROTTLE CUTOFF. To turn off an engine, I set the Throttle to CUTOFF, but the engine does NOT turn off, the rpm go to minimum in IDLE but do not go to zero, in fact FUELBOOST does not turn off on the CAS-MSG. To turn off the engine I should act on DISENGAGE, but it is a subterfuge because this only cuts the electrical power, while CUTOFF cuts the fuel. 2- STBY-AVIONICS and ENGINE-SYNC. I could not make them work in any way, so I programmed them with Mouse Macros. 3- The START Buttons do not light up while they are working. These incorrect behaviors do not exist in the Mustang F1, nor in the Mustang True. My friend and consultant, who is a true pilot of true Mustang, confirms this to me. Do you have a solution to these Problems again? Thanks again. Giancarlo.

I copy and paste my emails from Translator to Word, and then from Word to the Forum. But if I click “Pasted as rich text” they come out “blank”. If I click “Paste as plain text instead”, I lose all the formatting (Bold, Line spacing, underline, line break, etc.) and have to re-edit everything online. How should I avoid this? Should I use a particular Font? Which one?

Dear John. I clarify that when I wrote "I managed to assign some of the LUA Commands for the Mustang Flight1", it was obviously implied that those already assigned worked! That's why I didn't send you my files, that is, I considered your request superseded. But I'm sending them to you now (FSUIPC6.log FSUIPC6.ini). Regarding the Mustang vars list (similar to the C172 one), you say it is: [QUOTE John] "In the FSUIPC log file (i.e. FSUIPC6.log for FSUIPC6), exactly as indicated in the documentation". But as you can see it is not there. Will I have to give up? [QUOTE John] “to control the master warning switch you should assign a ‘LuaSet F1MustangSwCtl’ with a parameter of 17”. Sorry but I think I understood that 17 is just a progressive number, while the Parameter is 32, in fact with 32 it works and with 17 it doesn’t. Thanks for everything. Giancarlo FSUIPC6.ini FSUIPC6.log

Dear John Finally, thanks to your encouragement, I managed to assign some of the LUA package Commands for Mustang Flight1. [QUOTE] see the section “Gauge local variable access (L:vars)” on page 39 of the Advanced User Guide I had translated and read that Guide a long time ago, but unfortunately it is not user friendly. Furthermore, there are some things for which I do not find confirmation. For example: “Lvars can now be Listed in the Log”, and as an example it shows the list of the Cessna 172. But I do not find the Mustang List in any Log (neither in F1MustangSwCtl.log nor in FSUIPC6.log). I can extract only FEW Commands from the Script “F1MustangSwCtl.lua” (but it is neither .log nor List). In which Log is the complete list of the Mustang contained? [QUOTE] the aircraft name is "F1_Cessna_Mustang1". The name is probably different in P3D The name is the same in both FSX and P3D. [QUOTE] control number 65823 is Throttle4 Set so I do not understand that comment That number is present in almost all 20 Controls of the F1MustangSwCtl.lua script with parameters from 1 to 326 (See the attached file F1MustangSwCtl.lua). It certainly represents a Command not used in the Mustang, in fact I remember your explanation of 15/4/2025 “Sometimes aircraft developpers re-purpose controls that are not used for other purposes”. I’ll show you how I did it (I hope it can be useful to someone): Master WARNING (pushbutton) FSUIPC: KeyPress / ProfileSpecific / Set: Shift+Alt+F2 (example) / Control: Throttle4 Set / Confirm MobiFlight: Action: eventID / Throttle4 Set / Use (eventID: 65823) / Para: 32 Can you tell me if you think there is a better way? Now I will have to complete the assignment of all the other Commands present in the F1MustangSwCtl.lua and all the other non-Lua ones. If I encounter other obstacles, I will consult you again… Thanks for everything. Giancarlo F1MustangSwCtl.lua

I see the black box Text Original or Plain again... Ok, thank you, now I understand the difference between file.lua file.mcro and lvars. [QUOTE] “the easiest way to use lvars is to write a macro”. But for some Commands I can't make the Macro, because the area where to insert the Name doesn't appear. Lua was born precisely to make up for this deficiency (but also others...). In fact the Guide “FSUIPC Lua Plug-Ins”, of the “F1MustangSwCtl.zip” says: “Contains a Lua plugin to emulate certain mouse click controls for the Mustang subpanel and console switches”. But unfortunately despite the many tests done, even on other Commands, I can't make it work. I report the Script part of the file “F1MustangSwCtl.lua” regarding the “MASTER WARNING” Command: elseif ipc.testflag(17) then -- Emulate the MASTER WARNING switch mouse area. -- Using a pushbutton switch, -- Assign parameter = 17 to Switch "pressed" only clearflag(17) ipc.control(65823,32) -- send 32 (>L:ENGINE4_SET) I have inserted in various ways: (17), (65823), (32), etc., with no result, and I don't understand where I am going wrong. From the Guides and Translators I have squeezed everything there was to squeeze... Could you please give me a short tutorial? Otherwise I should seriously consider having to throw away so much work... and money... Thanks.

I can't post. My email are blank. I copy and paste from the traslator. Can you tell me which FONT I should use? Thanks.

[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

I don't know why some of my emails are blank. As always, I copy and paste from Google Translate.

[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.

Error. Here is the file. FSUIPC6.log

“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#

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