fuipc / cpflight arent talking to each other

[eddmariner]

cpflight v 3.86 will not connect with fsuipc v 7.5.2 in fs2020.

what additional info do you should i include\?

[eddmariner]

error message reads

fs_com  connection problem with fsuipc

 

[John Dowson]

Was it working with a previous version of FSUIPC7, and if so, which one?

Note that there is one recent change that can affect some add-ons expecting a value in offset 0x3308 (FS version) at start-up, as this is no longer set until FSUIPC has connected to MSFS. If that is the issue, you can add
    Init3308=13
to the [General] section of your FSUIPC7.ini file.

Is FSUIPC actually running? If so, you can attach your FSUIPC7.log file and I can take a look for any errors there, but I do not support CPFlight and you should contact their support.

This is also continually getting reported - check out one of the other threads on CPFlight with MSFS.

[eddmariner]

ok.where do i start,.  im using msfs2020 v13820/ cpflight mcp/ pmdg b777/ fsuipc v752 / win 11 home.

it all started last week after months of trouble free flying. when it did, i replaced fsuipc versions 751/752e/ and now 752. cpflight would not communicate with fsuipc.

i installed and reinstalled cpflight drivers and all fsuipc versions with no results.

after inserting your suggestion \(Init3308=13) things worked as they should.  \however, after restarting the computer i got the same non working situation. checking the ini file the inserted figures were missing, as it seems they do after any restart.  restarted and checked several times , sometimes init3308 is there sometimes not .

here are the text files so far.

\i appreciate anything you can do \mr. Dowson.

 

FSUIPC7_prev.log FSUIPC7.log

Edited Wednesday at 08:19 AM by John Dowson
event files removed - not needed

[John Dowson]

No need to attach event files or licenses - they are installed by the installer.

The two log files you attached are very different.
The FSUIPC7.log file (from last time it was ran) shows that you manually started FSUIPC7 once MSFS was running and it started, connected and ran without issues. Were thinks working in this session?

The FSUIPC7_prev.log file (from the previous time it ran) shows that FSUIPC7 was auto-started by MSFS but failed to connect. This looks to be because your MSFS is taking a long time to start and FSUIPC7 has not been tuned correctly. FSUIPC7 would usually auto-tune itself but it needs to actually connect to MSFS todo this. Your _prev.log file shows that auto-tuning was active but never completed as it never connected to MSFS.

I am not sure why it never connected when it weas auto-started - it could be that you ran out of Simconnect connections. What other add-ons are you running?
Please read the section 'Auto-tuning of initial start-up ini parameters' in the Advanced User guide, or read this FAQ entry: 

Also increase the number of simconnect connections allowed if you have not done this already. Do this by increasing the maxClients entry in your SimConnect.xml file to 128 (default is 64). 

3 hours ago, eddmariner said:

it all started last week after months of trouble free flying. when it did

So it just started on its own? Was there a sim update? Did your start-up times change drastically? Your DetectToConnectDelayAuto ini parameter is set to 50 (seconds), which seems reasonable, but your log from the auto-start shows that the last attempt to connect was after 220 seconds and for some strange reason this never succeeded or timed-out.
What is the (approximate) time it takes from when you start MSFS to when FSUIPC7 is started (i.e. you see the FSUIPC7 splash-screen), and then how long does it take from FSUIPC7 start until MSFS arrives to the main menu state? Have this times increased/changed dramatically recently (i.e. when your issues started)?

3 hours ago, eddmariner said:

after inserting your suggestion \(Init3308=13) things worked as they should. 

That may have been a coincidence. What version of FSUIPV were you using before updating to 7.5.1? If it was 7.5.0, and everything was working, then that parameter isn't needed, It does no harm to have it though.

3 hours ago, eddmariner said:

checking the ini file the inserted figures were missing, as it seems they do after any restart.  restarted and checked several times , sometimes init3308 is there sometimes not .

Sorry but this just doesn't make any sense. That ini parameter is never written or removed, only ever read. As other ini parameters can be added/removed, it may change position but will never be removed.

John

[eddmariner]

i use the fsuipc logo to start fs2020, the fuipc splash sreen logo comes on for one second and disappears. from then til the sim starts where i can choose aircraft and airport is very long , about ten minutes.

not sure of any sim updates as such, navdata update done before this all started,

fsuipc versions 751, 752e,752. all produced the same errors in connection but all versions each would work a least  once but then not work after that,\9now im confusing myself).

no matter what version i use, if fs2020 is started and fsuipc is running, when i connect cpflight and i see autoconnect icon on the init screen then i know its working right, if that autoconnect and check box isnt there its not gonna work right.  im gonna try a flight now and report back.

[John Dowson]

I have moved your post to the FSUIPC7 support sub-forum.

10 hours ago, eddmariner said:

from then til the sim starts where i can choose aircraft and airport is very long , about ten minutes.

That is a very long start-up time...how long from when FSUIPC7 is started by MSFS until you get to the main menu in MSFS?

With such a long start-up time, I think it is probably better if you disable auto-start of FSUIPC7 and always start it manually once MSFS is ready. You can (manually) create a link on your desktop to start FSUIPC7 only.

10 hours ago, eddmariner said:

fsuipc versions 751, 752e,752. all produced the same errors in connection but all versions each would work a least  once but then not work after that,\9now im confusing myself).

This is not related to any changes in FSUIPC7. Just use the latest release.

11 hours ago, eddmariner said:

im gonna try a flight now and report back.

Ok. If you get issues, check the to see if FSUIPC is connected.

To determine if there are any simconnect issues, you can enable simconnect logging - see 

 

Also you should increase the maxClients parameter in your SimConnect.xml file from the default of 64 to 128, if you have not done that already.

John

[eddmariner]

i have completed everything in this section except the log create file thing(confusing).

things are now working as they should (for now).so i thank you profusely Mr Dowson,for your time and expertise.

[John Dowson]

7 hours ago, eddmariner said:

i have completed everything in this section except the log create file thing(confusing).

Do you mean logging simconnect? What is confusing about those instructions? Please let me know and I will update...

But you probably don't need to do this - it is a last resort. It can help with diagnosing simconnect connection issues as it shows all simconnect clients and how many connections they are using (as well as all SimConnect activity). And the log files can grow large very quickly.

8 hours ago, eddmariner said:

things are now working as they should (for now).so i thank you profusely Mr Dowson,for your time and expertise.

Ok, not problem - thanks for the update. If these issues return, check the FSUIPC log file and see if there are any connection issues and if so take appropriate action (whatever that may be!).

Regards,

John