Jump to content
The simFlight Network Forums

GiankMustang

Members
  • Posts

    27
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Private

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

GiankMustang's Achievements

Apprentice

Apprentice (3/14)

  • Collaborator Rare
  • One Month Later Rare
  • Week One Done
  • Dedicated Rare
  • First Post Rare

Recent Badges

0

Reputation

  1. 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
  2. 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.
  3. 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.
  4. [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
  5. I don't know why some of my emails are blank. As always, I copy and paste from Google Translate.
  6. [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.
  7. “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#
  8. 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
  9. 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?
  10. 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.
  11. 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
  12. 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...
  13. 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
  14. Here are the two files attached. Thank you. 1SK CLOCHE.MCRO FSUIPC6.ini
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.