John Dowson

0x1264 holds the FUEL TOTAL CAPACITY. From the MSFS documentation: Maybe the aircraft is using the new Modular fuel system and the value does not include any unuseable fuel? If you want the total fuel capacity including unuseable fuel, you can use the simvar FUEL TOTAL QUANTITY EX1: This is not currently added to any FSUIPC7 offset - you can add it yourself to a free/spare offset if you want to use this.

The trial key has now been updated, valid until 1st November 2025. John

Strange this occurred with the first file and not the second...but it will be a false positive. This is continually happening with Windows Defender but is usually fixed pretty quickly by a subsequent virus definition update. This occurs with the compressed version - I have attached an uncompressed version below for you to try. Did you change your assignments, as indicated? If you are using the same assignments, the same thing will happen, as I explained. Please try again, and if you get the same issue pleaseattach your ini and log files again. But please attach the full log file, not an extract. If you cannot edit an assignment, this is because you either have multiple assignments to the same button, or you have edit the assignment to add a compound or condition on the assignment. If this occurs again, show me a screenshot together with your FSUIPC7.ini file. John FSUIPC7.exe

Well, its added now - but I may make this dependent on an ini parameter, as I said. John

In the attached, I have also enabled the Set Throttle1/2/3/4 Reverse Thrust On/Off controls to also allow the reversers to be used. In this version, you can also set your reverser button to Set Throttle1 Reverse Thrust On for the press and Set Throttle1 Reverse Thrust Off for the release, and also for reverser 2 using the matching Throttle2 controls. John FSUIPC7.exe

I have implemented separate reverser for throttle1 and throttle 2 in the attached version. With this version, assign your reverser buttons to TOGGLE THROTTLE1 REVERSE THRUST and TOGGLE THROTTLE2 REVERSE THRUST, both on press and release, and with no repeats. When you activate your reverse lever for a particular engine, it will then toggle reverse thrust mode for that engine only, and the throttle for that engine will increase the reverse thrust. When you move the reverser back, this will toggle reverse thrust for that engine again, disabling the reverse thrust. Let me know how it goes. John FSUIPC7.exe

Interesting this - seems to be a windows thing and depends on the keyboard layout. Some keyboards use the right Alt as Alt Grande, and as there is no windows key code for this, windows sends a left Control followed by aright Alt. So this is wht you are seeing. However, the assignment should still work, as when you press this again, it will send the same and trigger the assignment. I can also correct for this, to remove/ignore this additional left control that is sent. I have done this in the attached if you would like to try it. However, I am worried that if I release this as is, it will break any current assignments to the right alt/Alt Grande key. So I may add a new ini parameter to control this behavior (IgnoreAltGrande), with the default being how it works now, but when this parameter is set, the additional left control will be ignored. What do you think? You can try the attached version, where this additional left control is ignored. John FSUIPC7.exe

This is because you have assigned the reverser button to send Throttle Decr on repeat, so it keeps decrementing the throttle until you go to max reverse. Change this to not repeat, and it will go to idle reverse. But you will then need to assign something else to throttle decr to increase the reverse speed. You can't do this with the Throttle Decr, as any further movement on the assigned throttle axis will still apply forward thrust. You need to use the Throttle Reverse Thrust Toggle control to toggle this behavior. However, this is currently only implemented for all throttles, not individual throttle controls. I will look into allow this for individual throttle/reverser controls, but this may take a while. For now, you can just assign one reverser to Throttle Reverse Thrust Toggle both on press and on release (and with no repeats). If you do this, when you use that reverser lever, it will set the reverse thrust mode for both engines, and the throttle control for each engine will increase the reverse on that engine, and when you move the reverse lever back, it will toggle back to normal thrust mode. I will look into allowing the same behavior for the individual throttle1/2/3/4 reverse thrust controls. John

The current trial license is still valid up to and including the 1st October. I will update in a few days - on the 2nd or 3rd October. John

No, it has always been there. In the latest beta, I have move the List Lvars menu item from Add-ons->WASM menu to the Log menu. You should use that to list the lvars and not reload first. Reloading/rescanning for lvars can cause the WASM to crash - it may be that the WASM has crashed. Butthere is something strange happening as when this happens the number of lvars is reported as 0, but you can still list them. However, when I do this a few times here, the WASM will crash anyway. No. I will look into this again at some point but not for a while. Just use the Log->List Lvars menu item - you shouldn't need to reload. John

Yes, that is strange. I will look into it. John

