LucaZ Posted October 2 Report Posted October 2 (edited) Hi John, hope all is well. For several weeks now, I've had many issues with MSFS closing. Not sure where lies the problem.. FSUIPC (currently on version 7.4.17) with WASM enabled, GSX, Fenix A320 or PMDG (all running with the latest version). Since 3 weeks ago (when there were various updates from MSFS, FSUIPC, Fenix and PMDG), I started to get CTDs. Before posting this ticket, I read many forums and started my troubleshooting from scratch by reinstalled completely MSFS, cleaned up the community folder and installed the main programs. Then some tests: On the ground, never a CTD. GSX update in flight is disabled (GSX option). Using Fenix A320 and GSX I get a CTD. When only using PMDG 777 with GSX sometimes I get a CTD. Fenix A320 or PMDG 777 with GSX and SLC and or A Pilot Life: Random CTDs in flight, SLC closes on it own sometimes on the ground, A pilot's life sometimes closes on its own. Per suggestions on the different tickets that you have already answered in the forum, I have done the following: Reviewed the FSUIPC Advanced User Guide section on Auto-tuning of initial start-up ini parameters FSUIPC.ini: InitialStallTime set to 15 seconds FSUIPC.ini: Added "ProvideAIdata=No" above "KittyHawk" (per suggestions in one of the forums discussing GSX issues) FSUIPC_WASM.ini (WASM Persistence Area): LvarScanFrequency=0 and LvarScanDelay=10 In the SimConnect.xml file I also changed the MaxClients from 64 to 128. Today I was in the middle of a flight only using the Fenix A321 and GSX, and the sim suddenly closed. Attached you will find: FSUIPC.ini FSUIPC7.log FSUIPC_WASM.log (p.s. the errors on p42_immersion_fx... have any effect?) FSUIPC_WASM.ini Not sure if I have an issue with Simconnect, FSUIPC or anything not related to either? It's very frustrating so if there is anything you can see and help me to troubleshoot would be great. No sure if it matters, but I also noticed that in the .EXE file (C:\Users\...\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache), FSUIPC is not the first Launch Addon, but the second under the Fenix. Thank you John for your time and very much look forward to hearing from you. Luca FSUIPC_WASM.ini.zip FSUIPC_WASM.log.zip FSUIPC7.ini.zip FSUIPC7.zip Edited October 2 by LucaZ
John Dowson Posted October 3 Report Posted October 3 13 hours ago, LucaZ said: or several weeks now, I've had many issues with MSFS closing. If MSFS crashes, you need to look at the Asobo forums. FSUIPC7 is a separate application and it cannot cause MSFS to crash, and the WASM is sandboxed - if that crashes, it should not affect MSFS. Your WASM log shows no issues - except that it didn't exit cleanly (as MSFS had crashed), and your FSUIPC7.log shows no issues. I think your issue may be with GSX - I have heard a lot of reports of CTDs with GSC, e,g, see https://forums.flightsimulator.com/t/gsx-ctd/537743/7/, Have you tried without GSX? Other than that, as I can't see how this can be anything to do with FSUIPC. 13 hours ago, LucaZ said: (p.s. the errors on p42_immersion_fx... have any effect?) Not really. This just means that you may not be able to distinguish an lvar by name, using FSUIPCs lvar facilities, as it will be truncated to 55 characters.
LucaZ Posted October 3 Author Report Posted October 3 Thank you John for your time. I will unlink GSX and try a flight and will report back. Regards
Luke Kolin Posted October 4 Report Posted October 4 GSX, like FSUIPC, is also a separate application. Cheers
John Dowson Posted October 4 Report Posted October 4 13 hours ago, Luke Kolin said: GSX, like FSUIPC, is also a separate application. But doesn't it also have a component installed in the MSFS community folder, or even update some official files? And if it is only a separate application, it uses other APIs as well as SimConnect. For example, there was a known bug in the NavData API (used by GSX) that could cause the sim to crash, although I believe it is fixed now (haven't followed this though). There are also many reports of MSFS CTDs when using GSX, although this doesn't necessarily mean that GSX is at fault. But its certainly worth trying a few flights without GSX to see if the CTDs continue or not. Cheers, John
LucaZ Posted October 5 Author Report Posted October 5 Since I didn't know the source of the CTDs, I decided to literally delete MSFS, clean up the computer of any and all files related to it and start with a clean installation (which takes hours..). I just installed FSUIPC and Fenix A320. I'm currently troubleshooting: FSUIPC is on AutoConnect, but once MSFS starts FSUIPC stays in the state: Trying to connect. I need to look at the settings and understands why. When on the ground and preparing the Fenix MCDU, at some point the MCDU freezes, and then MSFS closes. I have checked that Flight Simulator is in he Windows Defender exemption. Not sure what is going on, but this is basic.so will keep researching. Thanks. Luca
LucaZ Posted October 5 Author Report Posted October 5 I'm currently doing a flight in which I excluded MobiFlight addon. So far all is working fine... could this be the issue??? I will revert back as soon as I land (hopefully). Cross fingers..
John Dowson Posted October 5 Report Posted October 5 2 hours ago, LucaZ said: FSUIPC is on AutoConnect, but once MSFS starts FSUIPC stays in the state: Trying to connect. I need to look at the settings and understands why. Please see the section Auto-tuning of initial start-up ini parameters in the Advanced User guide, and/or the following FAQ entry: 1 hour ago, LucaZ said: 'm currently doing a flight in which I excluded MobiFlight addon. So far all is working fine... could this be the issue??? No idea, Everyone suffers from CTDs at some point. It is up to you to determine the cause... John
LucaZ Posted October 5 Author Report Posted October 5 So... did a flight without MobiFlight and I had no CTDs... so for me this is one step forward. However I can't get FSUIPC to connect to MSFS automatically. I have to start it manually for some reason, and I think I have done all the steps indicated in the Auto-tuning of initial start-up ini partameters of the Advanced User Guide. Second flight just with the Fenix, the MCDU access buttons and displays stopped working,, and I'm using only Fenix and FSUIPC. So now I have to ask Fenix what could be the issue. But I must stay that I'm so disappointed with MSFS right now which makes me really think about not getting MSFS 2024 but rather moving to X-plane. When purchasing a software and add-ons, it shouldn't be the user twitching files, but rather the add-ons being thoroughly tested by the producer. What is the point spending money buying addons and then having all these issues? The only software I have issues with is MSFS. Thanks again for all your help and hope the items above help other users with similar issues. Luca
Captain_Johnny Posted October 6 Report Posted October 6 (edited) Interesting - I have almost the same setup ... running GSX, Fenix A320 and MobiFlight. When I've been flying online with VATSIM using vPilot, and within the last 5 or 10 min of the flight (approaching the circuit area) my MSFS CTD. Unless coincidentally, it often happens when I go to adjust the HDG knob. The reason I query FSUIPC as a possible culprit, is because when I go to Windows Event Logs (Windows+X keys / Event Viewer), and I look for the MSFS CTD, it says the cause of the CTD was FSUIPC (in each instance of this happening). CTD Data excerpt from Windows logs: Faulting application name: FSUIPC7.exe, version: 7.4.1.7, time stamp: 0x66d82cd2 Faulting module name: ntdll.dll, version: 10.0.22621.4111, time stamp: 0x518e67bb Exception code: 0xc0000005 Fault offset: 0x0000000000033faa Faulting process id: 0x0x120AC Faulting application start time: 0x0x1DB0D9DC187A81D Faulting application path: C:\FSUIPC7\FSUIPC7.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 931a5ee7-576a-49ed-b33c-a98b6e5734ea Faulting package full name: Faulting package-relative application ID: Are you able to please offer any assistance, thanks? Edited October 6 by Captain_Johnny Added CTD data
John Dowson Posted October 6 Report Posted October 6 13 hours ago, LucaZ said: However I can't get FSUIPC to connect to MSFS automatically. Why not? Please show me a log file for this. This usually happens if you have the DetectToConnectDelayAuto ini parameter set too high, and are not waiting long enough for it to connect., 13 hours ago, LucaZ said: Second flight just with the Fenix, the MCDU access buttons and displays stopped working,, and I'm using only Fenix and FSUIPC If assignments to presets or lvars/hvars/calc. code stop working mid flight, this is usually a sign that the FSUIPC WASM module has crashed, You can prevent this by setting a WASM ini parameter to stop repeated scanning for new lvars - see 14 hours ago, LucaZ said: When purchasing a software and add-ons, it shouldn't be the user twitching files, but rather the add-ons being thoroughly tested by the producer. What is the point spending money buying addons and then having all these issues? The only software I have issues with is MSFS. MSFS have not made it easy for 3rd party developers. Everyone has different add-ons, different PC specs, different controllers, etc. FSUIPC should work pretty much out-of-the-box for most users. However, some initial configuration maybe needed If you have many add-ons and it takes MSFS more than a minute or two to arrive to the main menu state. But even then, FSUIPC will auto-tune itself - but you need to exit MSFS and restart once MSFS has arrived at the main menu AND FSUIPC has connected. Once toy have done the initial set-up/tuning, you shouldn't need to do this again. Auti-tuning will still monitor the connection, and if multiple connection attempts are detected, it will flag auto-tuning to be ran the next time FSUIPC is auto-started by MSFS. For this to work correctly, you need to make sure that you are still in the MSFS main menu when FSUIPC7 connects.
John Dowson Posted October 6 Report Posted October 6 On 10/6/2024 at 5:35 AM, Captain_Johnny said: The reason I query FSUIPC as a possible culprit, is because when I go to Windows Event Logs (Windows+X keys / Event Viewer), and I look for the MSFS CTD, it says the cause of the CTD was FSUIPC (in each instance of this happening). CTD Data excerpt from Windows logs: Faulting application name: FSUIPC7.exe, version: 7.4.1.7, time stamp: 0x66d82cd2 Faulting module name: ntdll.dll, version: 10.0.22621.4111, time stamp: 0x518e67bb Exception code: 0xc0000005 Fault offset: 0x0000000000033faa Faulting process id: 0x0x120AC Faulting application start time: 0x0x1DB0D9DC187A81D Faulting application path: C:\FSUIPC7\FSUIPC7.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 931a5ee7-576a-49ed-b33c-a98b6e5734ea Faulting package full name: Faulting package-relative application ID: Are you able to please offer any assistance, thanks? That shows an exception in FSUIPC - did FSUIPC7 crash? Can you please show me/attach your FSUIPC7.log file from when it crashed. If MSFS CTD'ed, are there any windows events for this? If FSUIPC7 CTDs, this should not affect MSFS in any way, as it is a separate app. If MSFS CTDs, this can cause exceptions in FSUIPC7 (which will be reported in the windows events), but FSUIPC7 should handle this gracefully, and usually exits as it detects that MSFS is no longer running. Your log file would show if this is what is happening. John
LucaZ Posted October 6 Author Report Posted October 6 Hi John, as always you have a lot of patience and a complete gentleman. Very much appreciated. What bugs me about his is that I have a high end Corsair Vengeance i7500 with RTX 4090 and i9-14900K Intel Core. All my other programs, which require a lot of memory and peformance work very well. The only one is MSFS. So I run the different scans with an elevated command prompt, and without any surprise it's all ok: Dism.exe /online /Cleanup-Image /checkhealth Dism.exe /online /Cleanup-Image /scanhealth sfc /scannow Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore Dism.exe /Online /Cleanup-Image /StartComponentCleanup In reference to the FSUIPC Auto-Start, I let it run and it found the sweetspot, so it should be ok now. I have spent a lot of money on MSFS add-ons, and the problems started three weeks ago approximately when FSUIPC, Fenix A320, PMDG and MSFS had updates. So somewhere there is a conflict that is created by one of these updates, but I reinstalled everything from scratch and still have a problem. Is it Simmconnect, data leak, fenix? not sure at this point. I have spent a lot of money on add-ons, and the fact that I can't have a normal flight it just disappoints me so much. I will keep trying, but I'm really giving up. Will MSFS 2024 be any different or should I just switch to x-plane? Maybe the world imagery is not the same, but friends flying with have far less problems. Thanks, Luca
John Dowson Posted October 7 Report Posted October 7 Yes, MSFS has always given a lot of issues. By some reports, this can also be related to on-line activity. A few thinks to try: - switch to AI traffic if using live traffic, and maybe try some flights without traffic - turn off live weather if using that to see if that makes a difference - check for add-on conflicts - i.e. try the Simstaller tool from Parallel42 (free) - check the Asobo CTD reference for further tips: https://forums.flightsimulator.com/t/unofficial-reference-guide-to-ctd-solutions/442117 John
Captain_Johnny Posted October 7 Report Posted October 7 On 10/6/2024 at 9:41 PM, John Dowson said: That shows an exception in FSUIPC - did FSUIPC7 crash? Can you please show me/attach your FSUIPC7.log file from when it crashed. If MSFS CTD'ed, are there any windows events for this? If FSUIPC7 CTDs, this should not affect MSFS in any way, as it is a separate app. If MSFS CTDs, this can cause exceptions in FSUIPC7 (which will be reported in the windows events), but FSUIPC7 should handle this gracefully, and usually exits as it detects that MSFS is no longer running. Your log file would show if this is what is happening. John Hi John, thanks for helping out. I can't recall if FSUIPC actually crashed or not. When I look at the FSUIPC log files, it seems I only have the current day and previous session log file available - so I'll have to wait until it happens again and save that file then post it here for you to take a look if you're able, thanks.
John Dowson Posted October 7 Report Posted October 7 13 minutes ago, Captain_Johnny said: When I look at the FSUIPC log files, it seems I only have the current day and previous session log file available Yes - only log files from the current and previous sessions are available. 13 minutes ago, Captain_Johnny said: I'll have to wait until it happens again and save that file then post it here for you to take a look if you're able, thanks. No need to post it unless FSUIPC actually crashed. As I said, it was most likely an exception due to the MSFS crash, and then FSUIPC7 would exit gracefully. Just look at your log file to confirm this, and only post it crashed, i.e. no closing log statements, like the following: Quote ... 3767171 === Hot key unregistered 3767171 === Stop called ... 3767296 === Closing external processes we started ... 3767812 === About to kill any Lua plug-ins still running ... 3768734 === About to kill my timers ... 3768937 === Restoring window procs ... 3768937 === Unloading libraries ... 3768937 === stopping other threads ... 3768937 === ... Button scanning ... 3768937 === ... Axis scanning ... 3768937 === Releasing joystick devices ... 3768937 === Freeing macro memory 3768937 === Removing any offset overrides 3768937 === Clearing any displays left 3768937 === AI slots deleted! 3768937 === Freeing button memory ... 3768937 === Closing my Windows ... 3768937 === Freeing FS libraries ... 3769937 === Closing devices ... 3769937 === Closing the Log ... Bye Bye! ... 3769937 System time = 07/10/2024 12:12:36 3769937 *** FSUIPC log file being closed Minimum frame rate was 32768.0 fps, Maximum was 0.0 fps Maximum AI traffic for session was 0 aircraft Traffic deletions 0 aircraft Memory managed: 13 Allocs, 12 Freed ********* FSUIPC Log file closed *********** John
Captain_Johnny Posted October 7 Report Posted October 7 3 minutes ago, John Dowson said: Yes - only log files from the current and previous sessions are available. No need to post it unless FSUIPC actually crashed. As I said, it was most likely an exception due to the MSFS crash, and then FSUIPC7 would exit gracefully. Just look at your log file to confirm this, and only post it crashed, i.e. no closing log statements, like the following: John Got it, thanks John, wilco :).
LucaZ Posted October 7 Author Report Posted October 7 12 hours ago, John Dowson said: Yes, MSFS has always given a lot of issues. By some reports, this can also be related to on-line activity. A few thinks to try: - switch to AI traffic if using live traffic, and maybe try some flights without traffic - turn off live weather if using that to see if that makes a difference - check for add-on conflicts - i.e. try the Simstaller tool from Parallel42 (free) - check the Asobo CTD reference for further tips: https://forums.flightsimulator.com/t/unofficial-reference-guide-to-ctd-solutions/442117 John Hi John, yes planning to do a flight without live connection(bing data, etc) and see how it goes. I recall that this was an issue maybe 1-2 years ago? Will come back with news. Thanks
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