FSUIPC won't start

[speedbird144]

*** Moved from main support forum to FSUIPC7 support sub-forum ***

Greetings. 

When I start MSFS using FSUIPC icon for MSFS I noticed a small black window pops up and FSUIPC won't start anymore. I have to start FSUIPC manually now. I have not done any changes. It just started happening. I am wondering if this is FSUIPC related issue. I use Version 7.4.12c. 

Thanks for looking. 

 

Edited May 5 by John Dowson
Moved to FSUIPC7 support forum

[John Dowson]

That is the console window for the bat file. That is created but should be iconised, i.e. in your system tray. That window will stay around until FSUIPC7 is started, but if you kill that window, then FSUIPC7 will not start.

Does that window actually show, or are you opening it from your task bar?

If you just leave things and wait, you should see that console window disappear and FSUIPC7 will then start. 

Also, please post in the correct forum for support, which for FSUIPC7 is the FSUIPC7 / MSFS sub-forum - I have moved your post.

John

Edited May 5 by John Dowson
Further info added

[speedbird144]

That window pops up when I start MSFS. Yes, it does disappear now (it did not before). This console window did not show up before, I started noticing it like 2 days ago. Yesterday this console window remained open all the time even after MSFS fully loads. Several hardware stopped working till I manually start FSUIPC. Looks good today. Console window disappears now. 

Thanks for explanation.  

[speedbird144]

Hello again. 

Something is still going on. When the console window disappears I have got a message that another instances of FSUIPC already running. When I close this error message FSUIPC stops working. I still can open FSUIPC from the taskbar but I cannot open anything like assign any buttons or switches, etc. Shall I reinstall FSUIPC? 

[John Dowson]

33 minutes ago, speedbird144 said:

Something is still going on. When the console window disappears I have got a message that another instances of FSUIPC already running.

That message should be self-explanatory - FSUIPC7 was already running when you started MSFS via the FSUIPC7-installed MSFS.bat file.

33 minutes ago, speedbird144 said:

When I close this error message FSUIPC stops working.

What do you mean by this?  Was FSUIPC working before you closed this error message? Why was FSUIPC7 running already anyway? Perhaps it is being started both via the EXE.xml and via the MSFS.bat file?

33 minutes ago, speedbird144 said:

I still can open FSUIPC from the taskbar but I cannot open anything like assign any buttons or switches, etc.

This implies that you are using an unregistered/unlicensed version of FSUIPC7. Do you have a license, or are you using the trial license? If the latter, then this probably expired after 1st May. There is a new one available, valid until 1st June, but if you have already tried the trial license, you should either purchase or forget.

33 minutes ago, speedbird144 said:

Shall I reinstall FSUIPC? 

Re-installing FSUIPC7 will not do anything, so no - if you are on a version before 7.4.11 (current released version) then re-install. Looks like you are using a 7.4.12 beta, so don't re-install unless you want to go back to 7.4.11 or update to the 7.4.12 official release (see below).

Note that I have now released 7.4.12, but this is for the SU15 beta release of MSFS (1.37.17.0 and later). It does work with the current MSFS release (1.36.2.0), but I cannot guarantee the stability with this version as it is built using the MSFS SDK of the SU15 release (0.24.2.0). This is available here: 

For any further issues/questions, please attach your FSUIPC7.log file.

John

 

 

[speedbird144]

I have a registered version! 

I open MSFS via desktop FSUIPC icon. Before I updated FSUIPC to v7.4.12 I never saw console window opening. I am not sure why FSUIPC was already running. I rebooted PC several times, I made sure no processes were running before I start MSFS again. 

Now when I start MSFS I see that console window. It closes when I am at the main MSFS window before the aircraft selection. Then console minimizes and I got that message that FSUIPC is already running. I do not click or open FSUIPC separately. I just start FSUIPC using desktop icon. 

What I mean FSUIPC was not (fully) working, when I try to assign buttons or offsets etc, those options not available anymore, it looks like I do not have a registered version of FSUIPC, but I do. I had access to those options earlier but not anymore. I did not make any changes to the SIM or PC. 

The log is attached. 

I just noticed I have Console windows opens. I guess this is the problem?  

FSUIPC7, Version 7.4.12c.txt

[John Dowson]

20 minutes ago, speedbird144 said:

I open MSFS via desktop FSUIPC icon. Before I updated FSUIPC to v7.4.12 I never saw console window opening. I am not sure why FSUIPC was already running. I rebooted PC several times, I made sure no processes were running before I start MSFS again. 

