John Dowson

You should be able to do this without lua, by assigning the buttons to increment/decrement the spoiler handle position offset 0x0BD0. You would need the licensed version of FSUIPC though, not the free version. If you would like to try this I could provide you with a trial license. John

Yes, it is the BOM format that causes issues, in fact, any BOM format. Standard UTF-8 is fine. I don't really have a strong preference here. If FSUIPC creates the EXE.xml, it will use windows-1252, mainly for historical reasons. But it will not change the format if the file already exists. I actually use a scripting language called NSIS (Nullsoft Scriptable Install System), and an XML plugin for NSIS that handles XML documents. Unfortunately it is this plugin which has issues with xml documents encoded with a BOM. Also note that the BOM header is not required or recommended in the unicode standard. Not sure why writing a UTF-8 file in a standard way would also write a BOM, which seems to be the issue with quite a few installers. Anyway, thanks for updating your installer for this. l will see if I can do anything about this in the FSUIPC7 installer, when I get a chance. Regards, John

Thanks for correcting this. FSUIPC does have an issue installing or uninstalling if the EXE.xml is a badly formed xml document or is in an encoding format that it cannot read (mainly the non-standard *-BOM formats, and UTF-8). The installer handles this by logging a message and continuing, and means that the FSUIPC entry in the EXE.xml won't be added. However, it seems that the uninstaller just hangs if it can't open/parse the EXE.xml, and the only solution is to stop/kill it. I will see if I can update the uninstaller to just log a message and continue. There seem to be several 3rd-party installers that write or change the encoding of the exe.xml file to a BOM or UTF-8 format. Unfortunately its not easy for me to update the installer/uninstaller to handle such formats, but the uninstaller should at least fail gracefully and not hang. Cheers, John / FSUIPC

Also reported in the FSUIPC support forums here: https://fsuipc.com/community/fsuipc6-support/make-runways-error-p3dv5-4/ I have responded there, but unfortunately MakeRunways is no longer supported . Hopefully some other MakeRunways users may be able to help. John

ADE has not been updated to be compatible with P3Dv6, and ScruffyDuck has retired and nobody else has taken over the development of this utility as far as I am aware, so I don't think this is possible. I get the occasional question on this in the FSUIPC forums, e.g. https://forum.simflight.com/topic/99773-fsuipc6-will-not-connect/ I would be happy to be proved wrong! Regards, John

No. FSUIPC uses both the numeric and letter entries - both are needed, and if you relabel you will lose any assignments to those letters. You do have some assignments on your Bravo using letter D, which need to be changed to letter F. And you can delete the duplicate letter entries once this is done, but not relabel/change the letters if you have assignments on them, as you will then lose the assignments. For further assistance, if needed, please post on the FSUIPC support forum, and attach both your ini and log files. John

As indicated, you should use the FSUIPC forums for all issues / questions regarding FSUIPC: https://forum.simflight.com/forum/183-fsuipc7-msfs/ By default, the FSUIPC installer adds an entry to the EXE.xml file to get MSFS to auto-start FSUIPC. The icons installed by the FSUIPC installer only display a splash screen and then start MSFS, and installing FSUIPC does/should not remove any icon installed by MSFS (unless it possibly has the same name as the one FSUIPC creates). If there are issues with MSFS not auto-starting FSUIPC, this usually due to an incorrect EXE.xml (some other add-ons can corrupt this file), or another add-on started before the FSUIPC entry blocking/stopping from FSUIPC being started. If that is the case, you can try re-ordering the entries in your EXE.xml and place the FSUIPC one first. Note also, if you are using a licensed version of FSUIPC, you can use FSUIPC to start other add-ons via the functionality provided (see the documentation). For further information on auto-start issues, see the following FAQ entry: https://forum.simflight.com/topic/95918-msfs-fsuipc7-auto-start-with-msfs20202024/ John

Is your issue resolved? As I said, you need to post in the FSUIPC support forums for help. I do not provide support via avsim, and only monitor these forums occasionally for issues relating to FSUIPC. John

Re-installing FSUIPC will cause no issues - but it won't solve your problem either. As @sloppysmusic says, it could be that your device ids/guids have changed, or if you have controllers active in P3D then P3D could have automatically re-assigned your controllers. If you want further assistance, could you post in the FSUIPC support forums, attach your FSUIPC ini and log files and I will take a look. John / FSUIPC

Only the WASM component of FSUIPC should be installed into the Community folder (and this cannot be changed), The application itself (the FSUIPC7.exe) should be installed in a non-windows protected folder (e.g. not under the windows Program Files or Documents folders) which you select during the installation process (defaults to C:\FSUIPC7). There should be no issues using the MSFS Add-on linker with FSUIPC (WASM module), but you should probably always have the WASM running when FSUIPC is running (for access to lvars/hvrs/bvars/presets/calculator code) although this is not required(and won't be needed if you do not use the facilities it provides. John

Why not just try FSUIPC? Thee is a trial license available for FSUIPC7 (for MSFS2020 and MSFS2024) in this post , although the current one has lapsed (it will be replaced in a day or two): https://forum.simflight.com/topic/92702-fsuipc7-trial-license-available-here/ John

I agree 100% with this - you can't use multiple monitors for views very easily with MSFS, without treating them as a single (stretched) screen, with all the issues that brings with it. Also note that MSFS2024 will be released next month - maybe that will have better multi-monitor support, but I doubt it. Better to look into solving your display issue. If you want to upgrade, I would consider P3Dv5, or possibly P3Dv6, but check your add-on support for the latter. If using FSUIPC5, you will need to update to FSUIPC6 for P3Dv5 and/or P3Dv6 (and FSUIPC6 also supports P3Dv4). John

For those using PF3 (and possibly other ATC add-ons that use FSUIPC), an issue has recently been identified where AI aircraft in the Init or Sleeping status get promoted to Enroute (by FSUIPC) due to the a/c ground altitude being reported incorrectly as 0. This can cause some ATC add-ons to think there are AI aircraft in the air when they are actually still on the ground. This issue is detailed in this thread (on the FSUIPC support forums): https://forum.simflight.com/topic/98929-ai-traffic-query/ There is a patched version of FSUIPC6 available in the same thread, here: https://forum.simflight.com/topic/98929-ai-traffic-query/?do=findComment&comment=595003. For FSUIPC7, please use the latest beta release (also with traffic zapper enabled, as well as the traffic limiter) available here: https://forum.simflight.com/topic/98884-fsuipc7-version-7418beta-now-available-traffic-zapper-and-traffic-limiter-functionality-added-back/. Any issues, please use the FSUIPC support forums. John

This is an issue with the aircraft, not FSUIPC. However, I have implemented a fix for this that will be available in the next release. A beta version with this fix is currently available in the following post: https://forum.simflight.com/topic/97959-fsuipc7-thrust-reverser-breaks-built-in-msfs-sim-limitation/?do=findComment&comment=589697 John

If you are running the sim as an administrator/with admin rights, all SimConnect clients must also be ran with admin rights otherwise they wiil not connect. Right-click the exe files, select Properties and then Compatibility and check Run this program as an administrator for your add-ons (chaseplane, vPilot). But really you shouldn't run with admin privileges unless absolutely necessary... John