Redge

I had a similar experience after I installed SU10 and used the latest Nvidia Studio drivers. The problem was worst with the Fenix, where I would languish with frames down in the teens (for reference I've got an i7-10700k and RTX3080 and got ~40fps previously). I fixed it by doing a full clean install of the previous Game Ready Nvidia drivers (i.e. the one released back in August, before this latest version), and everything worked fine after that.

OK. And the extra long recompile time I'm experiencing — 30+ minutes. Is that expected? Or should I quit and restart?

Does the current Fenix version still work with SU10? I ask because I've been apparently recompiling the WASM for 30 minutes now, after upgrading to SU10.

On a flight this afternoon (set to real-time) while doing something on another computer I noticed a sudden switch in sunlight - with the sun suddenly shining brightly on the panel. The sim had switched from around 4pm to 9am all by itself. Real-time was disabled, so I had to do as @grandfred29 said above and adjust time manually before being able to reset it.

I think it doesn't appear on the roadmap because they don't know when they'll have the specific issues fixed, as it relies from input from outside (i.e. Nvidia). I fully suspect they'll launch it in the next month or so, but they won't set a deadline if they, themselves, don't know when the help they need will be delivered.

I was one of the people experiencing lots of CTDs last weekend when I first installed GSX. Today, as a test of GSX and general sim stability, I flew four sectors in a row in a single session (with GSX ops before and after each flight) and I had no issues with sim stability over 9 hours. GSX did freeze on me once before the fourth flight (the menu disappeared and I couldn’t get it back), until I reloaded the Couatl app in the background, but that was very minor and didn’t interrupt the sim session or anything. The GSX update wasn’t available at the time so hopefully it’s now even more stable than it was earlier today when I used it.

It’s in drone camera view in edit mode so you can use the keys/controls you normally use for that.

Quick update on my CTD experiences… After a weekend of troubleshooting and completely uninstalling GSX I saw all the threads about the somehow MS-induced crashes. I managed a couple of trouble free sessions without it, so decided to reinstall GSX and try again. Despite a hiccup during the installation process (The FSDT installer managed to install GSX Pro, but crashed before it would install GSX World), where I uninstalled and then successfully reinstalled, I’ve had no more crashes after a couple of full flights today. I sat out FSX and P3D so never had the pleasure of using GSX before, but it did look intriguing, and I’m very happy with it now that it seems to be working correctly. the installation process is a bit convoluted (and that I think could definitely be improved), but I’d give my experiences using GSX itself today a pretty solid 4/5 in terms of immersion and ease of use.

Just for the record, I’m one of those with constant CTDs and I’ve never owned P3D or GSX on any other platform.

Thanks for the tips. I’ve thrown the towel in for today, but will try clearing the rolling cache and community folder and see if that helps. Despite the trouble I’ve been having with this I am still hopeful for the future of the addon. I’ll just give it a bit more time for it to mature before I try installing it again.

I have completely uninstalled* GSX after experiencing consistent CTDs after 20-60 minutes of flight multiple times (across multiple routes and aircraft). However, today, even without GSX installed, I am still unable to fly for more than 20-60 mins without getting a CTD! Before installing GSX I don’t remember the last time I had a CTD, it was months ago. How can I completely clear my system of this software?! * As much as the installer will let me uninstall the files.

Both times for me were with the PMDG 737-700. I’m now trying the same flight with the Fenix. (Sounds like I’m about to be disappointed though). Glad to hear I’m not the only one experiencing these kinds of CTDs though.

Unfortunately some of us are still awaiting approval to access the forum to even raise a support request. Meanwhile I just experienced my second CTD (same scenario, and same result, albeit 20 minutes later in flight). I think I'll just uninstall it for now and await feedback once I gain FSDT forum access.

I just had my first MSFS CTD in a while, while using GSX for the first time on a proper flight (i.e. while not just testing the tool itself). Windows Event Viewer has logged a few (cryptic - to me at least) details about the cause of the crash: Faulting application name: Couatl64_MSFS.exe, version: 4.8.0.4797, time stamp: 0x62fd088f Faulting module name: Couatl64_MSFS.exe, version: 4.8.0.4797, time stamp: 0x62fd088f Exception code: 0xc0000005 Fault offset: 0x000000000019add8 Faulting process ID: 0x2838 Faulting application start time: 0x01d8b3c72a373508 Faulting application path: C:\Program Files (x86)\Addon Manager\couatl64\Couatl64_MSFS.exe Faulting module path: C:\Program Files (x86)\Addon Manager\couatl64\Couatl64_MSFS.exe Report ID: b77bf35a-1727-43f3-b943-ca9ab387118a Faulting package full name: Faulting package-relative application ID: And... Activation context generation failed for "C:\Program Files (x86)\Addon Manager\couatl\Couatl.exe". Dependent Assembly Microsoft.FlightSimulator.SimConnect,processorArchitecture="x86",publicKeyToken="67c7c14424d61b5b",type="win32",version="10.0.61259.0" could not be found. Please use sxstrace.exe for detailed diagnosis. I never owned P3D, but I know that couatl had a really bad reputation, and was blamed by many for causing the sim to crash. I've also read a very detailed response to those complaints from @Virtuali stating that couatl was simply the messenger when a crash happened, and was unfairly blamed, and incapable of crashing the sim. I'm also vaguely aware that there's a bug in SimConnect, fixed in SU10 (whose beta I'm not running) which would cause the sim to crash from time-to-time. Anyway, not sure if anyone else has experienced this (it was only 20 minutes into my flight - about an hour into the session) or whether the above log is at all useful to help find the culprit?

My problem appears to be that Couatl is unable to run in the first place - I'm getting runtime errors in the FSDT Live Update / Installer apps when trying to configure, update or even uninstall GSX. So I'm not even able to go start from scratch and uninstall GSX to be able to try again. The updater appears to work correctly for my other FSDT sceneries. (Just to clarify: I'm writing here for now as I'm awaiting approval to post on the official FSDT forum). Edit: All working correctly now. My problem seems to have been linked to incorrect downloading last night due to the cloudflare issues.