This apparently affects simconnect and aircraft like the Fenix and PMDG 737 and others. They are working on a fix for this now.  https://forum.simflight.com/topic/98295-new-fsuipc-update-kills-simconnect/

Thanks for heads up I will stay on the current version for now 🙂

 

Thanks

 

daz

Yeah, I'm already hanging out a couple of versions behind because the current ones don't play nice with my VA ACARS System. 

Not been able to use MSFS since the last update to FSUIPC,nothing works FBW,FENIX,GSX etc,i need FSUIPC for my addons,so ill just have to sit tight,unless anyone has the previous version they can share.

Gary Jones.

does anyone have the old installer lying around ? because i just updated and currently debuging for hours... thanks for the explanation 🙂

18 minutes ago, Bam2000 said:

does anyone have the old installer lying around ? because i just updated and currently debuging for hours... thanks for the explanation 🙂

There is a workaround on the thread I posted

 

Strange, I have the latest version installed, and everything works on my side.

EDIT: I checked my logs, and it actually fails to connect for several times, but eventually gets connected.

Edited March 30, 20242 yr by Watsi

yep last night  had no issues  but  today  same  with the  rest of  the users, had  to resort  to installing  my previous installer i had  saved  in  another  folder

The thread Bobsk8 posted shows how to look at your FSUIPC log file and then enter and set a FSUIPC7.ini file parameter called DetectToConnectDelayAuto under the [General] section if FSUIPC7 is loaded automatically, or the parameter called DetectToConnectDelay under the [General] section if FSUIPC7 is loaded manually.

The thread also contains a test FSUIPC7.exe version (7.4.11A) that you can download if needed that seems to work. You just paste the file as a replacement into the location where your current FSUIPC7.exe file is and restart the sim.

Al

Edited March 30, 20242 yr by ark

Thanks for the OP

You can download the previous version from Internet Archive Wayback Machine

Version 7.4.11 is out on FSUIPC's website.

I do not use FSUIPC Autostart because some of my MSFS Aircraft Profiles do not use FSUIPC.

So, I start FSUIPC manually thus no FSUIPC startup Bat file on my desktop (I delete it when it appears after any FSUIPC Update).
I created my own Shortcut to the FSUIPC exe file to start it.

To avoid now having to check MSFS loading time and editing the FSUIPC ini file I:

1. Start MSFS.
2. Wait for MSFS to fully load to the aircraft selection screen.
3. Start FSUIPC.
4. Start other Apps e.g. Navigraph Charts.
4. Select aircraft.
5. Continue on with other choices.

I stumbled into this horror the other day and spent several hours trying to figure out what the heck happened to FBW320n and Self Loading Cargo and finally figured out it was Simconnect related.  I give:  with such a fundamental interface doesn't it seem bizarre MS/A would leave this to Pete Dowson to stay on top of?  Seems like they ought to have their own Simconnect capability with so much dependent on it.  Fortunate my old copy was still in the Downloads folder so could restore functionality.

For any users with issues, please download and use the latest version, 7.4.11, and set/configure the DetectToConnectDelayAuto ini parameter for your installation as documented here:
        https://forum.simflight.com/topic/98307-fsuipc7-configuring-connection-parameters-for-optimal-use-and-to-prevent-simconnect-issues/

This should fix any and all issues with auto-start. If not, please post any issues to that same topic, and include/attach your FSUIPC7.log file and I will take a look.

John

Oddly, only today did I experience an issue, which I have hardly ever experienced in the past. For some reason, when I began to steer the aircraft and use the throttle after start up, nothing happened. When I went into FSUIPC I found that the assignments page was non existent! I had to come out of the sim and then restart the flight. A lot of faff, but it worked. Unsure what went on, but I will update shortly in the hope this issue doesn't rear it's head again.