John Dowson

Can you also activate logging for Events and Axis controls, and produce a short log where you load your aircraft and then move throttle 1 to full power anf then throttle 2. Then exit FSUIPC7 and show me your FSUIPC7.log file - you can zip/compress it if too large to attach. John

When using two throttle axis to control four engines, it is more standard to assign one axis to Throttle1 and the second to Throttle2, and then calibrate for Throttle1 and Throttle2 and map the Throttle3/Throttle4 calibration using the map checkboxes (and not calibrate throttle3 or throttle4). Having said that, you should be able to use one axis for throttles 1 and 3, and the other for 2 and 4, so I am not sure why this is not working. Are you using the Asobo 747? If do, I can check this... John

Why don't you just check the offset status document for FSUIPC7 / MSFS rather than quoting the documentation for other versions? This offset is clearly marked in red, i.e. not available or working. The old SimConnect weather interface has been deprecated in MSFS and is no longer available. You could try offset 0x2DF0, which holds the simvar AMBIENT VISIBILITY, documented as Visibility at the aircraft, in metres, as a 64-bit double floating point – for reading. (and in MSFS documentation: Ambient visibility (only measures ambient particle visibility - related to ambient density). John

You are using FSX version 10.0.62607.0, but you only have the following SimConnect SDKs installed: Found SimConnect build 10.0.60905.0 Found SimConnect build 10.0.61242.0 Found SimConnect build 10.0.61259.0 Could you check and see what is in the folder C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X Steam Edition\SDK One of those folders should be named after the FSX or SDK version number (mine is called SP1a) and inside that folder there should be an installer for the SDK - the one I have is called fsx_sdk_sp1a.exe. Could you find a similar file on your system (let me know the folder and file name please) and try running that. That should install the SDK valid for your FSX version. Once that is done, re-run the FSUIPC4 installer and try again. Any issues, send me your latest FSUIPC4 Install.log again as well as FSUIPC4.log file, if available. You can also try using the FSUIPC4_Loader.dll. I don't know much about this (before my time!). but the Installing and Registering FSUIPC4.pdf states: John

Are you using the LorbySceneryExport program? Scenery installs abiding by the new L-M system for addons will NOT be seen by MakeRunways unless you use this program. Please see the provided MakeRwys README.pdf section on how to use this utility for P3Dv3,4 and 5. Also please check that you are using the latest version of MakeRwys, v5.13. If that doesn't resolve your issue you can post again and @Pete Dowson may take a look. John

Your assignments are always saved to the ini file. If this is not happening, then it could be due to windows (or anti-virus) protection on the FSUIPC7 installation folder. Check that you have not installed into a windows-protected folder such as Documents or Program Files. Note that if you are editing the ini file manually, you should do this either with FSUIPC not running, or for editing button and assignments sections, you can have FSUIPC running but with the assignment panel already open, then make your changes and click the Reload all buttons or Reload all assignments button. If you manually change the ini and then open an assignments panel, your changes will be overwriiten. John

The first axis value change on any known axis will populate the axis assignment dialog with those details. You press the Rescan button to scan for a different axis. Sometimes a sensitive/jittering axis can make other axes difficult to be recognised - if this happens, you can click the Ignore Axis button which will then ignore any values from that axis for the rest of the assignment session, i.e. until you close the Axes Assignment panel. John

The license is available in the first post in this topic - currently valid until 30th August. John

👍 Note that you should always calibrate any axis assigned with 'Send direct to FSUIPC Calibration'. For axis controls that don't go via FSUIPC calibration, you can use the scaling facility instead, documented in the Advanced user guide (P41). John

Presumably you have tried the standard offset for this at 0x31F0? There is a simvar called PUSHBACK ATTACHED, but this is not available by default in any offset - you can add this to a free user offset and check to see if the PMDG 737 is using/updating that simvar. The specific PMDG offsets are not available in the current release (v7.3.7), but will be available in the next release (v7.3.8) and there is a beta version out of this release that you can try, available here: However, I don't see any offsets relating to pushback state in those offsets either. You can also try listing the available lvars to see if any look applicable, and if so then they can also be added to a free FSUIPC offset. Pushback and ground service handling in MSFS in general is quite different from other sims and I am not sure what is available without checking...I will rake a deeper look later in the week to see if I can see anything. John

Not if everything is working - its just an informative message that indicates the devcom threads could not be closed on the first attempt. You can safely ignore these. No - I don't have any experience with the saitek BIP, sorry. John

Have you tried the events/controls Parking Brake Set and Recognition Lights Set, with a parameter of 1 for on an 0 for off?

Could you please let me know your FSUIPC7 order number from simmarket and I will check your details here. There is an issue in the installer not correctly validating unicode key details, although these are validated ok by FSUIPC7 itself if you manually create the key file. I will look into this. There are already many posts where this information is available, although they may be difficult to find. I will add a FAQ entry on this (as well as looking to see if I can fix this issue in the installer). You could also have created a User Contribution for this if you think useful for other users. John