I have added another function ipc.getInstallationFolder() that returns the installation folder (with trailing '\' included). John FSUIPC7.exe

I have added an ipc.getLuaPath() function in the attached version. John FSUIPC7.exe

...or is it because the io.execute statement is not running under the LuaPath folder, so its creating the directory in the wrong place? I can see that you may need the LuaPath there...is there not an lua io function that can create a folder?

It will be portable if you use relatibe paths - thats the whole point. Why not? If relative paths are used, it doesn't matter what the root of the relative path actually is. I guess could add a lua function to return the LuaPath setting, but this shouldn't be needed. John

The hardware doesn't matter - it is just a collection of buttons and axes as far as FSUIPC is concerned. You would normally just assign the reverse lever button to a Throttle Dec control, so that when the throttle is in idle and you pull the reverse lever, the decrement should switch it to idle reverse. However, this could depend on the aircraft = which aircraft are you using? No point attaching it until you have the assignments. Try assigning again and if you still have issues, show me your ini and log files, the latter with logging for Events, Buttons & Keys and Axes Controls activated.

You cannot access the LuaPath setting. But why do you need this? Can you not just use relative paths, as you seem to be doing?

You need to press the Confirm button - are you doing this? Works fine here...

UTF-8 (NOT UTF-8 BOM) or Windows-1252. What are LVAR modules? The encoding is only relevant for the EXE.xml files for the FSUIPC7 installer. John

You reverse in the calibration panels, not in the assignments tab. You can also do this by scaling the axis by *-1 (e.g. add ',*-1' to the axis entry in your FSUIPC7.ini, before the comment). Then also calibrate with No Reverse Zone.

Your log file shows an issue installing the auto-start component for MSFS2020: This is because your current EXE.xml file either has the wrong encoding, or is an invalid xml file. Try changing the encoding (you can sue Notepad++ to do this) or check the format. For further details, see As for the WASM not being installed, the community path looks incorrect: I do not know why that 'xtBoot' string is for...do you know what this is? Could you show me / attach your Usercfg.opt file for MSFS2024 - this: C:\Users\Dale\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\UserCfg.opt Is your Community folder specified correctly there? It is the InstalledPackagesPath at the end of the file. Did you just install the 'fsuipc-lvar-module' folder? That should work, but why don't you just copy the one from your MSFS2020 folder to the MSFS2024 folder? If the FSUIPC WASM folder is installed in your MSFS2024 Community folder, but isn't working, can you show me your FSUIPC7.log file and also your FSUIPC_WASM.log file (if present - see the WASM documentation in the Advanced User guide if you don't know where this is located). It could be the WASM is installed and working (you can check this in MSFS2024, using the Developer menu), but FSUIPC7 cannot detect it, again probably due to this strange 'xtBoot' string that seems to be coming from your InstalledPackagesPath. John

It has been found that the update of the EXE.xml (to add the FSUIPC7 auto-start entry) can fail when the EXE.xml file has the wrong encoding. The EXE.xml file must have either standard UTF-8 encoding or Windows-1252 encoding. Sometimes this file can be encoded in UTF-8 BOM (or maybe other character set encodings) which will cause the update to fail. If this is the case, change the file encoding and try again. Note that you can use Notepad++ to view and change the encoding used in a file. I have updated the initial post in this topic with this information. John

How have you configured the reversers? Please show me / attach your FSUIPC7.ini file so that I can see your assignments. Do the reverse levers use an axis or do they trigger buttons?

The separate throttle control axes are calibrated to give full reverse (when a reverse zone is enabled) at -4096 - from the user guide (section DETAILS OF MSFS’s AXIS CONTROLS on page 48): This should give you movement of the throttle through its full range in the VC as the lower range is taken to match the aircraft. If this was calibrated to -16384, the throttle in the VC would hit the bottom when your throttle axis hit -4096, and the rest of your throttle lever below this would produce no throttle change in the VC. John

sound.adjust takes a reference (returned from sound.play or playloop), not a device number. If its just a sound issue, create a simple lua to test the sound, i.e sound.path("C:\FSUIPC7\Callouts") ipc.log("Playing sounds on device 4: " .. sound.device(4)) ref=sound.play("2000",4) sound.adjust(ref, 100) ref=sound.play("1000",4) sound.adjust(ref, 100) ref=sound.play("500",4) sound.adjust(ref, 100) ref=sound.play("400",4) sound.adjust(ref, 100) ref=sound.play("300",4) sound.adjust(ref, 100) ref=sound.play("200",4) sound.adjust(ref, 100) ref=sound.play("100",4) sound.adjust(ref, 100) ref=sound.play("50",4) sound.adjust(ref, 100) ref=sound.play("40",4) sound.adjust(ref, 100) ref=sound.play("30",4) sound.adjust(ref, 100) ref=sound.play("20",4) sound.adjust(ref, 100) ref=sound.play("10",4) Then assign that to a button. Also test on other sound devices (you could make the device number a parameter, or wrap it in a loop to iterate over devices 0-6. Do you hear anything on any device? Also try setting a Log->Custom value of x20. This should add additional logging on sounds.