John Dowson

The one that has the extension .log! You have windows Explorer set to Hide extensions for known file types. Uncheck this option (under Options->View->Advanced settings) and you can then see the extensions.

I have moved your post to the FSUIPC7 / MSFS sub-forum - please use that for all support requests when using FSUIPC7. This should be possible using a lua script. First you have to determine what holds the centre tank fuel quantity. First, try monitoring/logging offset 0x0B74 (FUEL TANK CENTER LEVEL) using FSUIPC's offset logging facilities (log as U32). This should hold the % left (*128*65536). If that looks correct, also log offset 0x0B78 to get the centre tank capacity - you will need this to determine the % value in offset 0x0B74 for 30Kg of fuel. You will also need to convert this from US gallons to kilos. Once you have determined what offset 0x0B74 holds when the centre tank is at 30kg, you can then monitor that offset in a lua script (using event.offset), and when the offset value is equal or is less that the 30Kg %age (that you have determined), you can write 0 to the same offset. If you let me know which aircraft you are using, and I have access to that aircraft, I can help you further. Otherwise, if you can confirm that offsets 0x0B74 and 0x0B78 are used by the aircraft, and let me know what offset 0x0B78 holds, I can provide you with a lua script you can try and customise. Probably next week now though as I have no time this weekend. If those offsets are not being used by the aircraft, you will need to determine what holds the capacity and current quantity. This could be held in other simvars or possibly in lvars. Again, if you let me know the aircraft, I can take a look. John

Further details from @Ray Proudfoot: Settings required to minimise / eliminate the delay when Autosave is enabled for the PMDG aircraft in Prepar3D all versions. In Windows 11 select Start - Settings. On the left menu select Privacy and security. At the top of the list select Windows Security. Select Virus and threat protection. Under Virus and threat protection settings select Manage settings. Scroll down to Exclusions. Select Add or remove exclusions Click "+ Add an exclusion" Add the following choosing File from the drop-down. Prepar3d.exe Add the following choosing Folder from the drop-down The folder containing FSUIPC6.dll The following folder. Your initial path may differ. C:\P3Dv5\PMDG\PMDG737NGXu\PanelState C:\Users\[username]\Documents\Prepar3D v5 Files Add the following choosing File Type from the drop-down. FXML PLN WX After adding those and with Autosave enabled I looked very closely for the autosave action. I barely noticed the save routine and there was no noticeable pause or stutter in P3D. My thanks to @Yakpilot for his post giving this extra info.

You only have the aileron axis assigned in one profile: Your log shows that you were using this aircraft: which is in this profile: i.e. you have no assignments to the aileron om the profile for that aircraft. I do not understand why you have different profiles for the same aircraft, different liveries. You should use one profile, and change the aircraft name in that profile to catch all variants, e.g. And make sure you have the aileron assigned and calibrated in that profile. John

As I said, no - it is not possible to read the status of a button flag from an offset. There is a "hot button" facility, where you can register to detect joystick button presses (see offset 0x2910), but not to read the status of a button flag. These are kept in internal data structures.

Ah, so it is a FAQ entry already! Maybe you could add those details to the FAQ entry for others? Cheers Ray - take care, John

No - going to post the new version now....

Thats good - if I remember correctly, most folks seem to still get a pause of a second or more, even after excluding files/folders from anti-virus scanning... Can you post the link here please - I may create a FAQ entry for this.... Yes, but it is even worse...and the flight save function is still not documented as working (although flight load is!) and so the auto-save is still noy 100% reliable. Some folks seem to have more luck with this than others....no idea why! Cheers Ray, John

Yes, this is a well know issue with auto-save and complex aircraft, such as the PMDG 737. The only thing that can be done to reduce pause times is to exclude the folder where the files are saved from any anti-virus software, but you may still get pauses lasting several seconds. There is also an autosave enable/disable control, which can be used to enable/disable autosave when it has been activated. Some folks use this to disable autosave on take-off and landing to prevent such pauses during critical moments. You could even have a lua script that enables/disables autosave automatically, maybe using the aircraft altitude above ground. Cheers, John

This is because you are using an unregistered/unlicensed version. If you have a license, you need to enter the details and validate them at the end of the installation process. If you do not have a license but would like to try the registered facilities, post in the trial license topic (at the top of this forum) and I will PM you a trial license (time-limited). John

