SPAD. NeXt and FSUIPC 7 seem to be causing CTDs

Bug Reporting Hub Resolved
43

CTD every start. Emty community . I am using FSUIPC
I leave Beta.

Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.25.4.0, Zeitstempel: 0x00000000

Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 1.25.4.0, Zeitstempel: 0x00000000

Ausnahmecode: 0xc0000005

Fehleroffset: 0x00000000013f7198

ID des fehlerhaften Prozesses: 0x1edc

Startzeit der fehlerhaften Anwendung: 0x01d846ca20540acf

Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.25.4.0_x64__8wekyb3d8bbwe\FlightSimulator.exe

Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.25.4.0_x64__8wekyb3d8bbwe\FlightSimulator.exe

Berichtskennung: 4bcf1d21-af28-47fa-bee9-fd40fefa54d6

VollstÀndiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.25.4.0_x64__8wekyb3d8bbwe

Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

44

Hi,
I have installed the full version of FSUIPC 7 today to be able to feather the props using my HC Bravo prop levers and so far I did not experience any problems.
I start MSFS using the FSUIPC shortcut. This also gives me a startup screen immediately, no need to worry for the first minute whether MSFS launches or not.

45

CTD for me as well when starting FSUIPC when in the cockpit after the flight loaded.

46

If the community managers manage to communicate the impact of this bug correctly to Asobo, this will be treated as a showstopper, because it’s a CTD and easy to reproduce, and receive a fix.

If not, FSUIPC and SPAD.next will learn to be smarter about the SimConnect requests they make and they’ll wait until the flight has been started before they make the requests that currently crash the sim.

If they literally started the sim, started a flight, then started each of these programs, one after another, each time wiggling a joystick and watching the result on screen, they would have concluded that everything is fine. You literally can not catch everything when you’ve got limited time.

I don’t remember changes to SimConnect being listed in the release notes. If that’s correct, SimConnect functionality might not have been on the list of things the QA team focused on. This bug could well have been caused by a change in a completely different system (let’s say AI traffic, since FSUIPC’s author seemed to think it was related to that).

Disclaimer: I worked in QA, so I tend to defend people working in QA. They have an impossible task.

2 Likes
47

Yes we are the tester and yes I found the solution for FSUIPC. We test and we will love with this, otherwise not use the Beta Version

1 Like
48

Well SPAD crashes the sim 100% of the time so there is no joystick wiggling possible :slight_smile:

If they tried SPAD they would have found the bug. And for such a big team i think we can expect them to test these things.

49

Point taken.

1 Like
50

Doesn’t work for me, still CTD when in the cockpit when starting FSUIPC.

Luckily I use this tool for my controls and that works fine: GitHub - TheFlyingDutchman77/EasyControlsMSFS: EasyControls application for Microsoft Flight Simulator

I use FSUIPC just for my virtual airline that I fly from time to time.

51

Sorry to hear about that, just going to have to wait that one out I think. Make sure it is reported to FSUIPC if it isn’t fixed in the next few days with any patches that come out.

52

They have beta testers.
But not long ago some of them searched for the flaps switch in the F-16 

And said the A/C has a bug 

Because no flaps switch

Have I said enough?

2 Likes
53

Do you have the same issue if you follow the OP’s steps to reproduce it?

Yes

Provide extra information to complete the original description of the issue:

Starting Spad.next or having the plugin in the community directory causes the sim to crash on load

If relevant, provide additional screenshots/video:

54

FYI


Connex (Spad.NEXT) has suggested that this is an issue with messed up wasm standalone module integration (again) in SU9.

I have not joined this beta on this occasion after seeing this issue reported so I can’t verify either way.

2 Likes
55

No need.

Go to: c:\Users\yourusername\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache

in notepad open file named exe.xml
delete lines between Launch.Addon

image
image703×250 8.92 KB

save changes and launch msfs

Source
https://forums.flightsimulator.com/t/loading-bar-and-stuttering-on-takeoff-and-landing/501740/6

56

@TenPatrol Just even better, you can still autostart FSUIPC if you change the FSUIPC7 INI to not Auto Connect to MSFS2020 :slight_smile:

Ok my current workaround is:

Set:

AutoConnectToSim=No

In the FSUIPC7 INI file, start as usual with EXE.xml, bat and so on.

After your in cockpit ready to fly, open FSUIPC and connect it to MSFS.
image

If you want to leave the cockpit, open FSUIPC again and disconnect from MSFS.

This works for me without any CTD :slightly_smiling_face:

1 Like
57

Do you have the same issue if you follow the OP’s steps to reproduce it?

I can confirm the same issue with my copy of Spad.NeXt. is causing a crash to desktop from the main menu screen of MSFS or when in a flight.

For me it doesn’t matter whether you start Spad first or after MSFS load.

I am running Spad.NeXt version 0.9.11.5 home use licence.

Spad opens with the splash screen and when the main window opens the sim crashes.

Windows Event Viewer Log:

Provide extra information to complete the original description of the issue:

Faulting application name: FlightSimulator.exe, version: 1.25.4.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.25.4.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000000131d85e
Faulting process ID: 0x3c74
Faulting application start time: 0x01d8473b3f3ba70a
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.25.4.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.25.4.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: 403bd514-81b9-4871-bc8f-62a9e7c39b4e
Faulting package full name: Microsoft.FlightSimulator_1.25.4.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

If relevant, provide additional screenshots/video:

58

Sorry found another cause of the CTD :frowning:
If I enable FSUIPC7 on ‘Cold and dark’ plane it crashed MSFS2020.
So my workaround only works if plane isn’t cold and dark.
I try to check if it only works when start on runway or also if you set the plane to run. But testing takes time, because the startup time of MSFS2020 is very high.

Ok it seems to be related to the starting position :frowning: So try to start on runway not parking position.

59

Or a True value on Disabled.

60

I did not think the CTD was related to that, but it is always worth trying without AI data going to FSUIPC7 as this has caused issues in the past.

It seems that this issue is related to the 3rd party programs use of SimConnect when in the MSFS main menu. If using FSUIPC7, the current fix (mentioned above and in the FSUIPC forums here: FYI: FSUIPC might be incompatible with SU9 right now - FSUIPC7 MSFS - The simFlight Network Forums) is to disable auto-connection and connect/disconnect manually when not in the menu system (i.e. connect after you are ready-to-fly, disconnect before returning to the main menu).

Hopefully Asobo will fix this before the official release. If not, I will look into updating FSUIPC7 to only connect once ready-to-fly, and disconnect as soon as the flight is cancelled.

John / FSUIPC

4 Likes
61

Confirmed, SPAD.NEXT via FSUIPC7 crashes the sim.

image
image1348×898 72.6 KB

62

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

Needed to uninstall FSUIPC 7 , CTD during load