FSUIPC not starting

[barrybartson]

Hello,

I have been using FSUIPC for a long time now but it stopped working all of a sudden. I have uninstalled and reinstalled but to no avail.

I only use it to connect to VAS ACARS and it is a real problem it does not work now, I tried to force start it manually but that does not work either.

Is there anyone that can help?

Thanks

[John Dowson]

For auto-start issues, please see 

 

6 minutes ago, barrybartson said:

I tried to force start it manually but that does not work either.

What do you mean by this? Just saying 'does not work' does not really help me....
What happens when you double-click the FSUIPC7.exe in Windows explorer? Do you see the FSUIPC7 splash screen or a windows message? Is the FSUIPC7.log file updated? If so, show me that. Otherwise, show me your InstallFSUIPC7.log file.

John

[barrybartson]

Thank you for your quick reply John.

It does not autostart but it has never done that. When I double-click the FSUIPC7.exe in Windows explorer I see the FSUIPC7 splash screen but when it dissapears again ot does not seem to run.

I am sorry for the very noob questions but I have no idea how to show you the log files?

[John Dowson]

31 minutes ago, barrybartson said:

It does not autostart but it has never done that.

Then see that FAQ entry I referenced.

32 minutes ago, barrybartson said:

I see the FSUIPC7 splash screen but when it dissapears again ot does not seem to run.

Are you aware that, by default, when you start FSUIPC7 it displays the splash screen and then sits in your system tray? To open the main window, try Alt+F.

I suggest you try reading the provided documentation if you do not know how FSUIPC7 operates - it is different to other versions of FSUIPC as it is a separate application/executable rather than an embedded dll. You should at least peruse the User guide.

35 minutes ago, barrybartson said:

I am sorry for the very noob questions but I have no idea how to show you the log files?

It will be in your FSUIPC7 installation folder. If you cannot see it, it will be due to your windows explorer settings. See the appendix in the Installation and registration guide on how to change this.

John

[barrybartson]

I know it should show the splash screen. Afterwards it does not work... if I do alt+f nothing happens.

I did read the user guide and know it should run as a seperate application, but do not seem to get it to work.

FSUIPC7.log InstallFSUIPC7.log

Edited October 2, 2022 by barrybartson

[John Dowson]

You ran the installer from within the zip file:
   Running in folder 'C:\Users\blaur\AppData\Local\Temp\Rar$EXa23188.45475\Install_FSUIPC7'
You should not do this - extract the files from the zip folder first before running the installer.

Do that and try again.

John

[barrybartson]

It works now. Thanks a lot

[N987PL]

John, since this is the closest post I can find regarding my issue, I wondered if you could help me.  Before the last two updates, (current logs attached), I didn't have to use the FSUIPC desktop Icon to start FSUIPC.  In MSFS load, the FSUIPC logo would display and everything worked when the MSFS load completed and I was on the ramp.  The only way FSUIPC works now is for me to use the desktop icon, and that was random a bit last Friday.  I can go to Windowed mode while the aircraft is on the ramp in MSFS, click on the FSUIPC executable, and everything loads then, but that is the only way to have FSUIPC control consistently.  Did a parameter change in the .ini with the latest releases that I need to address?  As you'll see in my attached .ini, AutoStart is set to "Y".  Much appreciation for your help in advance....

FSUIPC7.ini FSUIPC7.log

[John Dowson]

16 hours ago, N987PL said:

I didn't have to use the FSUIPC desktop Icon to start FSUIPC.

The desktop icon that is optionally added by the FSUIPC7 installer does not start FSUIPC7 - that icon simply starts MSFS and shows a splash screen for 25-30 seconds while MSFS is loading. It is MSFS that starts FSUIPC7 via the EXE.xml file.

16 hours ago, N987PL said:

Did a parameter change in the .ini with the latest releases that I need to address?  As you'll see in my attached .ini, AutoStart is set to "Y". 

There is no AutoStart ini parameter. Please see the following FAQ entry that details how auto-start works and what to check to fix any issues:

 

John

[N987PL]

Thanks for the reply John.  I moved FSUIPC ahead of the other two addons in my EXE.xml file.  Will see if this fixes and report back.

[N987PL]

Didn't fix the issue.  I completely deleted the EXE.xml file, uninstalled FSUIPC, and reinstalled.  FSUIPC re-created the EXE.xml file and the FSUIPC log attached didn't report any errors in autostarting.  And again, prior to the last two FSUIPC updates, FSUIPC started automatically.  I guess it could be a coincidence and may not have been a result of any changes with FSUIPC but rather an MSFS update.  I can still get FSUIPC working in MSFS by running the FSUIPC.exe, but have to do it manually while MSFS is loading. 

InstallFSUIPC7.log

[John Dowson]

All information on FSUIPC7 auto-start is in that FAQ entry - I have nothing more to add or say on this issue. Please read that thoroughly (there is an alternative method you can try..) - as it says in the README.txt:

Quote

3. FSUIPC7 does not auto-start with MSFS, even though this option was selected during installation.
   If you find that FSUIPC7 doesn't start with MSFS, this is usually due to a problem with your EXE.xml file. Please check your InstallFSUIPC7.log file.
   This is usually due to another add-on corrupting the EXE.xml file. To resolve, you can delete/rename your current EXE.xml file (whose location can be
   determined from your InstallFSUIPC7.log file) and re-install FSUIPC7. However, the add-on that corrupted the EXE.xml may not be started automatically.
   You will need to manually add this back if you want this app to also auto-start.
   Please see the following FAQ entry for further details on this as well as other possible causes:
      https://forum.simflight.com/topic/95918-fsuipc7-auto-start-with-msfs2020/
   I will NOT RESPOND to further support requests regarding this issue - I will reference this FAQ entry and close/lock the topic.
   If you must post, please use that topic referenced - but don't expect a reply, from me at least!
 

Sorry but I have responded to this same issue so many times now - this is why that FAQ entry exists;

John