John Dowson

Either way is fine, its up to your personal preference. Some people like to use separate scripts, others prefer fewer but larger scripts. You can also use the same handling function for throttle1 and throttle2 (as well as one for mixture1 and mixture2) and use a conditional statement in the handling function based on the offset value to handle things separately (or set things up separately) for each throttle. But again, thats just personal preference - no problem having separate functions. Cheers, John

If you want to add lvars to offsets, you can do this using lua. Otherwise you can access them via macros. See the Advanced User guide on how to use macros to control lvars. You can do this easily using macros - no need to add them to offsets. See page 39 of the Advanced User manual. John

In your FSUIPC7 installation folder. That is a partial log, pasted from the console window, and shows that FSYUPC recognised 4 devices: Logitech Extreme 3D T-Rudder Bravo Throttle Quadrant TCA YOKE BOEING Which device are you using for the fuel cut-off lever? This does sound like the lever isn't working. Can you see it in the windows game controller config?

I would like to close this issue asap as I need to release the next version of FSUIPC shortly, probably next week. I can release with this included or not...I will probably release with this included, and can address any issues afterwards. Note I will be away for the next few days, back on Monday. John

Sorry for the delay - this is the previous version, v7.3.20: FSUIPC7.exe If you get the same issue with that version, then the issue will be that your registry has this axis defined as a digital axis, and you need to follow the instructions in that post I referenced in my previous column. If it works with this version, I will investigate in more detail. Thanks, John

I have moved your post to the MSFS / FSUIPC7 sub-forum. Please enable logging for Buttons & Keys and Events, then generate a short log file showing your issue. Exit FSUIPC7, and then attach your FSUIPC7.log and DSUIPC7.ini files and I will take a look., John

By dragging them and dropping them to the bottom of the field where you enter comments, where it says 'Drag files here to attach...' or use the choose files link in the same place..... But if you are moving the lever and it is not recognised, then I doubt there is much I can do. Is it recognised by MSFS?

Sure - this is what it says in the download page for MakeRunwys in the Download Links -> Useful Additional Programs section of this forum (still need to add this to fsuipc.com): John

Check the aircraft name/title as logged in your FSUIPC6.log file. A profile will be selected based upon the first substring match (assuming you have ShortAircraftNameOk=Substring set in your FSUIPC6.ini) to this name. If you think there is a problem, please attach both of those files and I will take a look. John

Well, there shouldn't be a next time...The trial license is provided for you to test the licensed facilities. You are expected to purchase a license if you want to continue using these facilities, not keep updating to the latest trial license. It looks like you have been using the trial license since October 2021... If people are abusing this in this manner, I will stop providing a trial license in this manner and only provide one to new users on request.

That is strange - this is usually caused by the axis being registered/changed to be a digital on/off axis in your windows registry. There is a FAQ entry on how to dix this issue - see However, before doing this I will give you the previous version to test - you should get the same issue with that version if this is the issue. Will be tomorrow now though... Should be =No not =Off (but I think this is what you meant, looking at your ini), but this should not make a difference as the _EX1 controls should not be affected... John

Presuming there is enough disk space, I can't think of anything that would cause this except the security/permissions on this folder. Check those. There is no change in the installer, only the exe and a few other files/documents have been updated. Ok

Does it work if you select auto-start? You should also select that, otherwise you will have to manually start FSUIPC7 when needed.

The installer cannot write to your windows Documents folder: C:\Users\Yoshua\Documents\FSUIPC7 Is that the correct location? If so, I can only think that it is a permissions/UAC issue....

Ok - I expect that you would get the same with P3D... That's interesting.... I saw Thomas recommended this in a similar issue in another (old) thread...not sure why this would work at the moment, and I don't think it solved the OP's issue in the other thread... Ok, let me know how it goes. Thanks for the update. Regards, John

What happens when you click OK on the error message? Is an InstallFSUIPC7.log file produced, and if so please attach it. Are you using OneDrive or another cloud back-up service on your Windows Documents folder? If this works, show me the InstallFSUIPC7.log file from the install.

Check your antivirus to see if this is blocking the installation. Otherwise I have no idea what could be causing this. There is nothing wrong with the installer.... The FS12 documentation is installed by the Extras -> FS-Interrogate 2. Maybe try just selecting FSUIPC7 and the WASM module.... John

I have moved your post to the main support forum, as MakeRwys questions belong there. Be aware that MakeRwys is no longer supported, as Pete has retired, but he may respond. Otherwise, the source code for MakeRwys is available for anyone that would like to update this for MSFS issues. I cannot support MakeRwys, sorry. John

