Self-Loading Cargo/A Pilot's Life v2 no longer recognizing FSUIPC as running

[hinapilot]

Hey there,

 

I have a bit of a weird one. It seems that both SLC and APLv2 are not recognizing that FSUIPC 7.5.3 is running on my computer alongside MSFS2024 (which it is) and I'm wondering if you'd have any idea if FSUIPC might be responsible there or if that's just these software that are borked.

 

I have reinstalled FSUIPC to the latest version after uninstalling it, I'll attach the log too.

Ben

FSUIPC7.log InstallFSUIPC7.log

[John Dowson]

Your log file shows that FSUIPC7 was started manually and was started way before MSFS was ready to accept connections from client programs. You do have the auto-start component installed, so why not just let MSFS start FSUIPC7 when ready? If you want to start FSUIPC7 manually, then better to do this when MSFS is already running and has arrived at the main menu. If you want to start it earlier, you should adjust the DetectToConnectDelay ini parameter (only used when FSUIPC7 is manually started), which has a default value of 1. See the Advanced user guide on tuning FSUIPC start-up parameters.

If 3rd party programs don't recognise FSUIPC as running, then this is either because they are being ran at the wrong privilege level (all 3rd party programs must be ran at the same privilege level as FSUIPC) or is an issue with the program, in which case contact the program developer.
However, it could be that it is connecting to FSUIPC but not recognising the FS version being used. To check this, you need to set logging for IPC Reads (Log->IPC Reads) and send me /attach another log file.

Many 3rd party programs use offset 0x3308 to determine the FS being used. This used to contain 13 for FSUIPC7 with MSFS2020 and was always available. However, with the release of MSFS2024, this is now only populated once connected to the FS and contains 14 for MSFS2024. Some 3rd party programs read this offset before FSUPC7 is connected to the FS and so receive a value of 0, and do not recognise the FS and so fail to connect. To prevent this, you can try adding the following to the [General] section of your FSUIPC7.ini file:
    Init3308=14

Otherwise, if a 3rd-party program is using offset 0x3124 to determine the FS version, this used to contain 120 for MSFS2024, but since the release of SU1 this now contains 121. If this is an issue, it needs to be corrected by the program developer.

John

[hinapilot]

Sweet thank you so much John I'll try running everything at admin level and report back with the log!

[hinapilot]

Hey John,

 

It was an admin level issue as you said. Running everything as admin does fix the issue thank you very much.

 

Ben

[John Dowson]

8 minutes ago, hinapilot said:

It was an admin level issue as you said. Running everything as admin does fix the issue thank you very much.

Ok, thanks for the update. But note that you do not have to run everything at admin level, but at the same level. Better to run everything with standard privileges unless something must be run with admin privileges, in which case everything must then be run with admin privileges.

John