Did you install the 7.4.12-beta using the installer or by downloading and replacing the FSUIPC7.exe?
The auto-start method for FSUI{C7 has changed between 7.4.11 and 7.4.12. In 7.4.11, the MSFS EXE.xml file is used - the installer adds an entry to the EXE.xml file (or creates this file if not already available) to start FSUIPC7 via MSFS. In 7.4.12, the MSFS.bat file starts FSUIPC7 after a pre-defined delay/wait after starting MSFS - the console window will be created (hopefully iconised) and is visible when the bat file is running, i.e. for the delay period between when MSFS is started and when FSUIPC7 is started.

Looking at the log file you attached, FSUIPC7 IS being started via the EXE.xml file:

Quote

      282 Auto-started via EXE.xml with DetectToConnectDelayAuto=30, InitialStallTime=5

So it looks like FSUIPC7 is being started both via the EXE.xml and via the MSFs.bat file. You should use one method only. If you installed FSUIPC7 via the installer, it should only implement one auto-start method. I don't know why you have two enabled - you need to remove one. The easiest way to do this would be to download and install the full release of FSUIPC7 v7.4.12. Otherwise you either need to manually edit the MSFS EXE.xml file to remove the FSUIPC7 entry (or delete altogether if not used by anything else) or comment-out the start-up of FSUIPC7 from the MSFS.bat file. The location of the MSFS EXE.xml file will be logged in your InstallFSUIPC7.log file. and the MSFS.bat file will be in your FSUIPC7 installation folder.

20 minutes ago, speedbird144 said:

What I mean FSUIPC was not (fully) working, when I try to assign buttons or offsets etc, those options not available anymore, it looks like I do not have a registered version of FSUIPC, but I do. I had access to those options earlier but not anymore. I did not make any changes to the SIM or PC. 

Sorry, but I do not understand this. The log file you attached shows that FSUIPC7 is running as a registered version:

Quote

Checking the Registrations now ...
User Name="My name"
User Addr="email@gmail.com"
FSUIPC7 Key is provided
WIDEFS7 not user registered, or expired

from the folder D:\MSFS Programs\FSUIPC. If that message is logged, I cannot see how you cannot have access to the Assignments menu...

How come you have opted not to install the MF presets file:

Quote

       79 Preset file 'D:\MSFS Programs\FSUIPC\events.txt' not found [info only]

?

 

 

[speedbird144]

"How come you have opted not to install the MF presets file:"

To be honest no idea what does this even mean. I do not make any changes to any files. I just installed everything what comes with FSUIPC folder.  

"Did you install the 7.4.12-beta using the installer or by downloading and replacing the FSUIPC7.exe?"

I downloaded ZIP file, extracted and ran it. The installer deleted the current version and then installed the new one. I then selected as I have a registered version.

Should I run the installer again using the file included in the answer above? 

 

[John Dowson]

3 minutes ago, speedbird144 said:

To be honest no idea what does this even mean. I do not make any changes to any files. I just installed everything what comes with FSUIPC folder.  

This file is installed by default - if its not installed, then you must have de-selected it during the installation process.
The MF presets are extremely useful - you should install this file.

4 minutes ago, speedbird144 said:

Should I run the installer again using the file included in the answer above? 

Not sure what file you are referring to, but if you have the beta installer then yes, run this again and re-install. You could download the latest 7.4.12 release, but this is built using the MSFS SDK for SU15, so better to wait until this is released before installing that, unless you are already running the MSFS beta version.

Once re-installed, please try again. Any issues, please attach your FSUIPC7.log file and the InstallFSUIPC7.log file.
If you previously installed using that installer, the uninstaller may not remove the EXE.xml file entry for FSUIPC7 - check this after installation and remove manually if needed.

John

[speedbird144]

Hello John. 
After installing v7.4.11 I started noticing PMDG 737 freezes in MSFS. I don’t recall it happened with beta 7.4.12. I read on Discord PMDG forum that beta version 7.4.12 addressed some issues with PMDG. I am not sure if FSUIPS has anything to do with these freezes. The also told me, it could be WASM crash. Again , not sure if FSUIPC has anything to do with WASM. PMDG support and I are trying to figure it out these freezes. 

[John Dowson]

There is an issue in 7.4.11 where the PMDG threads are not starting correctly in some circumstances, fixed in 7.4.12 - see 

 

This is the PMDG issue that is addressed in 7.4.12. However, this will not be causing any freezes.

On 5/12/2024 at 10:33 PM, speedbird144 said:

The also told me, it could be WASM crash. Again , not sure if FSUIPC has anything to do with WASM.

The PMDG WASM crash? FSUIPC has nothing to do with this - it uses its own WASM.

On 5/12/2024 at 10:33 PM, speedbird144 said:

PMDG support and I are trying to figure it out these freezes. 

Ok - please update if you find out anything.

Cheers,

John

[speedbird144]

Hi John. Can you clarify Auto-tuning feature, please?

“Please note that this feature is only activated when using the auto-start facility, i.e. when MSFS is starting FSUIPC7, which is the default and recommended configuration.” 

Can you clarify “when MSFS is starting FSUIPC7”? Do I have to start MSFS using default MSFS icon, or FSUIPC7 installer icon?

 

I removed the DetectToConnectDelayAuto  ini parameter from the [General] section of FSUIPC7.ini file (before I start FSUIPC7 / MSFS).

I added the following to the [General] section of your FSUIPC7.ini file (before you start FSUIPC7 / MSFS):  StartUpTuningActive=Yes

 

After these steps should DetectToConnectDelayAuto reappear back in .ini file or not? (it is no longer there after I deleted it and started the sim).

When I added StartUpTuningActive=Yes should I start MSFS using MSFS default icon, or FSUIPC7 installer icon? If I start MSFS using default icon FSUIPC does not start.

I clearly missing something here.

 

FSUIPC7.ini FSUIPC7 log.txt

[John Dowson]

4 hours ago, speedbird144 said:

Can you clarify “when MSFS is starting FSUIPC7”? Do I have to start MSFS using default MSFS icon, or FSUIPC7 installer icon?

This is not actually correct anymore, but was correct on initial release, and should really have been 'when MSFS starts FSUIPC7 via the EXE.xml file'.
However, now that the default auto-start has been switched from using the EXE.xml file to the MSFS.bat file, it should be:
    “Please note that this feature is only activated when using the auto-start facility, either via the MSFS' EXE.xml file or the FSUIPC' MSFS.bat file (via the Desktop icon)” 

This is all explained in the latest FSUIPC7 Advanced User guide (for 7.4.12) which I have attached below.

5 hours ago, speedbird144 said:

I removed the DetectToConnectDelayAuto  ini parameter from the [General] section of FSUIPC7.ini file (before I start FSUIPC7 / MSFS).

I added the following to the [General] section of your FSUIPC7.ini file (before you start FSUIPC7 / MSFS):  StartUpTuningActive=Yes

If you remove the DetectToConnectDelayAuto  ini parameter, auto-tuning will run automatically, no need to add the StartUpTuningActive ini parameter. Otherwise, you can leave the DetectToConnectDelayAuto  ini parameter and add StartUpTuningActive=Yes to force auto-tuning.

5 hours ago, speedbird144 said:

After these steps should DetectToConnectDelayAuto reappear back in .ini file or not?

Only if it is needed.

5 hours ago, speedbird144 said:

When I added StartUpTuningActive=Yes should I start MSFS using MSFS default icon, or FSUIPC7 installer icon?

If you are using auto-start via the MSFS.bat file / FSUIPC 'MSFS' Desktop icon, then you must use this to start MSFS (and FSUIPC7) as this is where the auto-start component is. If you are using the EXE.xml auto-start method, then it doesn't matter how you start MSFS. Basically it is active if auto-started and not manually started via using the FSUIPC7.exe.

5 hours ago, speedbird144 said:

I clearly missing something here.

Why don't you take a look at your log file as this will log auto-start activity. Looking at the log you attached, this shows that FSUIPC7 was auto-started and auto-tuning was active:

Quote

      281 Auto-started via MSFS.bat with DetectToConnectDelayAuto=60, InitialStallTime=20
      281 **** Auto-start tuning is active

Note your log file ends after 70.89 seconds and was attached while FSUIPC7 was still running.

Auto-tuning terminates and updates your FSUIPC7.ini when MSFS gets to the main menu (and FSUIPC7 is connected at this stage). What is happening in your case is that you are getting to the main menu, selecting a flight and starting the flight before FSUIPC7 is connected. Therefore FSUIPC7 is not detecting MSFS in the main-menu state and so not updating the auto-start parameters. However, it WILL do this once you terminate your flight and go back to the main menu. If you exit before doing this, auto-start will just activate the next time that you run MSFS. If you want auto-start to do its job, you can always wait for a short while (until FSUIPC7 connects) when you get to the main menu to allow this state to be detected by FSUIPC7. 30-40 seconds should suffice.

Anyway, I really wouldn't worry about this to much. Your system loads pretty fast, and the auto-tuning process will do its job and probably reduce the DetectToConnectDelayAuto parameter to either its minimum or until it detects an error,  and then increases it again.

Note that I will release 7.4.12 when SU15 is released. It is already available from the Announcements sub-forum if using the SU15 beta.

John

FSUIPC7 for Advanced Users.pdf