LucaZ

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

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

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

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..

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

Thank you John for your time. I will unlink GSX and try a flight and will report back. Regards

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