John Dowson

Currently not. It is listed in the offset spreadsheet document (for FSUIPC7 / MSFS), but it has not yet been allocated to an offset. I can add this for you (if using FSUIPC6 or FSUIPC7 - other versions are closed for development). Which version are you using? John

When you minimise, it goes to the task bar not the system tray. To get the window back from the task bar, you have to click the FSUIPC task bar icon. If in full screen mode, you would have to exit this first using alt+enter. As Pete says, best to close to the system tray instead (either by clicking the X close button or the File -> Close menu option), especially if using MSFS in full screen mode (i.e. no task bar). I will look into also un-minimising from the task bar with the open/show hotkey.

FSUIPC just logs all events seen by SimConnect. Many aircraft (more in MSFS2020) and especially add-on aircraft can continually log events. Also, some controllers (notably the new Honeycomb bravo and alpha) have always on buttons, which, if assigned in the FS (FSUIPC assignments don't have this problem) can also continually be activated and send such events. So, if the controls are something that is actually being sent by one of you assignments, then you need to look into which button/assignment is sending those and check that assignment. If it is just something that the a/c model is using internally, then you can ignore such events using the DontLogThese ini parameter. Check the Advanced User guide for details. It goes in the [General] section, and for some versions of FSUIPC it can also be used in the [Profile.xxx] sections, but I can't remember off-hand if I added that in FSUIPC5 (for sure in FSUIPC6 and FSUIPC7). John

Did you check available lvars? The following are available (in the FBW mod version): A32NX_ECAM_ALL_Push_IsDown A32NX_BTN_TOCONFIG A32NX_BTN_CLR Not sure about the stock A320Neo. The MobiFlight spreadsheet is a good source of information on lvars, hvars and calculator code to use - see https://docs.google.com/spreadsheets/d/1jTXlcHaJWx0B7TB63Pmma7bKwpxsxXJO6EJ3ECt7zpc/edit#gid=172455454

New one posted, valid until 5th August.

No, as FSUIPC4 was closed for future development quite a while back.

There was an issue processing the command when enclosed in quotes which resulted in the parameters not being passed. I'm surprised this issue hasn;t been picked-up before - it must have been there for years!

Btw, you have set-up all your assignments in a profile, and don't have any general assignments for axes or buttons. It is generally better to set-up a general profile first, for all your main axes and button assignments. Then you can create profiles with this as a starting point, and change/add whatever is needed for that profile. Doing it this way, you will at least have basic controls assigned for all aircraft. As it stands, if you load any other aircraft apart from the Cessna 152, you will have no assignments.

Your log shows multiple conflicting throttle axis controls being sent: Looking at your assignments, you have the throttle set on 2 of your TPM axes: Try deleting one of those, probably the second one - best to use direct settings and calibrate.

Ah, ok. Yes, that will be the issue. The installer (and FSUIPC) doesn't support unicode. Thanks, John

It will do that - its not an issue. Please try again, let it uninstall and then re-install. Thanks.

You should still install the SPs. They mainly contain bug fixes and improvements, and shouldn't bloat the system too much. You can always uninstall any bloatware and disable specific components/services that you don't use or need.

Btw, if thats not the issue, can you show me your FSUIPC7.log and FSUIPC7.ini files.

Here's the FSUIPC6 version, v6.1.3a: FSUIPC6.dll

Sorry - you are on FSUIPC6 not 7! I will update in FSUIPC6 and post shortly. John

Glad you sorted the problem. However, I don't know why the installer couldn't validate your key and generate the key file. If you run the installer again (in won't do any harm) the registration fields will be pre-populated from the key file that you created. Does it validate ok when you do this? If not, it doesn't matter as you have a key file, but if thats the case could you let me know your order number so I can check it here. Thanks.

Could you you the attached version please. Note that the program must always be wrapped in double quotes if it takes parameters. FSUIPC7.exe

Sounds like your throttle has somehow changed to a digital on/off device in the registry. See Before you try that, you could activate logging for axes controls to verify that the values been sent on your throttle axis are 0 or 16383 (i.e. on/off). John

👍

I have just noticed this: That is the old method of accessing lvars via FSUIPC offsets. You should try the newer method using the MSFSVariableServices class. See John

For c# questions using Paul Henty's dll, you should really post in Paul's sub-forum. I will move your post for you. This can also occur if trying to read an lvar after opening a connection and before the lvar values have been received from the FS. To prevent this, you need to register for the update callback using the function fsuipcw_registerUpdateCallback Lvars will be available to read once the registered callback function has been called. If using a registered version of FSUIPC7, you (i.e. your users) can also try listing the available lvars and values using the Add-ons->WASM-<List Lvars... menu option. This should give you a snapshot of available lvars and values. Also, if using a registered version of FSUIPC7, it is possible to use the lvars-to-offsets functionality to populate a user offset with the lvar value, and then spoof the park brake position offset (0x0BC8) to the value held in the lvar offset. See the following post for details: John

@DakotaPilot and @aua668 there is definitely something strange going on with the run programs command with arguments. I will look into this and get back to you. However, this may take a while - I'll post back here when I find out anything useful. John

The code still exists. If you set that ini parameter to a control/event number, when FSUIPC sees that control it will automatically change to use the FSUIPC steering tiller control instead, As Pete says, its pretty much redundant these days. John

No problem. Just remember that by default, all general sections are loaded. Then, if there is a profile, buttons and key sections are loaded and replace/augmented the general sections (i.e. general section assignments apply unless changed in the profile). Axes and calibration sections work differently - if there is an axes profile section, the general section is dropped and the profile axes section is loaded and used exclusively, and the same with the calibration sections. If no profile axes (or calibration) section is present, then the default/general section will be used. Just FYI. John

Yes