Just check to see if there is an update, and if so update and then re-install FSUIPC4. Whether you update or not, I need to see your FSUIPC4 Install.log file.

Thanks for the contribution. Note that in the next release (v7.3.8) and onwards, presets will be available in a separate drop-down menu available on a new checkbox, and the name will be displayed without the 'Preset:' prefix. There is currently a beta version of this release available from the Announcements sub-forum.

If you accept/trust the module and continue, doesn't it run correctly? If FSX continually mistrusts the FSUIPC4.dll, please see this FAQ entry: What version if FSX are you running? Your log file shows: fsx.exe version = 10.0.62607.0 Not sure what this version is - have you installed SP1 and SP2? This should be updated automatically if using Steam - my steam FSX shows the following version: fsx.exe version = 10.0.62615.0 Can you check your FSX is up to date. Also note that the current/latest release will not work with the latest FSX beta - there is a specific version available for this, but it is recommended not to use this beta as it was only released to collect more info for the development if FSX. Can you also show me your FSUIC4 Install.log please. John

The *_EXT (and *_EXT1) controls cannot be calibrated, but they can be scaled (and reversed). See the section Additional parameters to scale input axis values on page 41 of the Advanced User guide. However you cannot set custom start/end values, only scale, but you should be able to scale to get something useable if not perfect... John

The *_EXT (and *_EXT1) controls cannot be calibrated, but they can be scaled (and reversed). See the section Additional parameters to scale input axis values on page 41 of the Advanced User guide.

Not quite - the previous log file is renamed to FSIOPC7_prev.log, so you always have the log file of the current and previous run if FSUIPC7. There are two know issues that can cause this. One is for Windows 11, when FSUIPC7 thinks that MSFS is no longer available and so exits, although it is still running. There is a new ini parameter for this issue, and this is now set automatically when FSUIPC detects you are running Windows 11. The second is related to a long standing issue with SimConnect. and can occur when simconnect runs out of client connections. This issue us quite rare and difficult to diagnose correctly (you need SimConnect logging), but if you think this could be an issue then just increase the maximum number of available client connections in your SimConnect.xml file. But you really need to show me your FSUIPC7.log file before anything else. And if MSFS is crashing, that should be reported to MSFS - FSUIPC7 is not the cause of this and I cannot investigate MSFS crashes. Check the windows Event log if you get a CTD.

What do you mean by this? If you open the axes or button assignments panels and move an axis or press a button, do you not see that recognised? Your ini file shows 5 devices were recognised and should be available for assignment: If you cannot see these devices in the assignments panels, please show me your FSUIPC7.log file. John

No - I just checked this an it is certainly v7.3.7. I don't understand how you can see 7.2.1... John

I am confused now - you did have the WASM enabled! The Add-ons->WASM menu items (such as Execute Calculator Code or Set Lvar) are not available unless the WAPI is enabled. Not without seeing your files again, with appropriate logging activated. Set FSUIPC7 logging for Buttons & Keys as well as Events, load your aircraft and press the assigned key. Note that the left/tight alt key modifiers are specific - i.e. your assignment is using the left alt key, not the right one. What events or presets are you using for this? If there are no specific on/off events (or presets) provided (I am pretty sure there are for Parking Brakes!), you can use the toggle event but with an offset condition in an offset that is holding the current state of the function you are trying to toggle. I am finishing now for the weekend. Provide more information (and possibly your FSUIPC7.log and .ini files again), and i can look into this further on Monday. Have a good weekend, John

No, I don't, sorry. Logging will show you the pause state changes, but not what is sending these. If its coming from FSUIPC, additional logging (and/or checking the FSUIPC7.ini file and maybe luas or macros - for registered versions). If its coming from an FSUIPC 3rd-party client, IPC Write logging should show this (although that can be difficult to interpret).

You can activate logging for Events in FSUIPC7, then take a look at the FSUIPC7.log. You can also log offset 0x0264 (as U16 in hex) which will log the 3 distinct pause states as: 0x1 -pause set 0x2 - pause on/off 0x4 - esc pause Note that MSFS can also be in multiple pause states at the same time. Btw, you posted in the main DSUIPC support forum. I will move your post to the FSUIPC7/MSFS sub-forum. John

That is not an error - it is an informational message [INFO]. Yes, this is normal. The default FSUIPC_WASM.ini is always located under your Community\fsuipc-lvar-module folder. This is the one installed by the FSUIPC7 installer when you install the WASM module. If you change that file, your changes will be overwritten the next time you re-install or update FSUIPC7. To prevent your changes from being lost, the WASM will also read an ini file from your WASM persistent storage area - this does not exist by default, you need to create (or better, copy) this file yourself. Please see the section WASM module ini file and parameters in the Advanced User guide (page 48). Can you try with another aircraft, so we can see if this is a general issue if specific to the C172. Maybe also set the logging lever in the WASM (and maybe also the WAPI, later) to Trace and resend the log file. It looks like the FSUIPC WASM module has crashed for some reason (or at least, its not available) as it doesn't seem to respond to any requests. I am busy this weekend - I will come back to this on Monday. John