John Dowson

As I said, I want to see your script and log files, not a video...there is no way I can tell what is happening from a video of the console log.....

There should be no difference in the actual execution of lua scripts, as the lua engine in FSUIPC7 is identical to the one in FSUIPC5. Any difference will be due to the simulator being used, and also, as FSUIPC5 is an embedded dll in P3D, and FSUIPC7 is a separate application, there will be a slight overhead with the communication to the FS (via SimConnect). What exactly is much slower? Can you show me the script, and both an FSUIPC7.log file and FSUIPC5.log file showing this performance issue.

You can log any offset - see the right-hand side of the Logging tab, and the User Guide, starting from page 17. You need to look/search the Offset status document for general offsets, and the PMDG offset document for PMDG specific ones. For the general offsets, see: And for the PMDG 737 specific ones, I can only see the following offset specific to the NGXu : Although there are others for annunciators relating to the auto-throttle state, e.g.: John

As I said, that is not needed in the latest version as that is now the default. You need to set this to the appropriate number if you want the pump offsets populated - see the Offset status document for details. No problem. Glad you isolated the issue - and maybe you should report this to GSX. Regards, John

But you still need to use the latest version, which includes the changes in that older beta version. As i said previously, please try with the console log open, and see what, if anything, is logged just before this pause, during and after - and using the latest released version. Did you install the WASM? Can you try with that installed, but without any other software (e.g. your Java Simulations glare fcu panel) to see if you get this pause/stutter then. Also try with the MSFS console window open (you need to be in dev mode), and see if MSFS is reporting anything.

But why are you doing this? That thread is old and the version there is older than the released version, which is also why you are getting those warnings. Please try the latest released version.

What version of FSUIPC7 are you using? You say you are using the latest as-of today, but 7.3.20 is the latest and should be using WAPI 1.0.2. Check the version logged at the top of your FSUIPC7.log file. Those warnings indicate a mismatch between the installed version of FSUIPC7 and the FSUIPC WASM module, but should not cause any issues. To resolve, make sure you are running the latest version of FSUIPC7, which I don't think you can be... John

First, please do not post continuation logs for support, i.e. do NOT use the New Log feature. I always need to see the full log file. Looking at your log file, you can see: 751343 LUA: Could not open HID This is most probably due to the fact that the device is a keyboard device. Are the keys not recognised by FSUIPC7 in the key assignments panel? If not, you could try setting UseKeyboardHook=Yes in the [General] section of your FSUIPC7.ini file. This will tell FSUIPC7 to receive its keyboard input directly from Windows rather than from MSFS. and can help when using additional keyboard controllers. See the Advanced User guide for details. For this issue, your logs show that FSUIPC is behaving as expected. The problem is that FSUIPC is continually seeing button press and release events, and so is acting on these press/release events and setting/clearing the parking brake. Is the same happening for your other button assignments on your Saitek Pro Flight Quadrant? e.g. what about these assignments: If the same thing is happening with the other buttons, then you need to try and determine what update caused this. Did you install any Saitek drivers or software? If so, try removing that - you should only use the windows default drivers with Saitek controllers if using FSUIPC. Otherwise, if it is only happening for this button, I suspect that there is a hardware issue with that button... John

That is the default and not needed. Every time? Do you have auto-save enabled? FSUIPC doesn't do anything special on touchdown. Do you see anything in your FSUIPC7.log file? You can post/attach it here, but it would be better if you could try landing with the FSUIPC logging console open (Log -> Open Console...) and see what, if anything, is logged when this occurs.

Yes, of course. John

You can use event.terminate to get a callback in a lua script before it is stopped. You can also try with event.sim to get notification of certain sim events, including aircraft change, although I am not sure how reliable these events are in MSFS.

