Strange problem, I have to close down and restart FSUIPC to get it to connect

[bobsk8]

This issue just started a few weeks ago. When I start a flight in MSFS 2020, my Track IR and Avlilasoft EFB do not connect, and they use FSUIPC. All I have to do is close down FSUIPC, and then restart it, and instantly everything connects normally. I downloaded and installed latest version, same problem.  It isn't a big problem, but wondering if there is something else I could look at to solve it. 

Thanks,

 

[John Dowson]

18 hours ago, bobsk8 said:

This issue just started a few weeks ago.

Did anything change to cause this issue? If it was an FSUIPC update, and you were previously using was pre 7.5.0, then it could possibly be due to the late population of offset 0x3308 that was introduced in v7.5.0, which is needed for compatibility with MSFS2024. If that is the issue, you can use/add the ini parameter Init3308 in the [General] section of your FSUIPC7.ini file to to 13, eg.
    Init3308=13

Otherwise, this is usually due to the auto-start parameters that need tuning. This is described in the Advanced User guide, or in the following FAQ entry:

If you can show me/ attach your FSUIPC.log file when FSUIPC7 is auto-started and your clients won't connect I can take a look.

Btw, I don't think Track IR needs or uses FSUIPC these days (if it ever did), although I don't have this for MSFS2020.

John

[bobsk8]

2 hours ago, John Dowson said:

Did anything change to cause this issue? If it was an FSUIPC update, and you were previously using was pre 7.5.0, then it could possibly be due to the late population of offset 0x3308 that was introduced in v7.5.0, which is needed for compatibility with MSFS2024. If that is the issue, you can use/add the ini parameter Init3308 in the [General] section of your FSUIPC7.ini file to to 13, eg.
    Init3308=13

Otherwise, this is usually due to the auto-start parameters that need tuning. This is described in the Advanced User guide, or in the following FAQ entry:

If you can show me/ attach your FSUIPC.log file when FSUIPC7 is auto-started and your clients won't connect I can take a look.

Btw, I don't think Track IR needs or uses FSUIPC these days (if it ever did), although I don't have this for MSFS2020.

John

I forgot that I use FSUIPC to set a couple of controls to TrackIR from my joystick, and that's what doesn't work, not track IR itself. I had init 3308=13 already installed. Will send log file the next time it happens. 

[John Dowson]

10 minutes ago, bobsk8 said:

I forgot that I use FSUIPC to set a couple of controls to TrackIR from my joystick, and that's what doesn't work, not track IR itself.

Ok, that makes more sense then, and it will be because FSUIPC is not connecting to the FS. The log file should reveal why.

John

[bobsk8]

5 hours ago, John Dowson said:

Ok, that makes more sense then, and it will be because FSUIPC is not connecting to the FS. The log file should reveal why.

John

Here is log file

FSUIPC7.log

[John Dowson]

The log you attached shows that FSUIPC7 did not connect, and was still running when you attached the log file. Please ALWAYS exit FSUIPC before attaching files.

And please leave FSUIPC7 running at least until MSFS arrives at the main menu.

Your issue is almost certainly due to the auto-start parameters not being tuned correctly. I cannot advise what to use with that log file you attached for the reasons already stated. Try tuning the auto-start parameters yourself (see the documentation or that FAQ entry I referenced) or provide me with a better log file and I can advise what to try.

Also check your EXE.xml (location is logged in the InstallFSUIPC7.log file if you don't know where that is. If there are multiple entries for other apps, then you can also try making sure FSUIPC7 is started first. You can also attach this and I can take a look.

John  

[bobsk8]

7 hours ago, John Dowson said:

The log you attached shows that FSUIPC7 did not connect, and was still running when you attached the log file. Please ALWAYS exit FSUIPC before attaching files.

And please leave FSUIPC7 running at least until MSFS arrives at the main menu.

Your issue is almost certainly due to the auto-start parameters not being tuned correctly. I cannot advise what to use with that log file you attached for the reasons already stated. Try tuning the auto-start parameters yourself (see the documentation or that FAQ entry I referenced) or provide me with a better log file and I can advise what to try.

Also check your EXE.xml (location is logged in the InstallFSUIPC7.log file if you don't know where that is. If there are multiple entries for other apps, then you can also try making sure FSUIPC7 is started first. You can also attach this and I can take a look.

John  

I just looked at the exe.xml, and FSUIPC was at the bottom of the list, I moved it up to the top, and now is  starts up properly every time... 

 

Thanks,

 

EXE.xml