FSUIPC stops running after a few seconds

[Gabedi]

Good Day Pete,

Computer:
Intel I7 - 5930K
16GB DDR 4 Ram
GTX 960 (Latest Drivers)
Windows 10 Pro x64
P3D V3 3.4.9

Addons:
PMDG 737 NGX
PMDG 777
PMDG 747 
Majestic Dash 8
FS Labs A320
Active Sky Next
FS Time Sync
PFPX
Vpilot

I've been having this issue where FSUIPC seems to stop working midflight although it keeps logging. When you try and open it from the add on menu in P3D it does not open. The aircraft controls become unresponsive even though you can see the yoke/throttles and control surfaces moving on the aircraft. If the aircraft were in motion when FSUIPC stops it becomes uncontrollable and inevitably crashes, but FSUIPC stops before the aircraft moves the aircraft seems to remain stuck even under full power.

At first the problem seemed to happen after a few minutes of flight and this prompted to do a clean install of P3D, however this seem to make the problem worse. Now it happens within 10 seconds of starting the Sim.

I've tried everything i could find on forums Deleted p3d CFG, updated graphics card drivers, Mapped flight controls to just P3D, mapped flight controls to go through FSUIPC calibration (with them disabled in p3d) and i haven't had any luck.

I've tried running P3D without the external Addons (PFPX, ASN, Vpilot, Fs Time Sync) and still get the same result. 

This morning I decided to see what effect deleting FSUIPC would have and guess what all my problems seem to disappear and aircraft respond as the should

I would appreciate your assistance.

Regards,

Gabedi
 

FSUIPC4.log

[Pete Dowson]

1 hour ago, Gabedi said:

I've been having this issue where FSUIPC seems to stop working midflight although it keeps logging. When you try and open it from the add on menu in P3D it does not open. 

So the FSUIPC entry is still in the Add-Ons menu?

1 hour ago, Gabedi said:

 The aircraft controls become unresponsive even though you can see the yoke/throttles and control surfaces moving on the aircraft.

The surfaces and graphic control levers moving means that the controls must be working. Nothing else would do that. if the flight of the aircraft doesn't reflect those changes then there's something wrong with the installed aircraft. There's no way FSUIPC has of moving control surfaces and cockpit control graphics without sending controls to P3D. If P3D is then not responding correctly you need to look at the installed aircraft, not FSUIPC.

Try with a default aircraft. Do NOT load one of those very complex aircraft by default. Test with a default aircraft and load the more advanced one after.

1 hour ago, Gabedi said:

Now it happens within 10 seconds of starting the Sim.

Surely you cannot have started a flight within 10 seconds of starting the sim. Even on my 5GHz cockpit system it takes minutes, not seconds, and you seem to have a lot of add-ons.

The Log shows nothing wrong, but then you didn't actually do anything by the look of it:

    47219 Starting everything now ...
    47281 ASN active function link set
    47281 Ready for ASN WX radar
    82031 Sim stopped: average frame rate for last 49 secs = 19.9 fps
    82031    Max AI traffic was 0 aircraft

So, the system would have been ready to fly some time after 47 seconds from starting P3D. I've found here that the FSUIPC "Starting everything now" occurs whilst P3D is still actually loading stuff, with its progress bar on screen.

To actually see when it does occur on your system, could you run P3D in Windowed mode (ALT+ENTER) and enablre FSUIPC's Console Log (in the Logging tab in Options). You'd need to restart P3D after setting these changes. Then you would see the log being created at the same time as the progress of the P3D loading etc.

The log you supplied shows you terminated the session pretty much when it was ready to fly (i.e. when it could accept the terminate request) -- just 35 seconds after FSUIPC itself was ready. So, there's absolutely no useful information in the log. It is just a successful load and termination of P3D and FSUIPC.

1 hour ago, Gabedi said:

I've tried running P3D without the external Addons (PFPX, ASN, Vpilot, Fs Time Sync) and still get the same result.

You are looking in the wrong place. From the symptoms you describe it has to be one of the internal add-ons, the complex aircraft. I  suspect one or more of those is clogging up the SimConnect communications. If they have DLLs being loaded then you might need to try disabling those too.

Pete