Dutch60 Posted Thursday at 08:06 AM Report Posted Thursday at 08:06 AM FSUIPC7 7.5.3 Crashes FS2024 SU3 beta 1.5.10.0 When starting with sim in EXE.xml When starting after sim is already running in the menu When starting in cockpit crashes the sim directly It does not crash FSUIPC7
John Dowson Posted Thursday at 08:47 AM Report Posted Thursday at 08:47 AM As this is in the beta, you should wait for a fix in the beta. FSUIPC7 is an external app and in no way should it crash the FS. Maybe check the Asobo beta forums to see if anything has been reported there regarding simconnect apps. I have had a severe crash on my development PC during a windows update and cannot look into anything at the moment until I have repaired this. John
John Dowson Posted Thursday at 08:59 AM Report Posted Thursday at 08:59 AM ...and are you sure this is related to FSUIPC7? i.e. does it run normally without FSUIPC7 running? There are lots of reports of CTDs in this beta version - see https://forums.flightsimulator.com/t/ctd-loading-into-1-5-10-0/727551 And I cannot investigate MSFS crashes - you need to report to Asobo. Even if the SimConnect API has changed, it should be backwards-compatible, so I am confident, even if this issue is provoked by FSUIPC7, it is an issue for Asobo and must be fixed by them. John
Dutch60 Posted Thursday at 09:06 AM Author Report Posted Thursday at 09:06 AM I know that SU3 is still in beta but I never had any problems with FSUIPC7 in any stable or beta versions. On the official forums the problem has also started buzzing sinds the release of SU3 1.5.10 yesterday. There is no mention of any updates in the beta that affect the SDK and SimConnect. That's why I'm confused on to why FSUIPC7 does directly crashes the Sim when it connects in anyway with SimConnect. No other utility that I have and uses the SDK or SimConnect crashes the Sim. As I was a software developer for many year (Microsoft business software) I will fully respect that you can't fix this asap so please take the time to fix it. I just wanted make you aware of this problem for future releases. Regards Hans.
Dutch60 Posted Thursday at 09:11 AM Author Report Posted Thursday at 09:11 AM The main problems where with SU3 beta 1.5.9.0 and entering the cockpit where all official FS20 and some FS24 where crashing the Sim. FSUIPC7 was working fine in SU3 beta 1.5.9.0 These problems are now fixed in SU3 beta 1.5.10 PCUIPC7 is the only SimConnect app (I have) that is crashing the Sim in SU3 beta 1.5.10.0. Regards Hans.
Dutch60 Posted Thursday at 09:14 AM Author Report Posted Thursday at 09:14 AM Other SimConnect apps I use are: Virtual Fly HUB for my Virtual Fly controllers. Octavi IFR-1 for my Octavi autopilot. FSRealistic Auto-FPS Beyond ATC FlyByWire FSLTL ...
John Dowson Posted Thursday at 09:19 AM Report Posted Thursday at 09:19 AM 7 minutes ago, Dutch60 said: so please take the time to fix it. There is nothing wrong with FSUIPC and there is no fix, unless SimConnect is no longer backwards-compatible (which I very much doubt!). This needs to be fixed by Asobo. This has happened on previously beta releases and is usually fixed in a subsequent beta update. As I said, there is no way I can fix or investigate a sim CTD, only report this to Asobo.
John Dowson Posted Thursday at 09:36 AM Report Posted Thursday at 09:36 AM You could maybe try removing the FSUIPC WASM from your community folder. You won't have access to lvars or presets, but that would test if its the WASM thats the issue, not FSUIPC7 itself. There was a report/comment on that link I posted that said this fixed the issue.
Dutch60 Posted Thursday at 10:04 AM Author Report Posted Thursday at 10:04 AM First Test Part of the logfile where things seem to go wrong 144531 User Aircraft ID not supplied -- trying default 144531 Requesting keyboard input... 144531 Requesting user aircraft data... 149812 Failed on SimConnect_CallDispatch for Message, return = 0xC000014B 149812 Failed on SimConnect_CallDispatch for Traffic Message, return = 0xC000014B 149812 Failed on SimConnect_CallDispatch for Traffic Message, return = 0xC000014B 151062 MSFS no longer running - trying to find... 151062 === Calling SimConnect_Close ... 151281 === SimConnect_Close done! FSUIPC7 Test 1.log Second Test Removing FSUIPC7_WASM.wasm Removing events.txt and myevents.txt Stripping the PCUIPC7.ini file of all aircraft specific entries. Did not fix the problem. Part of the logfile where things seem to go wrong 4203 User Aircraft ID 39124992 supplied, now being used (myftm=1) 4203 Requesting keyboard input... 4203 Requesting user aircraft data... 4297 Aircraft loaded: running normally now ... 4797 System time = 26/06/2025 11:53:28, Simulator time = 09:53:28 (00:00Z) 5125 Failed on SimConnect_CallDispatch for Message, return = 0xC000014B 5125 Failed on SimConnect_CallDispatch for Traffic Message, return = 0xC000014B 5578 MSFS no longer running - trying to find... 5578 === Calling SimConnect_Close ... 5797 === SimConnect_Close done! FSUIPC7 Test 2.log Regards Hans
Dutch60 Posted Thursday at 10:32 AM Author Report Posted Thursday at 10:32 AM As I have been using FSUIPC forever I know you are a very experienced developer! I don't know if you use C++ or C# but this is some example code where things go wrong. SimConnect Dispatch C++.txt SimConnect Dispatch C#.txt
John Dowson Posted Thursday at 10:53 AM Report Posted Thursday at 10:53 AM 46 minutes ago, Dutch60 said: 5125 Failed on SimConnect_CallDispatch for Message, return = 0xC000014B 5125 Failed on SimConnect_CallDispatch for Traffic Message, return = 0xC000014B 5578 MSFS no longer running - trying to find... These errors are due to the fact that MSFS has crashed and is no longer available. As I keep telling you, there is nothing wrong with FSUIPC7. This needs to be fixed by Asobo.
Dutch60 Posted Thursday at 01:16 PM Author Report Posted Thursday at 01:16 PM Ok thanks for the investigation I just have to accept it's Asobo is messing things up again! Up until now I never ran into major problems with the stable and beta version but the last two SU3 betas are a true ....show. Kind regards Hans.
John Noe Posted yesterday at 03:32 AM Report Posted yesterday at 03:32 AM All I know is everything works in 15.10.1 until I load FSUIPC then CTD without hesitation. I don't know if it crashes by itself or through Simconnect. 1
QFAussie Posted yesterday at 04:30 AM Report Posted yesterday at 04:30 AM I have the same experience. The sim loads without FSUIPC. When I add FSUIPC, I get a CTD.
Dutch60 Posted yesterday at 09:20 AM Author Report Posted yesterday at 09:20 AM Good to see I'm not the only one affected by PCFUIPC crashing FS24 SU3 1.5.10.0 Let's hope Asobo can fix this a.s.a.p.
QFAussie Posted yesterday at 09:33 AM Report Posted yesterday at 09:33 AM Dutch, Although I support what you say. I can also say that when I select anything bigger then GA, I still get CTD, without FSUIPC installed. So I do think it is part of the problem, its not the whole problem.
Dutch60 Posted 14 hours ago Author Report Posted 14 hours ago I tried something bigger than GA ''A320neo from EHAM Schiphol" (no FSUIPC) and it worked just fine no crashes with settings at Ultra and at 4K.
QFAussie Posted 13 hours ago Report Posted 13 hours ago Have you tried anything else? I'm not a technical expert, but I think it's a simconnect issue. Once MSFS fix simconnect, FSUICP will work again.
Dutch60 Posted 12 hours ago Author Report Posted 12 hours ago I used to be a Microsoft business software developer and in the FSX day I wrote a small app using SimConnect and FSUIPC but that definitely does not make me an expert on developing something for SimConnect. What aircraft or anything else that I own would you like me to see if it works in FS24 SU3 1.5.10.0? I own the Aviator Edition and a lot of Carenado and Just Flight GA aircraft but I don't have any 3rd party big birds.
QFAussie Posted 10 hours ago Report Posted 10 hours ago I've never developed anything, but have used every sim since MSFS95 and a whole bunch of add ons, apps, mods etc. I also own the Aviator Edition. I've done a little more testing. All at YSSY Flytampa to stay consistent. I tried the new A359 ULR from Inibuilds and I re tried the A333. Both loaded in fine if I closed GSX before attempting anything. Volenta - no crash, no tracking without FSUICP Navigraph hub/simlink - no crash A Pilots Life 2 - Opens but doesn't speak to the sim as it requires FSUICP BeyondATC - The app opened, but couldn't find a connection to the PC GSX - If allowed to auto start, causes CTD when attempting to start a flight. If GSX closed prior to starting a flight and then manually opened, GSX won't open Active Sky - CTD Simapp pro (winwing) - works, no crash I then did the same with the Cessna Skycourier. When I attempted to open BeyondATC, it attempted to load into the flight and then CTD. All I'm saying is, if CTDs are still happening, even after FSUICP is removed, I think we can rule it out and more then likely Simconnect is the issue. 1
Dutch60 Posted 10 hours ago Author Report Posted 10 hours ago Great testing and I totally agree that it's very likely a SimConnect is the issue. A lot if external apps seem to result in CTD. Let's see and wait what SU3 1.5.11.0 will bring us.
QFAussie Posted 8 hours ago Report Posted 8 hours ago External apps seem to be the biggest issue. Xbox users on the forum seem to have little to no issues. Meanwhile us PC users are going nuts over it. I just hope when it comes out, that FSUICP and all the other apps go back to working. I find it hard, that an organisation the size of MS/Asobo, didn't test this before releasing it.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now