No - this file is from 24/03/2023 and from FSUIPC7 version 7.3.19, whereas your FSUIPC7.ini file is from version 7.3.20 (the latest version). If you cannot see the FSUIPC7.log file, you probably have windows explorer set to hide the extension of known file types. Then, if you have set the logging as I have asked, then either the extension is hidden, as with the FSUIPC7.log file, or the lua script is not running. How are you starting the HidDemo.lua script? I see no [Auto] section in your FSUIPC7.ini that starts this. So, please check that the lua script is actually running. Then, once you have confirmed that it is running, please provide the files I asked for with the logging asked for (and no other logging). For your parking brake issue, please also attach the ini file for the aircraft/profile that you are using, and please keep the test as short as possible, i.e. load your aircraft, press the button to activate the parking brake, then release. Then exit FSUIPC7 and show me the files requested. Note that you have two issues, and I expect to see two sets of files, one for each issue, as they are not related. In future, please create a separate topic for each issue. Looking at the in you attached. it looks like you are trying to comment out lines by using the double back-slash '//'. Those characters do NOT designate a comment in an ini file. Use the semicolon ';' instead. Also, change to i.e. use substrings for your aircraft profile names John

No, you should use the number.

Sorry but I don't understand. What is a 'chassis crane'? What do you want to do?

Why? The preset is a name, and the documentation for this function is: The only number needed is the parameter, if the preset uses one (most don't). John

Can you not do this yourself? Why don't you just try running it, and use the provided debugging facilities if you have any issues. As you are not using the double press, then you should at least remove the following line (as it will create an error if you do double-press): ipc.control() Or, better still, remove the code that handles a double-press completely if not using this. John

Activate logging for Events (Log->Events) and open the logging console (Log->Open Console) and see if anything is logged. However, at the moment, since the latest SU release, many events are not logged as they are now using the new *_EX1 event system. I have an update for this to be able to catch such events, but this is not yet released. This will be in the next release (7.3.21). Also note that only standard events/controls are logged. You will not see any preset names being logged, as these are not actually used by the aircraft. The code for a preset mimicks what happens when a VC control is activated.

No, that won't work, as you are changing the variable value. You can use one script if you know what you are doing (I am not going to explain this to you...!), but it is probably easier to use a separate script for each button. What don't you understand? Your script contains the following lines to execute the control/event: ipc.control(67279) So that sends the control AUTO_THROTTLE_DISCONNECT. To send a preset instead, change that to: ipc.execPreset("presetName") where presetName is the name of the preset. Or add the parameter if the preset uses one, e.g. ipc.execPreset("presetName", param) John

For presets, just use ipc.execPreset instead of ipc.control John

No, mouse macros are not possible with MSFS2020.

Take a look at the TripleUse.lua script which is included in the lua examples (zipped in your FSUIPC7 Documents folder). There is also a more advanced version of this lua script available in the User Contributions sub-forum: You should be able to adapt either one of those for your needs. John

The presets provided are a community effort, led by MobiFlight. If there are currently no presets available for this aircraft, it is because nobody has yet submitted any. You can define your own presets if you like, using the myevents.txt file (see Advanced user guide, WASM section). You should also submit any presets you create to MF, so that they can be used by others. However, looking at the Headwind A330, it does say that it is based on the FBW A32NX, so you may find that many of the presets for that aircraft also work with the A330.

To enable debugging in one script, just restart it by using the LuaDebug control. If you want to be able to turn debug logging on and off in a script without restarting it, add the following code to your lua script: Then, to turn on/off debugging in the script, you can assign a button or key press to the control LuaValue <scriptName> (where <scriptName> is the name of the lua script) with a parameter value of 1 for turning on debug logging, and 0 to turn it off. You can also change the debug logging function or the type of hook to suit your needs - again, see the ipcDebug.lua script for an additional debug logging function, and see the lua documentation on the debug library and the sethook function.

I am still not 100% sure in what you are trying to achieve.... If you want lua debug logging active in one script only, I have explained how to do that, If you want to be able to turn debug logging on and off in the script itself, this is not possible as things are. However, if you want to do this, you can add two additional functions to the ipcDebug.lua to add and remove the debug hooks, and then include/require that and use them. You can even use the ipcPARAM parameter to determine if debug logging should be enabled or not when you start the script, if you so wish. So, anything should be possible really. Just take a look at the ipcDebug.lua script, and look at the lua documentation for the debug.sethook function.

Whatever you want - this value is just passe to the lua script in the ipcPARAM variable.