MSFS + Prosim crashing : FSUIPC also mentioned in log

[GSalden]

Hello John,Pete,

I am having CTD’s when using MSFS with my Prosim cockpit .
Flying half an hour to do some sightseeing at low altitude is no problem.
Making longer flights always result in a crash.
This time after 45 minutes.

Prosim V3.03b13 / FSUIPC mode (otherwuse blanc speed window in CpFlight MCP Pro 1 )

First this :
Windows Apps log :
FlightSimulator.exe 
0.0.0.0 
5fda32ba 
FlightSimulator.exe 
0.0.0.0 
5fda32ba 
c00000fd 
00000000009805de 
1f10 
01d6f23031ca2ce3 
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe 
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe 
451e640f-9a3b-46d3-91d0-23adea41d9bc 
Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe 
App 

Then this :
Windows Apps log :
FSUIPC7.exe 
7.0.0.4 
5ff89538 
ntdll.dll 
10.0.19041.662 
27bfa5f0 
c0000005 
0000000000045f86 
ec0 
01d6f2306e1250b9 
C:\FSUIPC7\FSUIPC7.exe 
C:\WINDOWS\SYSTEM32\ntdll.dll 
4bc5cda9-42c6-43f7-b991-d34af7b228df 
 

Then this :
FSUIPC log :
21016 MSFS version = 11.0.282174.999
21016 Initialising SimConnect data requests now
26828 \\SERVER\Users\gsald\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\prosim-b738\SimObjects\Airplanes\prosim_b738\aircraft.CFG
26875 flights\other\MainMenu.FLT
28312 Aircraft loaded: running normally now ...
29156 User Aircraft ID not supplied -- trying default
30156 System time = 24/01/2021 10:08:37, Simulator time = 08:08:34 (09:08Z)
30172 Aircraft="Prosim_B738 2021a KLM"
690406 -------------------- Starting everything now ----------------------
690406 Starting WideServer now ...
692484 \\SERVER\Users\gsald\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT
1552812 **** Restarting traffic scanning due to non-reception ****
4377344 Failed on SimConnect_CallDispatch for Traffic Message, return = 0xC000014B
4377344 Failed on SimConnect_CallDispatch for Message, return = 0xC000014B
4377437 TransmitClientEvent failed! (Event=65706, Param=-2964, nGroup=0, fSame=0
4377547 TransmitClientEvent failed! (Event=65706, Param=-2959, nGroup=0, fSame=0
4377641 TransmitClientEvent failed! (Event=65706, Param=-2954, nGroup=0, fSame=0
4377750 TransmitClientEvent failed! (Event=65706, Param=-2949, nGroup=0, fSame=0
4377844 TransmitClientEvent failed! (Event=65706, Param=-2944, nGroup=0, fSame=0
4377844 **** Too many TransmitClientEvent errors received! Re-connecting now ... ****
4378500 MSFS no longer running - exiting


I have a RTX 3090 and have it running at default speeds with only a more acxtive fan profile for maxed cooling.
Driver 461.09. Happened too with the driver before that one.
Swapfile = automatic ( perhaps on fixed values ? )

CPU 7940X @ 4.7 Ghz since 3 years / 32 Gb 3600 / 2 Tb M2 (MSFS + P3D) + 1 Tb M2 (P3D)
Displays 4K @ 30 hertz. One wide view spread over 2 displays (4096x2160).

Already lowered settings so 38-50 fps is no problem to sustain. Set FPS to 30 inside MSFS.
Also emptied Rolling Cache to be sure that there wasn't faulty data in it. 
 

Is this a Simconnect issue from what I see in the FSUIPC log ?

Thanks and best regards,

Gerard

[Pete Dowson]

32 minutes ago, GSalden said:

Is this a Simconnect issue from what I see in the FSUIPC log ?

Yes, and there are threads about it here and in the dedicated MSFS subforum above. The problem has been reported to Asobo, but it might help emphasise the matter if you could also report it via Zendesk along with the Windows crash data for MSFS (they won't be interested in the subsequent crash which that caused in FSUIPC7, but certainly John will want to look at that though as a separate matter.

Currently it seems you can alleviate the problem (though not eliminate it) by setting "ProvideAIData=No" in the [General] section of the FSUIPC7.INI file. This reduces the amount of SimConnect interaction -- it seems that MSFS doesn't survive well with too much, and FSUIPC is pretty intensive in that. I expect ProSim adds a lot as well, whether you run in FSUIPC or SimConnect mode.

The only drawback with not reading the AI data is that some programs (not sure about ProSim) will not get the traffic information they need for such things as TCAS warnings or ATC operations.

This problem seems to have been introduced with the last update to MSFS as CTDs were far less likely in previous releases.

Pete

 

[GSalden]

Many thanks for explaining what is going on. I also found other threads about it and will try the workaround too.

Is it correct that I then do not see AI traffic on my PFD ? 
If that is so then it is no problem as finishing a flight is more important.

Surely I will make a Zendesk ticket .

Regards, Gerard

 

Additional :

Unfortunately MSFS crashed again with the workaround applied, just by standing on the tarmac , but with Prosim running. I now only see 1 error Simconnect message instead of multiple, so there is progression.

 

   39359 Aircraft loaded: running normally now ...
    39547 User Aircraft ID not supplied -- trying default
    40547 Aircraft="Prosim_B738 2021a KLM"
    40547 System time = 29/01/2021 07:59:23, Simulator time = 05:59:21 (06:59Z)
   272750 -------------------- Starting everything now ----------------------
   272750 Starting WideServer now ...
   275922 \\SERVER\Users\gsald\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT
  1884906 Failed on SimConnect_CallDispatch for Message, return = 0xC000014B
  1888187 MSFS no longer running - exiting
  1888187 === Hot key unregistered
  1888187 === Stop called ...
  1888203 === Closing external processes we started ...

[John Dowson]

4 hours ago, GSalden said:

Is it correct that I then do not see AI traffic on my PFD ? 

Only if the PFD is taking traffic data from the FSUIPC traffic tables, which  I doubt.
It should only affect any 3rd party programs that rely on FSUIPC for traffic data.

It has been reported (on the Asobo forums) that it is also improved for some folks when disabling both live and AI traffic in MSFS.
You could also try that, but that would affect the AI traffic on the PFD.

John

 

[GSalden]

Hi John,

Humberto from Prosim wrote me that these types of CTD are already under investigation.

He stated that it is the result of doing something to an unfinished product, when the lack of documentation is the main issue.

Prosim for MSFS is a kind of “preview” and any update from Asobo might even break the current status.

Your suggestion to disable Live Traffic and AI Traffic might help, so for flying from A to B it is no problem.

If I want AI all over the place I can switch to P3D.

regards, Gerard