FS2020 and FS2024 installation

[beatic]

I have been a registered user of both FSUIPC7 and WideFS for several years, for which I have the corresponding Registration key

I have used these programs for several years and have never had any problems with them.

All these years, when I use the simulator, I start the auxiliary programs for the simulation.... LittleNavMap and Andalusí (flight reporting program of my VA) .... for which I add the following lines to the end of the fsuipc.ini file:

[Programs]

runif1=READY,CLOSE,"H:\08 - Andalusi\Andalusi.exe"

runif2=READY,CLOSE,"H:\Little Navmap\Little Navconnect\littlenavconnect.exe"

A week ago I installed the new MSFS2024 on my computer and downloaded and installed FSUIPC7 version v7.2 in C:\FSUIPC7 and although I still use the same instructions in fsuipc.ini to open Andalusi and LittleNavMap, but none of them run anymore when I click on any of the icons that the FSUIPC7 installation has created on my desktop … and they don’t do it either in the installation for the two simulators ( MSFS2020 and MSFS 2024 ) nor with the separate installation for each of them.

As a consequence I must first start MSFS2020 or MSFS2024 and when it is running I directly run FSUIPC7.exe as administrator and immediately LittleNavMap and Andalusi open and run completely normally and from that moment on everything works normally.

Please let me know what the problem might be so that these programs do not activate when I click on any of the icons that the FSUIPC7 installation has created on my desktop but it does when I run FSUIPC7.exe directly as an administrator

Thank you very much

J J GómezInstallFSUIPC7.log

[John Dowson]

7 minutes ago, beatic said:

installed FSUIPC7 version v7.2

I presume you mean 7.5.2...

9 minutes ago, beatic said:

when I click on any of the icons that the FSUIPC7 installation has created on my desktop … and they don’t do it either in the installation for the two simulators ( MSFS2020 and MSFS 2024 ) nor with the separate installation for each of them.

What does this mean? The two icons that the FSUIPC installer installs on your desktop only start MSFS2020 and MSFS2024 only (unless using the batch auto-start method, which you aren't).  Do they  start the respective MSFS versions?
When each MSFS version starts, does FSUIPC7 also auto-start? If not, then auto-start is not working - see the following FAQ entry: 

 

14 minutes ago, beatic said:

Please let me know what the problem might be so that these programs do not activate when I click on any of the icons that the FSUIPC7 installation has created on my desktop but it does when I run FSUIPC7.exe directly as an administrator

Do you need to be running as an admin? Always better to run with standard privileges if possible, but if running as admin then everything must be ran as admin - MSFS, FSUIPC and all client programs.

17 minutes ago, beatic said:

[Programs]

runif1=READY,CLOSE,"H:\08 - Andalusi\Andalusi.exe"

runif2=READY,CLOSE,"H:\Little Navmap\Little Navconnect\littlenavconnect.exe"

Note that with the READY, the programs will not be started until an aircraft is loaded and ready to fly. If you want them started earlier, when MSFS is still in the menu system, use the keyword CONNECTED instead.

Any further questions, please attach your FSUIPC7.ini and FSUIPC7.log files, not your InstallFSUIPC7.log file. There is no issue with your installation.

John

[beatic]

Many thanks John for your rapid response to the problem; effectively I refer to the version v7.5.2, sorry for the error.

It has a perfect explanation; now I use the batch auto-start method and it work correctly.

For the moment I continue using the READY command because I can wait until an aircraft is load an ready for a flight.

With your permission, I am going to transcribe your response in the Forum of my VA AlAndalus Airlines, because another colleague also had the same problem.

Thank you again John

Juan José Gómez

[John Dowson]

6 minutes ago, beatic said:

I use the batch auto-start method and it work correctly.

Ok, but I wouldn't recommend this. Better to sort out issues with the EXE.xml auto-start if possible.

And when using either, if you get any connection issues or too many retries (check your FSUIPC7.log file if you have issues - in many cases, this will indicate where the issue is...) then look at tuning the FSUIPC start-up parameters (described in the Advanced User manual, and there is a FAQ entry for this in these forums).

11 minutes ago, beatic said:

For the moment I continue using the READY command because I can wait until an aircraft is load an ready for a flight.

That is fine. I am actually thinking of making CONNECTED the default for starting programs, and add a new option EARLY (or maybe START) to start programs after FSUIPC has started (i.e. the current default). This is because that it looks like quite a few add-ons don't handle the connection stall times, timeouts and reconnection gracefully, which can starve the FS of further simconnect connections if not handled properly. So always better to start such programs after FSUIPC has obtained a connection.

16 minutes ago, beatic said:

With your permission, I am going to transcribe your response in the Forum of my VA AlAndalus Airlines, because another colleague also had the same problem.

No problem.

Saludos,

John