Did you uncompress/extract the installer from the zip file before running it? If not, try that. I am pretty sure there is no problem with the installer - this would have been reported many times already if there was. Maybe the download is corrupt - try downloading it again. You can also try deselecting the documentation installation.

Ok, that makes sense, and is basically what the preset does. I don't understand why you cannot control multiple throttles in the same calculator code string though. Then this should be raised with Asobo. However, the documentation does say only for engines 1-4, so you are lucky that the throttle works for indices 5 & 6. Probably worth asking in the Asobo SDK forums though - or I can do this if you like. If they don't change via calc code, then I suspect not. You could try adding them to an FSUIPC offset, but I suspect this would only work for the throttle simvar with indices 5 & 6, and you will get an error (something like 'index out of bounds') with the prop and mixture ones. John

MSFS only provides events/controls for 4 engines, and FSUIPC only has in-built support for up to 4 engines, and the offsets only hold the simvars (A-type variables) for 4 engines. How are you doing this - using offsets? The GENERAL ENG THROTTLE LEVER POSITION simvar is currently held in offset 0x38A8 - engine/index 4 0x3968 - engine/index 3 0x3A28 - engine/index 2 0x3AE8 - engine/index 1 with mixture and prop lever positions held in adjacent offsets (see the offset status document). You can add this simvar with indices 5 & 6 (for engines 5 and 6) to offsets designated as 'free for general use' using the facilities provided - see the section Adding Simulator variables (simvars) to FSUIPC offsets in the Advanced User guide for details. However, the SDK documentation does say (see https://docs.flightsimulator.com/html/Programming_Tools/SimVars/Aircraft_SimVars/Aircraft_Engine_Variables.htm#note😞 so maybe this isn't possible... You can try this, and you will see an error in the log if the simvar with indices 5 and 6 are not available, although I suspect that this is a documentation error. Alternatively, you could define your own preset to update these simvars, and then assign your axis to the preset. For example, to define your own preset to control all 6 engines on one axis, add the following line to your myevents.txt file (create this file in your FSUIPC7 installation folder if it doesn't exist): Six Engine Throttle#$Param 16383 + 32767.0 / (>A:GENERAL ENG THROTTLE LEVER POSITION:1, percent over 100) $Param 16383 + 32767.0 / (>A:GENERAL ENG THROTTLE LEVER POSITION:2, percent over 100) $Param 16383 + 32767.0 / (>A:GENERAL ENG THROTTLE LEVER POSITION:3, percent over 100) $Param 16383 + 32767.0 / (>A:GENERAL ENG THROTTLE LEVER POSITION:4, percent over 100) $Param 16383 + 32767.0 / (>A:GENERAL ENG THROTTLE LEVER POSITION:5, percent over 100) $Param 16383 + 32767.0 / (>A:GENERAL ENG THROTTLE LEVER POSITION:6, percent over 100) (assuming axis value goes from -16383 to +16282) Then, in the axis assignment panel, move your axis lever and check Select for Preset and Send to FS as normal axis, and then select the preset Six Engine Throttle from the drop-down. However, I have just tried this and it doesn't seem to work...it functions correctly if you reduce the code to control one throttle, but not when trying to control two or more... not sure why this is at the moment. I will look into this further and get back to you. John

Hi Bob, So this is the same laptop that you use for WideClient with MSFS as you do for WideClient with P3D? If so, this is very strange as WideClient is the same (obviously), and the WideServer element in FSUIPC5/6 is the same as that in FSUIPC7. I will look into your crash logs and WideClient log, but for now could you change to Log=Yes in the [User] section of your WideClient.ini and show me the log file generated with this after a CTD, as well as the corresponding windows event. The log file will be large and need compressing/zipping before attaching. This should hopefully show the last things being written before the crash. Try a few times to see if this is consistent before posting the log. if this doesn't reveal anything, we you can also try with Log=All, and Log=DebugAll Thanks, John

uSER GUIDE, PAGE 22 (bottom of page 21...) section Explained in the User guide, but just set AutoAssignLetters=Yes in the [JoyNames] section of your FSUIPC6.ini file. John

Of course not - that makes no sense. You can assign a key press or button to an axis control, but you need to provide the axis value which would be fixed. If you wanted to assign a key or button to increment or decrement an axis value by a defined amount, you would normally use an offset that holds the axis value and use the offset inc/dec controls to do this.

What device is this lever/button/switch attached to? Are any buttons/switches/axes on this device recognised? As I have already said (when you asked this question in another post), please attach your FSUIPC7.log and FSUIPC7.ini files. Why? If installing the Efis Control panel software caused this issue, why not try uninstalling that first to see if that solves the issue....