The "InputEvent received but not known:" messages were logged as no input events were received. This was because they were being requested to early - I have corrected this in the next update which I will release shortly. in the beta announcement thread. Please update and try this when released. And please remember to report any issues in the beta release thread, not here. John

Please post any issues with the beta version in the announcement topic (as it says). Can you please repost your issue in that thread. I will look into this tomorrow (and install the improvement mod to check here), but I will respond in the beta announcement topic. John P.S. No point extracting and/or sorting log entries. If a log file is too large to attach, zip/compress it. I always need the full log file.

Thanks for this detailed and well explained contribution! The best way to do this would be using a preset (calculator code). The calc. code of the preset would have to scale the axis value range (usually -16384 to +16383) to the lvar value range before setting the lvar. You can assign an axis directly to a preset - as long as the preset contains a parameter placeholder ($Param or the @ symbol). Regards, John

Yes, but not your FSUIPC7.log file, which I also need to see for this problem...

Yes, there will be. For example, for the TOGGLE_MASTER_BATTERY event: So the parameter is the index of the battery.

This feature has now been released in the latest beta, 7.3.26f. John

In the next release, I will update to log multiple parameters when available. I have tested this in the DA62 with the Left Engine Master On switch, and this is now what is logged: Note that the easiest may to control this switch via assignments is to use the Input Event ENGINE_Master_1. Assignment to Input Events is a new feature and currently only available in the latest beta release, from this topic: I will update the beta available there in the next couple of days with a version that will include this additional parameter logging for events/controls that have more than one parameter. The official release date of this version (7.3.26) is still TBD. John

I would leave the Pollrate and just increase the FastTimeLimit. The rotary script should work reasonably well - if it isn't, try and understand what the script is doing, and try and work out what is happening. As I said. logging is your friend - use it. You can also add additional logging statements (using ipc.log) to help you understand what is happening. If your rotary is a two-phase type rotary switch, thus lua script may not be the best option - see the Advanced User guide om how to handle such rotary types. Otherwise, try to see what is happening yourself using the logging facilities provided.

What do you mean? Your ini file shows that the following 6 controllers are recognised: For some reason, you also have a rudder axis assigned on your Bravo, and a left brake axis assigned on your T.A320 Pilot: Please explain more clearly what your issue actually is, and also show me/attach your FSUIPC7.log file. John

Most toggle events don't take any parameters, but some do in MSFS. Two values are shown, the control/event number, and the parameter. Both numbers are shown as decinmal integers with the hex equivalent after this in brackets. Sime toggle events do have parameters -this is obviously one that does. Only one parameter/indices is currently logged. There currently seems to be some confusion between the events that take multiple parameters and those that don't, and also a similar confusion between standard controls and *_Ex1 controls. This is rather technical, but multiple parameters for events are only seen when received as *_EX1 events. not as standard events. And many EX1 events don't take multiple parameters and are received as standard events, not EX1 events. I will look into trying to log multiple parameters for events when such parameters are received. But note that it is only possible to send events with multiple parameters/indices by using calculator code.

License sent. John

Please find a trial license for FSUIPC7 attached, valid until 1st December. Just save this key file to your FSUIPC7 installation folder and you are good-to-go. Note that time-limited/trial licenses are not validated by the FSUIPC7 installer. Regards, John FSUIPC7.key

License sent. John

Ok, very strange....I don't understand how that can solve your issue, unless your 5.3 client got corrupted somehow, but your symptoms were very strange if that was the case. Thanks for the update. John

Lua scripts are only started once you have an aircraft loaded and ready-to-fly. The log you attached ends after 65 seconds and shows that you were not even connected to MSFS. Please try with an aircraft loaded. There is also an error in your [Auto] section: Should be: As I said, can you please at least check your logs before posting for support - there is no point in showing me your log files until these lua scripts are running. If you are unsure if they are running or not, add the following to the end each of your ButtonBox.lua script: ipc.log("ButtonBox.lua running and waiting for events") and a similar log line to your BU0836X-2.lua script. You will then see that line logged when the script is running. As I said, logging is your friend - please get into the habit of using this to try and solve your own issues. In the button assignment window, so that you can assign to them as you would a normal button However, as these are controlled by the lua script, that needs to be running, which means that you need an aircraft loaded and ready-to-fly. John