FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: EasternT32 on August 19, 2022, 04:23:21 pm
-
Hi All,
I'm so happy to have GSX in MSFS, thanks FSDT!
However I’ve had 2 identical CTDs today, i've not had any CTDs for a while and these have only happened after installing GSX, not saying it's GSX but it's the only change to my sim.
Description
Faulting Application Path: D:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Problem signature
Problem Event Name: APPCRASH
Application Name: FlightSimulator.exe
Application Version: 1.27.14.0
Application Timestamp: 00000000
Fault Module Name: StackHash_be1e
Fault Module Version: 10.0.19041.1806
Fault Module Timestamp: 1000a5b9
Exception Code: c0000374
Exception Offset: PCH_44_FROM_ntdll+0x000000000009DA94
OS Version: 10.0.19043.2.0.0.768.101
Locale ID: 1033
Additional Information 1: be1e
Additional Information 2: be1ee9ae549d770496f97ecca7c2c2eb
Additional Information 3: b180
Additional Information 4: b180b1ed557ec7b600acdb36ba4ca9f3
Just wondering if you've seen or know what's causing this?
Thanks
-
I’ve just had a 3rd CTD exactly the same.
-
Nobody ever reported a CTD before. The only thing that could possibly crash the sim is our very small WASM module, because all the rest runs externally. However, it's unlikely, considered how little WASM modules can do.
You can *try* removing this folder:
%LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\fsdreamteam-gsx-pro
And star the sim, this will rebuild it on the next start (don't worry, it doesn't take 10 minutes like an airplane)
-
I have the same problem. Since I've installed GSX this morning, I got at least 5 CTD. I just had one in the fenix A320 5 minutes after takeoff while it never happened before. I use LFMN by Justsim with a GSX profile (VDGS and custom pushback). Maybe there is a conflict with the simulator because of the VDGS ? I had 2 CTD just after parking...
-
Same problem here, departed Samos (LGSM) in the Fenix A320 and after a while a CTD, never had any CTD problems in MSFS only after installing GSX.
-
GSX runs completely external to the sim, so it cannot crash it, surely not directly, and of course none of the testers ever reported a crash.
However, it's possible that, if your are a bit low of available VRAM, run detailed scenery and detailed airplanes, adding the extra object by GSX might be tipping the point to a possible crash, so you just might have to lower the settings.
-
Nobody ever reported a CTD before. The only thing that could possibly crash the sim is our very small WASM module, because all the rest runs externally. However, it's unlikely, considered how little WASM modules can do.
You can *try* removing this folder:
%LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\fsdreamteam-gsx-pro
And star the sim, this will rebuild it on the next start (don't worry, it doesn't take 10 minutes like an airplane)
I will try this, as for the VRAM, I have a very high end machine, I highly doubt it's this.
I'm just intrigued as I I've never seen the fault module name before. I will keep testing and see what I can find
-
I'm just intrigued as I I've never seen the fault module name before. I will keep testing and see what I can find
That module is a very low-level part of Windows, which deals with memory allocation.
-
First flight with GSX installed and around 10 minutes after takeoff got a CTD. Event viewer shows a crash with Couatl64_MSFS.exe. Interestingly with a timestamp not matching the actual crash of the sim. Not exactly sure what to make of this, there was no other crash than the one after takeoff.
This was with the Fenix A320. I can't remember when I had the last crash of MSFS. It's surely a very long time ago.
So we have multiple user's sim crashing when going away from the airport. I'm tempted to see a pattern here.
-
I really hate complaining/being negative, I loved GSX in FSX and P3D, I will love it in MSFS, but I can't currently, over on the MSFS forums it's very clear GSX does cause CTDs.
Emi has also discussed CTD's in his latest video,
https://www.youtube.com/watch?v=daAGeQow_uI&t=21s
-
Well I can unfortunately confirm a 100% CTD rate with GSX installed (tried 4 flights). A friend of mine who flew with me had the same problem and 2 or 3 viewers of my stream reported the same.
The crashes started with GSX, might be a really unlucky coincidence but at least on my end and what I got told first hand with GSX the CTD rate skyrocketed.
For now I had to remove GSX, although I was very hyped about it and have to run some tests without GSX. I could've waited for the rest of the bugs to be ironed out but the crashes are to severe, quite disappointing. I hope there is a fix in the near future, as I love to use GSX again.
-
I too have noticed a sudden spike in CTDs after installing GSX, there must be something happening for sure.
-
Happened to me a few times, but it was only while loading at 3rd party airports. I deleted my rolling cache which seems to have fixed it.
-
but I can't currently, over on the MSFS forums it's very clear GSX does cause CTDs.
There's only some anecdotal evidence about GSX being the "cause".
I don't know if he's using SU9 or the SU10 beta but, during the SU10 Beta, many release notes clearly stated lots of CTDs which DID happened with SU9 (so, clearly, before GSX came out) are supposed to be fixed. SU10 has been delayed because Microsoft wants to work more on DX12 stability. So, while GSX per-se, cannot crash the sim, it's possible that calling heavily into Simconnect with lots of features that, before all our feedback to Asobo, DIDN'T EVEN WORK, AT ALL, before, so I'm open to the possibility we might awoke some seldomly used call or feature that might still have issue IN THE SIM itself.
An example is the new Attached object feature. It's incredibly convenient to use, because it allows lots of efficiency and modularity, since objects can contain other objects and so on, very easily, and without requiring any call every frame to keep the objects attached to each other, with better performances, less stuttering and with all the attached object always perfectly in sync. We used it a lot, for the baggage cart, the passengers in the bus, all drivers, the rotating lights, the towbars, etc.
This feature was added during SU9 Beta, so it's very recent, and I don't know if there are many add-on that use it. And, during SU9 Beta, it was very unstable, with lots of CTDs when LOD with attached objects switched fast with the camera. Most of those have been fixed in time for the official SU9 but, perhaps something so cutting edge might still have some issues, but how could we renounce to such useful feature ? When you are Deboarding/Boarding passenger and Luggage, using the large Bus, there might be up to 45 people attached to the Bus, 11 bags for each carts, 3 carts per wagon and two loaders, you could have an extra 66 attached luggages, in addition to the other objects like drivers, vehicles, etc. If we didn't used that feature, we would have to send hundreds of calls *per frame* just to keep the things attached to each other, it would have been a stutter mess, so we would had to drastically cut down on the people/baggage density. Instead, the attachments is handled entirely by the simulator, with no commands required on our side, so the passenger Bus can go away full and remain smooth. So, maybe we took a risk using a brand new feature that hasn't been tested much but, without it, the program would be way less attractive and way more clunky. If there's a problem in the SDK that risk a CTD, it WILL eventually fixed, sooner or later, it's not as if we are for the quick money, we plan to improve GSX for the next 10 years.
The keyboard handling is a mess in the MSFS SDK, there are still issues and errors for no reasons, plus the inability to intercept a key from the sim, which makes the interface clunkier than it should be.
And clearly, we have lots of objects with lots of different textures, and while GSX might not be able to crash the sim, it IS possible that some less than stable DX12 handling might be stressed more with so many different objects.
What worries me more, are his comments about the procedural aspect. Something that puzzles me is the complain about how the Pushback operator is too slow, but the suggestion to add extra 10 minutes between the arrival of the crew and the passengers. Sure, it's realistic but, how the "normal" user would react to 10 minutes of nothing ? Most users take less than 10 minutes in TOTAL to complete the whole flight preparations. There must be some compromise between absolute realism and playability.
One must understand the premise how this kind of product evolves. We HAD to redo the graphic first, and it took A LOT OF WORK, we were on the verge of burning out, I didn't had a vacation in more than a year, and haven't stopped working, not even in weekends, and I still haven't gone to sleep since the day BEFORE release ( so I'm approaching 48 hours of being awake, that's why I'm probably babbling ), and during those 2 years MSFS came out, we had to keep pushing SOME scenery at the same time, otherwise we would have gone bankrupt already, if we had to survive with the leftover sales from P3D.
Because users TALK about realism and procedures, but when they SEE the graphic, they open their wallets. If this wasn't true, we would all still using P3D today, because as far the SDK and flexibility is concerned, it's WAY ahead than MSFS. Sure, MSFS has many new features, everything you do looks good, but the SDK, when pure programming is concerned, is only marginally better than FSX, with even few things missing.
Speaking about procedures, we really would appreciate some help, because while we think to be fine when programming, modeling, animating and texturing is concerned, some more expertise in real world procedures is always welcome. Yes, lots of the other services are "the same" compared to P3D, but the Pushback has been changed quite a bit, some of the changes were made even fairly recently, like the fact that now the first thing being done is inserting the bypass pin before doing anything, because somebody pointed out to us it was a big no-no as it was before. So no, not the same.
We know the Towbar should stay separate from the Truck and be attached later, that's why we jumped on the Attach point feature as soon as we could, even it it MIGHT be risky, but the towbar now is already separate, we placed many towbars in random places close to the jetway to populate the airport a bit, but also to show the Towbar is ready to be treated separately, because it's already a separate object, so we'll eventually get there.
-
Go get some sleep, things won't get better with too little sleep :)
As for procedures you might want to contact Chock over at Avsim's forum, he's a ground handler in real life and loves to tell from his work.
-
Thanks for your reply Umberto, I really do appreciate the amount of work you have put in. procedures aside because they don't matter as much currently, the stability in the major issue.
Yes it may not be GSX itself causing the crashing of the sim but GSX surely has to be a part? I've seen many a report so far saying they've have been unable to complete a flight with GSX installed, they've uninstalled GSX and the crashes have stopped, then reinstalled GSX and it's started crashing again.
-
Also having this issue, GSX was the only change to my setup and suddenly every flight I attempt ends in a crash. Sometimes it happens during boarding, sometimes it happens two hours into the flight. Almost always happens while I'm moving the camera. Uninstalled GSX and haven't had a crash since.
Event Viewer shows FlightSimulator.exe as the faulting application and module, exception code 0x80000003 which seems (?) to have something to do with memory management.
Even if the crash isn't directly caused by a line of code running in GSX, I have to believe from what I've seen and read that GSX being loaded has some side effect somewhere else that causes MSFS to crash.
GSX was one of my most anticipated plugins for MSFS so if we could send logs or something to help find the issue, please let us know!
-
Good morning !
I am also a bearer of bad news, as I am also encoutering CTD since I've installed GSX.
To be frank and honest, I might had 2 to 3 CTDs maximum since I've bought MSFS2020 back in August 2020 (with two different systems).
But since yesterday, when I've installed GSX, I haven't been able to complete a single flight. CTD occured at least 4 times in the last 24 hours, and happen either during boarding, or sometimes on final.I've also had CTD 1 hour after take-off.
CTD were common for me during the P3D era, but they almost completely disappeared with MSFS for me, and last time I've got one was maybe last year (I don't remember having one those last months).
I'm trying to insist on that, as like many other users, I suspect GSX being a part of it (but not completely as you suggested).
I was really happy to have that immersive addon back with the new sim, but it's a shame that I'm not able to fully enjoy it.
-
I'm really happy to have GSX in MSFS. It was for the last 2 years the tool that I missed the most, this is awesome work ! There are some bugs, and it is normal for a tool as complex as this, but CTD's are the worst things that can happen because it prevents us from enjoying the sim with GSX. Could someone confirm that since the last update of MSFS (1.27.16.0) the CTD problem with GSX seems fixed ? I'm using DX11. By the way, what version of DX were you using when you got the CTD's ?
-
Unfortunately I have to report, that I'm also getting the CTDs, I'm on SU9 so not on the MSFS Beta. I've had a very stable simulator, almost never had any CTDs. With GSX it happens on 3 out of 4 flights. I unlinked it for now, the simulator is stable again. Waiting for a couple of patches here. Thx for your effort!
-
I'm also having CTDs all the time after installing GSX. Had a very stable simulator before (SU9). Installed GSX and now i have only completed 1 out of 6 flights because it crashes in various stages of flight. Uninstalling GSX solves the problem. Directly, or indirectly, I am convinced that GSX is the culprit here. Among other things that makes this product feel "unfinished", this issue surely must get all the effort to solve first since it makes it unusable.
Kristian
-
In my experience when the sim crashes every flight it's a addon conflict of some kind. I'd suggest deleting the content.xml if you're on SU9 and see if that helps with some prioritization conflict.
Otherwise I'd suggest a complete reinstall of GSX (uninstalling and then manually deleting all GSX related stuff, including couatl and couatl64 folders; to be safe you can just delete the whole addonmanager folder [you will have to reinstall your FSDT airports after that, though, so be aware]).
The good news is CTDs that happen every time are rather easy to track and solve, in comparison to those that happen only every 10th flight. So there's reason to be optimistic.
DISCLAIMER: I am in no way part of FSDT, just a regular user that offers some tips.
-
I also got 2 CTDs in 3 flights.
One during cruise the second one on final approach.
Kai
-
Currently standing at 3 CTD's since installing GSX Pro a few hours ago.
Prior to that the sim was very stable.
-
Could anyone of you please confirm that deleting the content.xml and/or clean reinstalling did NOT help?
-
Same here! After installing GSX PRO I start to experience CTD, previous to that they've never happened.
Not talking about couatl not starting issue ("solved" by unistalling the p3d version).
From a long term GSX user (since fsx), I'm very disappointed with that...
-
I'm having too many CTDs, even though when I'm not using the tool (I don't open the toolbar menu). So for me it is not usable at all, sadly!
-
Hi,
I have tried 3 flights with GSX until now. All of them crashed to desktop while descending to the destination airport.
This is the error message:
Faulting application name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.19041.1806, time stamp: 0x1000a5b9
Exception code: 0xc0000374
Fault offset: 0x00000000000ff609
Faulting process id: 0x32e0
Faulting application start time: 0x01d8b488aeaa0298
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: f7ac668b-1504-46cd-9feb-952e2bab198e
Faulting package full name: Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
-
To confirm - has anyone with CTDs tried these three things and it still happens?
1. Delete your rolling cache. Try this first and see if it helps.
2. Delete your content.xml and let it rebuild. Try this as second and see if it helps.
3. Complete reinstall, last resort:
- Uninstall everything using the FSDT Installer
- Uninstall the FSDT Installer itself from the Control Panel
- Go into your Addon manager folder (the one you chose for the installation) and remove the whole folder
- Run the installer again.
-
To confirm - has anyone with CTDs tried these three things and it still happens?
[…]
2. Delete your content.xml and let it rebuild. Try this as second and see if it helps.
[…]
Where is that file located?
-
To confirm - has anyone with CTDs tried these three things and it still happens?
[…]
2. Delete your content.xml and let it rebuild. Try this as second and see if it helps.
[…]
Where is that file located?
Sim from MS Store:
%localAppData%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache
Sim from Steam:
%appData%\Microsoft Flight Simulator
You can let it rebuild by just starting MSFS afterwards. It's only the load order of addons, nothing substantial gets changed.
-
To confirm - has anyone with CTDs tried these three things and it still happens?
[…]
2. Delete your content.xml and let it rebuild. Try this as second and see if it helps.
[…]
Ok thanks. But is it deleting the whole file itself or rather open the text file and delete the contents of it alone?
Where is that file located?
Sim from MS Store:
%localAppData%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache
Sim from Steam:
%appData%\Microsoft Flight Simulator
You can let it rebuild by just starting MSFS afterwards. It's only the load order of addons, nothing substantial gets changed.
-
the same here.Position EDDS.one CDT at taxing and one on Gate. i never had a CDT before.
-
To confirm - has anyone with CTDs tried these three things and it still happens?
[…]
2. Delete your content.xml and let it rebuild. Try this as second and see if it helps.
[…]
Ok thanks. But is it deleting the whole file itself or rather open the text file and delete the contents of it alone?
Where is that file located?
Sim from MS Store:
%localAppData%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache
Sim from Steam:
%appData%\Microsoft Flight Simulator
You can let it rebuild by just starting MSFS afterwards. It's only the load order of addons, nothing substantial gets changed.
Just delete the file itself.
-
I have been testing GSX since yesterday on 5 different flights, all of them with a CTD. Without GSX no CTD.
The product has clearly not been tested thoroughly enough before release, it is still in a beta stadium. Although I see a lot of potential, there is no other way than uninstall it again in order to complete my flights.
Btw, also one of your beta testers has this opinion and experiences CTD's: https://www.youtube.com/watch?v=daAGeQow_uI&ab_channel=737NGDriver (https://www.youtube.com/watch?v=daAGeQow_uI&ab_channel=737NGDriver)
-
737NGDriver was not a beta tester, he was a reviewer.
Please try the following solutions againt CTDs and report back if it worked or didn't (and which step was the solution):
1. Delete your rolling cache. Try this first and see if it helps.
2. Delete your content.xml and let it rebuild. Try this as second and see if it helps.
3. Complete reinstall of GSX as a last resort:
- Uninstall everything using the FSDT Installer
- Uninstall the FSDT Installer itself from the Control Panel
- Go into your Addon manager folder (the one you chose for the installation) and remove the whole folder
- Run the installer again.
DISCLAIMER: I'm not affiliated with FSDT or their support, just a regular user. But I have a lot of experience with CTDs in MSFS and try to offer advice here.
-
737NGDriver was not a beta tester, he was a reviewer.
Please try the following solutions againt CTDs and report back if it worked or didn't (and which step was the solution):
1. Delete your rolling cache. Try this first and see if it helps.
2. Delete your content.xml and let it rebuild. Try this as second and see if it helps.
3. Complete reinstall of GSX as a last resort:
- Uninstall everything using the FSDT Installer
- Uninstall the FSDT Installer itself from the Control Panel
- Go into your Addon manager folder (the one you chose for the installation) and remove the whole folder
- Run the installer again.
DISCLAIMER: I'm not affiliated with FSDT or their support, just a regular user. But I have a lot of experience with CTDs in MSFS and try to offer advice here.
I already did all these steps before posting, nothing helped.
-
Okay thanks for reporting back.
-
Nobody ever reported a CTD before. The only thing that could possibly crash the sim is our very small WASM module, because all the rest runs externally. However, it's unlikely, considered how little WASM modules can do.
You can *try* removing this folder:
%LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\fsdreamteam-gsx-pro
And star the sim, this will rebuild it on the next start (don't worry, it doesn't take 10 minutes like an airplane)
Yeah probably because you have not tested it enough and released it 2 days after giving out press copies... If you had waited another week you would‘ve gotten the feedback by the reviewers/testers of your press copy, which I assume is the same build as the release version. Now you have angry costumers and heavily damaged your companies reputation within the community.
Let's be clear here; I am sure those bugs will get sorted out and this will be a great product in the future, but you must to understand that most people have to uninstall it in order to complete flights! Everyone who is talking about GSX is reporting CTDs with GSX installed and saying that they are gone after uninstalling it. So please stop insisting that GSX does not cause the CTDs!
-
Very well said, it's still incredible everyone has the same mistake but it comes not from them but from us. FSDT just admit that the problem is yours and send us an update. I was the first to be super happy with the release of gsx but with CTDs it's impossible to continue
-
GSX runs completely external to the sim, so it cannot crash it, surely not directly, and of course none of the testers ever reported a crash.
However, it's possible that, if your are a bit low of available VRAM, run detailed scenery and detailed airplanes, adding the extra object by GSX might be tipping the point to a possible crash, so you just might have to lower the settings.
My specifications are 12900K, Nvidia 3090 24GB VRAM, RAM 64 GB, and I have CTDs as well using LVFR SAEZ as departure airport, 15 minutes into the flight with the FBW A320, so I don't think RAM or VRAM can be considered as possible culprits, unless you consider those specifications as substandard...
As for testers not reporting CTDs I am not overly surprised. This morning I tested GSX at five different addon airports, WITHOUT making a flight, just to familiarise myself with the various aspects of the product (I used it since FSX), and never had a CTD while doing that, departing from a gate after using the various services including pushback, taxiing and returning to another gate using the Follow-me and parking guidance. Everything worked fine except for a few hit and miss (like having the stairs sent by GSX to the back door and the passengers debarking from the front door with no stairs - FBW A320). So testers concentrated on ground operations, not flights!
-
I can confirm that GSX is causing the CTDs. I have tried to perform 3 flights today. 2 of those flights got a CTD when I have started taxiing.
And lo and behold, I have disabled the GSX, and MSFS runs with ZERO CTD. All of those 3 flights were performed exactly the same. Same stand, same scenery, same addon.
My specs: i7 9700K, 32GB RAM, RTX3070Ti, SU9
So IT IS caused by the GSX. PERIOD...
-
I only took one flight after GSX setup, got CTD two minutes after take off. This was the first CTD I got with MSFS in a long time.
-
I go back to what I said it's not gsx's fault, several people had the same error yesterday and today and some of them don't use gsx.... Sorry Umberto
-
I go back to what I said it's not gsx's fault, several people had the same error yesterday and today and some of them don't use gsx.... Sorry Umberto
how did you fix it
-
Very well said, it's still incredible everyone has the same mistake but it comes not from them but from us. FSDT just admit that the problem is yours and send us an update. I was the first to be super happy with the release of gsx but with CTDs it's impossible to continue
In the FS Community Umberto is known as "the guy who always blames others (even blaming his customers) in stead of critically looking after his own processes....first reaction is always "it wasn't me ! (e.g. FSDT...")
The product is badly tested....makes me furious!
-
Very well said, it's still incredible everyone has the same mistake but it comes not from them but from us. FSDT just admit that the problem is yours and send us an update. I was the first to be super happy with the release of gsx but with CTDs it's impossible to continue
In the FS Community Umberto is known as "the guy who always blames others (even blaming his customers) in stead of critically looking after his own processes....first reaction is always "it wasn't me ! (e.g. FSDT...")
The product is badly tested....makes me furious!
Amen, brother...
-
Hi ! I got the same problem about the CTD
Both MSFS and Couatl crashed :
-- MSFS CRASH --
Faulting application name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.22000.832, time stamp: 0x3907dfbc
Exception code: 0xc0000374
Fault offset: 0x000000000010c9a9
Faulting process ID: 0x1ce8
Faulting application start time: 0x01d8b4acb38ddda2
Faulting application path: F:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report ID: 019e6f61-2ffc-4ae7-a57e-311aea8efa55
Faulting package full name:
Faulting package-relative application ID:
-- COUATL CRASH --
Faulting application name: Couatl64_MSFS.exe, version: 4.8.0.4801, time stamp: 0x62ff6870
Faulting module name: Couatl64_MSFS.exe, version: 4.8.0.4801, time stamp: 0x62ff6870
Exception code: 0xc0000005
Fault offset: 0x000000000019adf8
Faulting process ID: 0x38b4
Faulting application start time: 0x01d8b4b7052f1af4
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: f568474b-c3b7-4381-9e09-5eaa660bfc08
Faulting package full name:
Faulting package-relative application ID:
The DxDiag is attached to the reply.
-
I've seen increasing reports of people getting the 'ntdll.dll' error with crash without even having GSX installed some people with fs2crew, so it may be an issue with the sim not specifically GSX.
-
TBH, GSX MSFS even ruins an existing GSX for P3D installation. The whole thing is becoming a disaster.
-
Yeah probably because you have not tested it enough and released it 2 days after giving out press copies...
"Probably" not. We had TWO beta cycles:
- One started 10 days ago, with daily updates, which involved about 30 people, some for the forum, others being well known developers.
- After a week, we sent what was the daily beta to Reviewers, another 30-35 of them.
Nobody ever reported a CTD during this time. But of course, when it goes out in the wild, in the thousands of different combinations of hardware, settings and installed add-ons, you can be sure there WILL be unexpected problems.
But rest assured this is our topmost priority right now, because we obviously hate CTD as much as anybody else. We are trying to reproduce it, which is going to take some time, because we need to test MS Store SU9, MS Store SU10 Beta (last one came today), Steam SU9 and Steam SU10 Beta, and of course we should probably install lots of 3rd party add-ons as well, to put it under stress.
If we fail to reproduce any CTD, there might be another option: if some of you have a constant, easy to reproduce CTD, we can explain how to create a complete memory dump we can SEND TO ASOBO for inspection, and they can tell us exactly what is happening, and why.
-
It doesn't come from gsx a lot of people had CTDs today and yesterday and they don't have gsx look on the microsoft flight simulator forum
-
I now also had three unexplained CTDs with faulting module being the ntdll.dll since installing GSX Pro into the MSFS. Weird thing is that they seem to be happen totally at random, one happened at the Gate while loading the 737-700, the next happened also with 737 but this time in cruise somewhere above eastern France. And now the last crash happened while flying with the Carenado M20R over SoCal without even touching GSX during the flight.
I mean usually I wouldn't think this pointing to GSX as the culprit, but nothing else changed on my sim during the last few days and I never had any issues with CTDs before this.
Weird thing is that acutally the SU9/SU10 things seems to actually involved, since of my friends none with SU10 have any issues with CTDs while we few still on SU9 all have these issues.
-
I'm sorry to have to add to this thread but it's happening for me too flying the Fenix. Twice on descent at exactly FL100 (signficant?) and the third time at FL330 30 minutes after departure. Just to test on the third flight I had no other software running (such as FS2Crew) but I still caught the CTD. I don't think it's either 3rd party airports or a dodgy Fenix livery as I've used all of these trouble free pre-GSX Pro.
I have used GSX in P3D for many years and I really appreciate how powerful it is. It does so much and most of it totally customisable. I'm not surprised that there are some bugs. Even the powerful Microsoft and ASOBO produce software with bugs. The GSX Pro Manual is the best and most comprehensive manual for flight simulation software that I've ever seen.
Of course, I want this fixed as much as the next guy, but criticising Umberto and his team won't help at all. The software has only been on general release for 2 days so with feedback from more knowledgeable people than me I am confident that these problems will be identified and overcome.
Meanwhile I have unlinked GSX and I will patiently carry on flying until a fix is discovered.
-
It doesn't come from gsx a lot of people had CTDs today and yesterday and they don't have gsx look on the microsoft flight simulator forum
Karty3200, you need to be realistic, you do not know GSX isn't the cause. However we do not know if it is the cause.
I am the first to defend developers when they come under unneeded criticism. I must say I am not trying to attack Umberto or FSDT here, I love GSX in FSX & P3D and I will in MSFS as it is a crucial part of my entire simming experience.
There are many reports here on this forum, the Microsoft Flight Sim forums and other forums, YouTube videos and other place where CTDs have occurred coincidentally as GSX has been introduced to systems. Every report is the same; users including myself have reported a very stable sim with little to no CTDs and then as soon as we've installed GSX we are unable to complete flights without having a CTD. Then we uninstall GSX and are then able to complete the same flight but without a CTD.
It is looking very likely that GSX (maybe not directly) is causing a issue with the sim, causing CTDs. You say others are reporting CTDs without GSX, however there are many types of CTD errors, so it is very rash to say they are all connected. Also the fact that people are able to complete flights after uninstalling GSX does show that again it is likely to be at this point a error around GSX.
I do thank and commend Umberto and the team for making these CTD investigations a priority, and hopefully soon we can definitively say wether it is GSX or not and those of us that can't complete a flight with GSX involved can soon fly with it installed.
-
It doesn't come from gsx a lot of people had CTDs today and yesterday and they don't have gsx look on the microsoft flight simulator forum
Yesterday and today a massive amount of people had CTD regarding server issues with the MSFS servers.
I've done now 4 flights with the PMDG 737 and no crash.
Sometimes GSX needs two clicks to respond and of course not everything is as it should, but this is in my opinion expected for a first day software.
Cheers
Artox
-
Regarding CTD, it may just be a really bad coincidence. There have been reports of MS server issues causing problems.
Releasing GSX right at that time might just be bad luck. I had CTD yesterday. And I very rarely have CTD. So it would have been easy to blame my freshly installed GSX.
People having been blaming GSX, others FS2Crew update , then the reports of MS server issues. Then there are reports of many CTD from people who don't even have GSX installed.
Today no problems so far. Did two flights earlier (1x 2h and 1x 4.5h). Currently in my third flight and passed the 4h mark.
Still lots of bugs to iron out though, which Im sure are being worked on.
-
First of all, I would like to thank fsdt for the continuation of the excellent add-ons for MSFS, which is GSX Pro. After buying and installing it, I found a few bugs, which will be corrected with an update over time, such as passengers on a building, carts in the air before moving and so on.. but then came the main one, the CTD, mostly when the camera was moving on the ground, more often in the air. If they react to an error that can be found in the event management in Win, then yes, the same one popped up. And now we consider... In error there is nothing that reports an error on GSX, but on ntdll.dll, or MSFS as an application, see the text of the error or even on FSUIPC7.dll like me. And now a pearl of knowledge. I tried using Google Maps instead of the MSFS base map via the application Map Enhancement 5.1 or later and after completely uninstalling GSX I got the SAME ERROR on my next flight!! He also removed this application and no error popped up on the next flight? So let's summarize: Since the GSX always froze when moving the camera to complex terrain, i.e. immediately loading data into memory, when downloading large Google Maps data, it's similar to the memory, so I can think of only one thing. The problem is not necessarily in the GSX, but in MSFS, which CTDs when the memory is full or something with it. I'm using SU10 Beta. Now I'm thinking of trying to install it again without Google Maps and into a clean GSX and we'll see... if there's still a CTD, it's clear that it's a problem on the MSFS side, because the memory overflows even if you clear it beforehand, it keeps filling up, whether it's activities and everything related to GSX, or possibly uploading the Google Maps terrain, it's a huge flow of data. Nobody's perfect, maybe I'm wrong, but it's good reasoning that it is easy to immediately condemn GSX, rather than to find out the possibilities of other causes?
Errors found in GSX Pro:
1. For third-party airports, which is the vast majority, in the configuration where you have a list of Gates and stand areas, the path to the DEFAULT airport, which in AFCAD has completely different stands, is incorrectly set in the configuration where you have a list of Gates and stand areas. In FSX, I remember that the path it had to be correct on the AFCAD of a specific third-party airport and here is a question mark, which files from the addon are AFCAD file types, especially if you have an addon purchased through the Marketplace directly from MSFS. In the Official folder? I see this as a fundamental problem, why ini.cfg can't work. You have it in the Virtuali folder and yet after starting it in MSFS GSX it doesn't offer anything because you are outside?
2. CTD error see introduction..
3. Passengers do not go in the building to the Gate but above the building, before they get to the beginning of the gate from the building, it is a bug to be fixed as well as the carts when launched into the air and the staff with them, please fix.
4. When switching on GSX from the panel, there is sometimes a long delay before the function table starts up. Also a question about the upcoming update. I believe that everything can be solved, it just takes time. First, the fundamental problem and that is CTD.
To bring back a lot of users who were looking forward to it like me. We are in the same boat, this is an important addition that will take MSFS a long way!!
-
Hello, has anyone tried a roll back on Nvidia 516.59. there are many voices saying that the new 516.94 causes many problems in MSFS even without GSX
-
Hello, has anyone tried a roll back on Nvidia 516.59. there are many voices saying that the new 516.94 causes many problems in MSFS even without GSX
Ive stuck with 512.95. Updating beyond has caused CTD's for me.
-
I do thank and commend Umberto and the team for making these CTD investigations a priority, and hopefully soon we can definitively say wether it is GSX or not and those of us that can't complete a flight with GSX involved can soon fly with it installed.
I must say I was initially very worried, because we are doing so many new things and so much stuff is happening on screen, that I assumed it might have been possibly a GSX problem, although I was more inclined to think it might be caused by GSX indirectly, the real bug might have been some Simconnect function not many developers use that still need fixing.
However, after reading all those comments on the Microsoft Flight Simulator forum, there's just TOO MANY cases of users with constant CTD, sometimes only after 20-30 minutes, and NONE OF THEM HAS GSX. Some of them have it, of course, so I can fully understand why it might be easy to point fingers to GSX, because it just came out when these CTDs started but, there's just too many reports about users starting to have CTDs with NO ADDONS, or other addons, I suggest reading that thread, because it's quite interesting.
What is possibly happening, is that Microsoft is preparing the servers for the final SU10 release, so they are possibly updating files, those servers might be under stress and I'm also sure they use a big network ( Azure ) of nodes, so it takes a while for all nodes to be updated (this sounds familiar), and this might be a cause of the unusual increase of CTDs, which happened to be almost coincident with GSX's release.
We surely continue to keep an eye on this, and of course we are fully aware we have LOTS of fixes to do in the next days/weeks, but I think I'm quite positive the worse of all, CTDs, is not what I feared might be.
-
I'm using Nvidia 516.59 right now and GSX also had CTD, but see the text above... I'll see what it does without Google Maps on the next flight... and that I fly around Europe often :-)
-
I've also rolled back to 516.59, with lots of hopes, thinking that I've updated my Nvidia drivers literally the same day as I've installed GSX, and that this could have been the culprit. I was boarding at EGCC, and everything went fine. That's what I've thought ahah
MSFS crashed right after boarding completed. I almost never had a crash on the version of the driver I've rolled back on, so I'm definetly sure that GSX is involved somewhere in those CTD.
-
MSFS crashed right after boarding completed. I almost never had a crash on the version of the driver I've rolled back on, so I'm definetly sure that GSX is involved somewhere in those CTD.
I strongly suggest to read the whole thread on MS Forum, the nVidia drivers were an issue only for SOME users but, most of them had lots of crashes THESE DAYS, and many never had GSX installed, some had many add-ons, others a clean install without ANY add-on, and they all said an abnormal rate of CTD started very recently, something they never experienced before.
-
As being one of the users with constant CTD I have to take a small step onto GSX / Umbertos side. My crashes started the second I used GSX in a real flight (just ground testing and learning the UI before), as many of my friends did.
I have to be honest, what favored this assumption was Umbertos statement "It cannot be GSX" which, to be honest, was not great communication as there wasn't really time to test when this statement was made. I would've expected more of a "We're sure it is not GSX but we'll investigate". This has changed as seen above and a thumbs up from me for that.
I've read across different topics today and the sheer amount of reports let me doubt this really is caused by GSX. If it proves to be just a very awful coincidence the crashes started with the release of GSX I am really sorry for Umberto for taking all the whacks in the last hours / days.
For myself I unlinked GSX and had another crash 10 min into a flight, so I am up for any news but I won't expect them too soon as of the weekend.
GSX still has some bugs no matter the crashes, but it's nice to read that they're being addressed soon ;)
-
I'll make it easier for everybody, and will link the interesting post of the thread named "Constant CTD every flight now"
https://forums.flightsimulator.com/t/constant-ctd-every-flight-now/537543
https://forums.flightsimulator.com/t/constant-ctd-every-flight-now/537543/20
I had no issues since I bought the game but since August 16, I am experiencing CTD’s all the time. I first repaired, then reset, then uninstall and re-install, to no avail. I have only the PMDG in the Community folder and always a CTD a few minutes later during setup
https://forums.flightsimulator.com/t/constant-ctd-every-flight-now/537543/48
Did you guys all have Bought GSX PRO ?
I have not.
Nope.
Nope. I think it’s not related to GSX. Is just yet another bug in this simulator
I had it installed, after 5 consecutives CTD, I decided to uninstall it… I’m still experiencing CTD on each flight after 20-30 min…
I have not bought GSX as yet.
I have removed everything from the community folder, then repaired, then reset, then uninstall and install, and keep getting CTD in Safe Mode with no 3rd party add-ons, also with no error message. Just CTD. I’d never had any issues before, so this is baffling. My problems started on August 17
His problems started the day *before* we released gsx
https://forums.flightsimulator.com/t/constant-ctd-every-flight-now/537543/77
Since few days i can’t fly a single flight in which the sim does not crash at least once (today a flight with 4 crashes) I have a fresh install of Window 11 and MSFS without any 3rd Party addons just Windows and MSFS running.
Since two days constantly CTDs and I don’t see any pattern here why the sim is crashing. I also installed GSX Pro but the issue started already before the installation.
https://forums.flightsimulator.com/t/constant-ctd-every-flight-now/537543/142
I had 3 crashes today, first I thought it was gsx causing this but it happens even without it. All started today, yesterday 0 problems
https://forums.flightsimulator.com/t/constant-ctd-every-flight-now/537543/144
i have done a fresh install cant even install the world updates without this sim CTD
https://forums.flightsimulator.com/t/constant-ctd-every-flight-now/537543/159
nt.dll CTDs for the past few days on every flight. Win 10, 3080 Ti (tested with July and August drivers), without GSX.
https://forums.flightsimulator.com/t/constant-ctd-every-flight-now/537543/179
No GSX installed here
https://forums.flightsimulator.com/t/constant-ctd-every-flight-now/537543/181
Do you have any mods installed? If so, which one(s)? NONE as i done a fresh install so was vanilla
The topic is still going, by I believe there's enough evidence CTDs that started recently are not related to GSX.
-
There's only some anecdotal evidence about GSX being the "cause".
My $0.02
In P3D, I spent most of my free time perfecting my GSX profiles. This program was the best thing since sliced bread. Amazing work by the FSDT guys. When I started using MSFS, I quickly realized that there was in DIRE need for GSX. So, today, I bought GSX. I cannot express my excitement more. I then realized quickly that I had to destroy my P3D GSX just to get it to work. So I uninstalled it completely from P3D and installed fresh as this forum directed me to do. It was frustrating to have to constantly manually start COUATL because I often forget and have to restart AGAIN....and we ALL KNOW MSFS does NOT load quickly. So I spent a LOT of my valuable free time exiting MSFS just so I can manually start COUATL because restarting in the sim does not work at all. So, FINALLY, I was able to start trying out GSX. It's EXTREMELY well done. It helps that now I have access to a drone cam to get up close and personal to every single entity in GSX to place it perfectly. I was able to customize 2 parking spots at KDAL and 1 at TISX. HOWEVER, ....a BIG HOWEVER...... now, when I load MSFS, if I start COUATL first, it crashes to the desktop. I have NEVER had a CTD in MSFS!!!!!!! If I DON'T start COUATL, MSFS loads perfectly fine, but tells me COUATL has not started. So, the statement that 'There's only some anecdotal evidence about GSX being the "cause".' cannot be true. Guys, please, we spent good money to have this on our systems. You guys, WE KNOW, have busted your rumps to put out an amazing product. We KNOW there's gonna be bugs. However, PLEASE work diligently to fix this. We can already see that this was not tested on a system that had GSX loaded for P3D AND MSFS. There's more work to do. Also, please realize that MANY of us are loyal customers of yours. Don't leave us hanging. I know that I have pretty much every US P3D airport you created. That's a lot of dough. Many of us will download your latest airport the DAY it's released. Please help us out and fix these issues. We were waiting for this addon with bated breath.
I am not runnig SU10 beta. I have not changed anything on my system. It was working this morning after I trashed my P3d GSX. I explored MSFS GSX, then I shut down the sim to go do my "adulting" for the day, and when I cranked it back up later, .....CTD
-
Need FSUIPC7?
-
Treeb52 I don't think FSDT will leave any of us hanging. The CTD's you experienced this evening may not be GSX related. I had 4 CTD's in a row just trying to start MSFS. There's a long forum thread on the Microsoft forums of people sharing their recent experiences in the past two days or so with multiple CTDs. The majority of those responding don't own GSX for MSFS. So there is something going on with MSFS that is causing a lot of these issues and it just happens to be happening within the window of GSX being released.
-
So, the statement that 'There's only some anecdotal evidence about GSX being the "cause".' cannot be true.
I understand you were replying to my initial post, one before we could gather enough proof but, haven't you read the post just before yours, which is a collection of a very long thread on Microsoft forum, which confirm PRECISELY that all the assumptions made about GSX were exactly that, anecdotal evidence.
That post is more a way to summarize the thread and isolate the most tell-telling sentences, to make it easier to form a picture, it doesn't include much opinions, it's a link of what other users experienced, not what I think. If if YOUR experience might haven been leading to the conclusion "it was GSX", putting together additional information will help you reaching a more informed opinion, that's why it's called like that: you need as much *information* as possible to form an "informed opinion", if you are using only your own single experience, it's easy to fall into the trap of confusing correlation with causation.
-
So, the statement that 'There's only some anecdotal evidence about GSX being the "cause".' cannot be true.
I understand you were replying to my initial post, one before we could gather enough proof but, haven't you read the post just before yours, which is a collection of a very long thread on Microsoft forum, which confirm PRECISELY that all the assumptions made about GSX were exactly that, anecdotal evidence.
That post is more a way to summarize the thread and isolate the most tell-telling sentences, to make it easier to form a picture, it doesn't include much opinions, it's a link of what other users experienced, not what I think. If if YOUR experience might haven been leading to the conclusion "it was GSX", putting together additional information will help you reaching a more informed opinion, that's why it's called like that: you need as much *information* as possible to form an "informed opinion", if you are using only your own single experience, it's easy to fall into the trap of confusing correlation with causation.
GSX PRO needs FSUIPC7?
-
Need FSUIPC7?
It's not listed as a system requirement, so I doubt it requires FSUIPC7. However, there are plenty of other utilities you may encounter that will require it. The basic FSUIPC7 is free to use. The paid version unlocks other features which may or may not be useful to you.
-
GSX PRO needs FSUIPC7?
No, it doesn't. It might still be useful for GSX usage, not because GSX would use it, but you could write LUA scripts to interact with GSX variables.
But if the reason of your question was because you think FSUIPC7 might be the cause of CTDs, I don't think it is, based on multiple evidence of may users with *no add-ons* installed still getting lots of CTDs.
-
I don't think it's GSX. I think it's COUATL. The only thing I can form opinions on are my own experiences. In my experience, I have never had CTDs in MSFS. I got GSX to work for a little while (which I loved), but now, after changing nothing, I cannot load a flight without a CTD if I load COUATL before launching MSFS, which is the only way I was able to utilize GSX in MSFS. It's just data. Please use it for the next update. You guys are amazing. Your ability to write code is without peer. Keep going! The PMDG guys realize this. Simmers all have different rigs with different configs. You're realizing quickly that many simmers want to keep P3D because they've (we've) invested hundreds, if not thousands, in addons. MSFS is and/or will be the same. You have a product that almost EVERY MSFS simmer SHOULD have. It needs to be flexible. It's gonna get worse before it gets better, but please listen to us and don't chalk it up as anecdotal evidence. Your products will get dismissed quite quickly. Hardcore simmers feed on forums to solve problems. We're smart. We take hundreds of forum inputs to solve problems specific and unique to our own problems. Keep this going, brother. Your company is one of the most amazing simming companies out there. Make this GSX as stable as your P3D version. Accept the challenge
-
I don't think it's GSX. I think it's COUATL. The only thing I can form opinions on are my own experiences.
And that's why you are wrong because, this is not politics, where you have the right of forming your own opinion, based on any criteria you decide, no matter how absurd it might look to others.
Computer science is called like this FOR A REASON, because something is either true for all or false for all, you can start by forming your own opinion but, as with science (again, I.T. IS science), you must be prepared to CONFRONT your own experience with reports from others because, by keep saying you "think it's Couatl" just because it seems to happening TO YOU, it doesn't mean it is the real "cause" of the problem, because other evidence gathered from a larger sample, other users, suggests the only common pattern here is we are in a "CTD week", which seem to have started slightly BEFORE GSX came out, which lead many to initially assume it has something to do with GSX, but clearly is not, because we have overwhelming reports that it can happen to anybody, with or without any add-ons.
-
I don't think it's GSX. I think it's COUATL. The only thing I can form opinions on are my own experiences.
And that's why you are wrong because, this is not politics, where you have the right of forming your own opinion, based on any criteria you decide, no matter how absurd it might look to others.
Computer science is called like this FOR A REASON, because something is either true for all or false for all, you can start by forming your own opinion but, as with science (again, I.T. IS science), you must be prepared to CONFRONT your own experience with reports from others because, by keep saying you "think it's Couatl" just because it seems to happening TO YOU, it doesn't mean it is the real "cause" of the problem, because other evidence gathered from a larger sample, other users, suggests the only common pattern here is we are in a "CTD week", which seem to have started slightly BEFORE GSX came out, which lead many to initially assume it has something to do with GSX, but clearly is not, because we have overwhelming reports that it can happen to anybody, with or without any add-ons.
I have to agree with Umberto that the CTD problem may be related, paradoxically, to a problem that started to occur with the GSX released at the same time.For Example: Maps Enhancement: it changes the landscape into I can say better maps. I was interested and tried it. FPS went down slightly but no crashes. Suddenly GSX was released. I'll try. It showed a crash on the ground and in the air when using the view either at the airport terminal or in flight. Specifically, see the ntdll.dll and MSFS.exe or FSUIPC7.dll tables above. Fine, I'll join the line of complainers that I have CTD almost every flight. But... and now watch out! after completely uninstalling GSX, Maps Enhancement still remains. On the very next flight, AGAIN THE SAME ntdll.dll error message and other things he wrote. Why if suddenly I no longer use GSX in MSFS?? Fine, I'll put the maps away and use the classic DEFAULT MSFS. So I'll take another flight. Wow, increased FPS, I'll fly out of the airport, I'll do a lot of looking at the landscape like before and the crash is nowhere? Ok, I'll take off into the clouds and into a high flight level. I'll give storm clouds and I'm still wondering when the CTD will happen. I'm at 35000ft, I've been flying for about an hour, around beautiful dense clouds, it's flying at 45 FPS / used to be around 25 /, I'm changing views which have had freezes and crashes and CTD nowhere??? I don't know... it seems to me that rather a paradoxical situation has occurred, that CTD occurs precisely with the release of GSX due to possible other things connected with MSFS itself, but the finger is immediately pointed at GSX because, for example, something broke remotely in MSFS at that time, which causes CTD, but a lot of people just bought and started testing GSX at that time and now, perhaps quite innocently, they mistake it for another problem in MSFS, that it is to blame. I don't think 100% because I personally wouldn't have those crashes with the same message when using Maps Enhancement even though GSX was gone completely. Weird right?
-
I'm getting CTD when trying to load into a flight, this is my 5th attempt now and no success. I haven't added anything new to the Sim except for GSX.
-
So after doing some reading, I am more leaning towards it being a MSFS issue and it's the worlds biggest coincidence that has unfortunately led me and others to pointing the finger at GSX, sorry Umberto, hopefully whatever it is can be sorted and that we're all back to flying soon
-
I just performed 4 different tests the first:
- a flight between brussels and corfu with gsx and online service = CTD
- Same flight without gsx and online service = CTD
- Same flight with GSX and offline service = NO CTD
- I then returned to corfu - brussels with gsx and offline service = NO CTD
So this is not a gsx problem but a microsoft problem.
I apologize for pointing fingers at you Umberto
-
What do you mean with online service?.. GSX was the only change to my setup (also no Update to Nvidia or Windows) and suddenly every flight I attempt ends in a crash. Sometimes it happens during boarding, sometimes it happens two hours into the flight. Uninstalled GSX and haven't had a crash since.
If the error is not corrected I would like my money back
-
I can confirm that before loading into a flight I turned all online services off in the sim and loaded succesfully into the sim, once I was in I just turned them all back on again.
I don't believe this to be a GSX issue at all.
-
I also read that there were server problems. This is stupidly coincided with the GSX Pro release.
Sure it still has some bugs, but hey what program is perfect from the start. I look forward to further updates
-
I really think Umberto and GSX got unfair publicity sofar. For me it started with the Youtube item from 737NG driver, when he explained why he uninstalled it. I generally like his clips and value his opinion, but in this case he was too quick to jump to conclusions and all of a sudden everyone is all over GSX with uncollaborated stories. I find that sad.
Besides the CTD's he also mentions all kind of things that go wrong, but - in my opinion - are easily fixed when you make your own config.
I think the lesson should be to be careful when making statements like this before you have tested it and ruled out other possibilities
-
I really think Umberto and GSX got unfair publicity sofar. For me it started with the Youtube item from 737NG driver, when he explained why he uninstalled it. I generally like his clips and value his opinion, but in this case he was too quick to jump to conclusions and all of a sudden everyone is all over GSX with uncollaborated stories. I find that sad.
Besides the CTD's he also mentions all kind of things that go wrong, but - in my opinion - are easily fixed when you make your own config.
I think the lesson should be to be careful when making statements like this before you have tested it and ruled out other possibilities
I completely agree with you Isaiah, gsx just had no luck, but I find the product incredible with a few small bugs that don't bother me. (GSX is considered too realistic for some youtubers). I am sure that with the weeks to come the product will be at the top
-
I really think Umberto and GSX got unfair publicity sofar. For me it started with the Youtube item from 737NG driver, when he explained why he uninstalled it. I generally like his clips and value his opinion, but in this case he was too quick to jump to conclusions and all of a sudden everyone is all over GSX with uncollaborated stories. I find that sad.
Besides the CTD's he also mentions all kind of things that go wrong, but - in my opinion - are easily fixed when you make your own config.
I think the lesson should be to be careful when making statements like this before you have tested it and ruled out other possibilities
Well most of us thought it is linked to GSX as it started with GSX. Emanuel just made a video of it (which has been updated meanwhile) and pointed out some flaws. Yes they can be fixed but they're still flaws and easily noticeable without hours of testing.
There are several things you just cannot fix with configs, e.g. the wrong position of the wing walker after disconnecting, slow procedures connecting and disconnecting the Tug or the menu disappearing all the time. For the pax I noticed that they spawn in the jetway so if they're above it it is either a problem in the scenery or GSX not processing the data right. The pax path can only be set in the static part of the jetway as you cannot edit it as long as the jetway is connected and thus cannot know where exactly the jetway will be if you try to set it without the jetway being connected.
So yeah those are bugs I'm sure will get sorted out but imho it's valid to point them out.
-
It is ''the most of us thought'' I have a problem with. You have to be sure, and to be sure you need to know - and test - what goes wrong. On assumption judging something is unfair and harmful (in this case for Umberto) The other issues you mention I agree, you can point it out, but the backlash from a clip like Emanuel did was not in proportion to the issues. Some reaction were that it is a scam etc. That goes way beyond what is reasonable and is not reflecting reality.
facts not assumptions. But let's get back to topic. I think we have a great community and solutions will be found
-
this is my last CTD .I departed in EPKK Aircraft Fenix A320, after departure crossing level 150 i got CTD with this info(sorry its in german,you can use Deepl translate)
-
this is my last CTD .I departed in EPKK Aircraft Fenix A320, after departure crossing level 150 i got CTD with this info(sorry its in german,you can use Deepl translate)
Not sure why you are posting here, when it has been cleared by now those CTDs are caused by some server issues on Microsoft. At FL150, GSX is not even active.
Try to disable Online Service in MSFS, and see if the crashes stops. That will indicate you the problem is on MSFS own servers.
-
I must apologise Umberto, I tried my first flight since Friday, and it CTD'd 8 hours into a 9 hour flight, different error report to Friday.
It is a sim issue now as far as I am concerned, hopefully Asobo sort it out soon. Just very unfortunate timing for GSX
-
I must apologise Umberto, I tried my first flight since Friday, and it CTD'd 8 hours into a 9 hour flight, different error report to Friday.
It is a sim issue now as far as I am concerned, hopefully Asobo sort it out soon. Just very unfortunate timing for GSX
Exactly what I said. Unfortunately, something remotely went wrong in MSFS and the GSX was just released, of course a lot of people bought and tried it... and CTD... and immediately points the finger at someone who has a lot of credit for MSFS it looked even better and with life around... It's not an easy job and I thank the creator, because for the stupid timing with some error in MSFS, it seems that GSX is to blame for everything. The stupid beginning will gradually be resolved and GSX will be an integral part of MSFS. By the way, I got the same error and CTD in the Menu when zooming in on the map, GSX was not running. It's easy to criticize something, but it's also nice to appreciate it even if the interplay of events didn't exactly favor it.
-
CTD=MSFS servers well that’s a game changer Umberto for sure.
-
Hi Umberto,
First time today experiencing an issue with MSFS in a long time after an install of GSX. I didn't CTD, but COAUTL essentially crashed when I was loading my charts in the Navigraph in-game panel. My sim froze and became unresponsive, but it did not CTD. I could not exit it and had to close the application via task manager. Here are my specs and what I was using at the time along with my .err file:
R7 5800x
RTX 3080TI
64GB Ram @ 3600MHZ
1 TB SSD
Nvdia Driver: 516.94
Windows 11 21H2
Windows OS Build 22000.856
Running Sim Update 9
Drzewiecki Design MDW
FSUIPC 7.3.7
PACX
Navigraph In Game Panel
Honeycomb Alpha and Bravo
Thrustmaster Airbus Side Stick
Thrustmaster T Flight Rudder Pedals
PMDG 737-700
Description
Faulting Application Path: C:\Program Files (x86)\Addon Manager\couatl64\Couatl64_MSFS.exe
Problem signature
Problem Event Name: APPCRASH
Application Name: Couatl64_MSFS.exe
Application Version: 4.8.0.4801
Application Timestamp: 62ff6870
Fault Module Name: Couatl64_MSFS.exe
Fault Module Version: 4.8.0.4801
Fault Module Timestamp: 62ff6870
Exception Code: c0000005
Exception Offset: 000000000019adf8
OS Version: 10.0.22000.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 9f2f
Additional Information 2: 9f2f74b570935a1285a45de585f01fd5
Additional Information 3: ffdd
Additional Information 4: ffdd49f9f9f19d2e7a692374de1e85ca
Extra information about the problem
Bucket ID: 01696e89afa5156bc5624467875996e0 (1540869233957246688)
-
I didn't CTD, but COAUTL essentially crashed when I was loading my charts in the Navigraph in-game panel.
Well, at least that tells us Couatl really can't crash the sim, even when it goes into panic.
This is of course worth investigating, possibly in another thread, because this discusses CTDs of the simulator, which were initially suspected to be caused by GSX, but now it seems they aren't.
-
I didn't CTD, but COAUTL essentially crashed when I was loading my charts in the Navigraph in-game panel.
Well, at least that tells us Couatl really can't crash the sim, even when it goes into panic.
Correct, it didn’t crash to desktop, but it did render the simulator unresponsive and unrecoverable. Feel free to split it Into a new thread as needed. Thanks!
-
Correct, it didn’t crash to desktop, but it did render the simulator unresponsive and unrecoverable.
Sorry, I understood the sim was unresponsive for a brief moment until you terminated Couatl, but then recovered. That was strange, and that's why I initially said it would be worth investigating, now I fully understood what really happen, then no, what you saw wasn't Couatl making the sim unresponsive, it was the sim that crashed for all the reasons that has been discussed in this thread, that seem to have found an agreement the sim IS unstable these days because of server issues over Microsoft.
Because of this, Couatl crashed, the same made it crash, not vice-versa.
The common pattern that seems to emerge is, it's a problem of the MSFS servers, because it seems that almost everybody who had continues CTDs these days, fixed them immediately by switching off the online services in MSFS. And keeping GSX, of course.
-
It is ''the most of us thought'' I have a problem with. You have to be sure, and to be sure you need to know - and test - what goes wrong. On assumption judging something is unfair and harmful (in this case for Umberto) The other issues you mention I agree, you can point it out, but the backlash from a clip like Emanuel did was not in proportion to the issues. Some reaction were that it is a scam etc. That goes way beyond what is reasonable and is not reflecting reality.
facts not assumptions. But let's get back to topic. I think we have a great community and solutions will be found
Well the others sticked to the argument that it cannot be GSX which was also a statement nobody could be sure of as there was no evidence for it. Now we can be more sure that it is probably only connected to Asobo, but we cannot be sure about that either because first they have to sort out their problems for us to be able to test GSX again.
It looks like many viewers didn't watch both of Emanuels videos or in its entirety as he mentioned he only uninstalled it because of the crashes. Still it's a valid assumption as the crashes started with the release of GSX for the users. Usually this points to a problem with an addon if before there were no problems. It's super unlucky timing for Umberto and I too feel sorry for that but I cannot really blame anyone as this was the only "evidence" we had at that time. As there is no logging in MSFS you cannot have 100% solid proof if it was A or B. Some of the backlash was also linked to the flaws present, but Emanuel himself said that those were minor and not a big problem. It's on the viewers if they overinterpret, this is also unfair in Emanuels direction. Some did tests and they didn't have crashes after uninstalling GSX. Also pure luck as they still were present, but this strengthened the assumption it had to be linked to GSX in some way.
So overall it was just a horrible coincidence and all of us who read the different topics about it (or watched Emanuels corrected video) know that there's something else going on by now.
-
I had very rare CTDs before using GSX. I bought it on Friday and had a series of CTDs. I unlinked GSX from my community folder and had no more CTDs. On Sunday I wanted to give it another try and relinked it to my community folder. Guess what: I had CTDs :(
It's for sure there are CTDs caused by the sim itself, but at least on my side there is a tendency, that GSX is involved as well.
-
I had very rare CTDs before using GSX. I bought it on Friday and had a series of CTDs. I unlinked GSX from my community folder and had no more CTDs. On Sunday I wanted to give it another try and relinked it to my community folder. Guess what: I had CTDs :(
It's for sure there are CTDs caused by the sim itself, but at least on my side there is a tendency, that GSX is involved as well.
I agree.... when GSX installed.... instant and quick CTD mid-air ; without GSX no CTD .... its related to gsx in a way ....
EDIT:
I tried deactivating latinvfr AREX Airport Regional Environment X Global & ambitious pushback toolbar ..... no ctd during the test flight which ctd each time before.
-
Hi,
same observation for me. It has def not todo with online/offline or server state. This morning I tried three times a flight VHHX-RJTT with GSX linked but even not in use. Three times CTDs after a few minutes in flight. Unlinkend GSX by removing the links out of the comm folder cause Installer even did not unlink and doing the same flight without problems now. I know Umberto you said already quite a few times that this is highly unrealistic but there seems to be a link between GSX and the CTDs. I'm on SU10 Beta btw. Otherwise I'm CTD free. Sadly there were at least no outputs in the event log on my side this morning. But thats nothing new either with CTDs of MSFS.
Cheers
T.
-
Here's what the MSFS Forum Community Manager wrote:
Summarizing all the data I’ve collected from this thread so far:
This specific CTD is only affecting PC players (both MS Store and Steam). Xbox and Xbox Cloud Gaming players are NOT impacted.
Only some, not all, PC players are getting this CTD.
This specific CTD starting occurring on or about Friday, August 19.
It is affecting players with both Nvidia and AMD GPUs. Driver version does not seem to matter.
Sta interessando i giocatori sia sulla build live SU9 che sulla build beta SU10.
Sta interessando i giocatori sia su Windows 10 che su Windows 11.
It is likely (unconfirmed) related to online services such as Live Weather, Live Traffic, and Azure terrain caching.
Ultimately it would seem that the problem concerns only the European servers.
-
So,
as i wrote above i deactivated latinvfr AREX Airport Regional Environment X Global & ambitious pushback toolbar.
For now, im on my 5th leg without restarting msfs (so also no ctd).
I would say: The CTD are related to GSX, but the problem is that only one Ground Handling Addon (or related to airport vehicles etc) should be active within msfs. So GSX is running fine for now.
-
So,
as i wrote above i deactivated latinvfr AREX Airport Regional Environment X Global & ambitious pushback toolbar.
For now, im on my 5th leg without restarting msfs (so also no ctd ; ... just to be sure you understand ;).
I would say: The CTD are related to GSX, but the problem is that only one Ground Handling Addon (or related to airport vehicles etc) should be active within msfs. So GSX is running fine for now.
-
So,
as i wrote above i deactivated latinvfr AREX Airport Regional Environment X Global & ambitious pushback toolbar.
For now, im on my 5th leg without restarting msfs (so also no ctd).
I would say: The CTD are related to GSX, but the problem is that only one Ground Handling Addon (or related to airport vehicles etc) should be active within msfs. So GSX is running fine for now.
Strangely enough i had several flights WITHOUT any issues (no CTDs). Today i added LVFR AREX Europe and got my first CTD inflight. Sim simply quit, no messages ...
Oliver
-
Hi everyone,
I purchased GSX Pro last Friday and since I installed it I have been experiencing random CTD. Yesterday I uninstalled it and everything works fine again, without any CTD. I think is quite clear where the CTD are coming from. I hope a coming update to fix it.
I'm using SU10 beta.
-
I purchased GSX Pro last Friday and since I installed it I have been experiencing random CTD. Yesterday I uninstalled it and everything works fine again, without any CTD. I think is quite clear where the CTD are coming from. I hope a coming update to fix it.
I would suggest reading this whole thread again, from the start. It has been confirmed by multiple source, GSX doesn't have anything to with this, because far too many people that don't have and never had GSX installed ( not here, of course, on Microsoft forums ), started to have CTD with an abnormal frequency.
The thread on Microsoft how has more than 1000 posts and MOST of the users there not only DO NOT HAVE GSX, there are many without ANY add-ons!
If you don't believe me, have a look at this from Microsoft Community manager:
https://forums.flightsimulator.com/t/constant-ctd-every-flight-now-ntdll-dll/537543/618
Let's put together what Microsoft says:
This specific CTD starting occurring on or about Friday, August 19.
And what YOU wrote:
I purchased GSX Pro last Friday and since I installed it I have been experiencing random CTD.
So, it's abundantly clear by now, that GSX doesn't have anything to do with this, it just was an incredibly unfortunate coincidence it started to happen on GSX release day
-
@Hanson,
same here, over 80 flight´s on VA, no CTD,
i´m install Saturday GSX pro and 3 of 5 flight´s CTD...
yesterday i deinstall GSX pro and 3 flight´s no CTD...
so, on my PC 100% crashed GSXpro my MFSF....sorry virtuali, that´s the truth´s...
no beta installed...
-
so, on my PC 100% crashed GSXpro my MFSF....sorry virtuali, that´s the truth´s...
Don't you even realize that, CTD happens at random, so your truth is completely coincidental ? Why you don't try something else, instead, like turning off online data, for example.
But don't worry, you don't have to believe me, just wait until Microsoft will fix that, and this will all stop.
-
@Hanson,
same here, over 80 flight´s on VA, no CTD,
i´m install Saturday GSX pro and 3 of 5 flight´s CTD...
yesterday i deinstall GSX pro and 3 flight´s no CTD...
so, on my PC 100% crashed GSXpro my MFSF....sorry virtuali, that´s the truth´s...
no beta installed...
I think you're just unlucky I made I think a total of 10 flights with gsx and offline services and I got 0 CTD, I tried a few minutes ago to turn the services back on j I got a ctd, maybe by chance I tried again with the online services and after 3 minutes I got CTD
-
so, on my PC 100% crashed GSXpro my MFSF....sorry virtuali, that´s the truth´s...
Don't you even realize that, CTD happens at random, so your truth is completely coincidental ? Why you don't try something else, instead, like turning off online data, for example.
But don't worry, you don't have to believe me, just wait until Microsoft will fix that, and this will all stop.
What do you mean with turning off all online data? Live weather, photogrametry and Bing terrain data?
-
What do you mean with turning off all online data? Live weather, photogrametry and Bing terrain data?
Exactly, the sim won't look very good, but it will work, and you'll have proof it's not GSX, but something on MSFS servers.
-
What do you mean with turning off all online data? Live weather, photogrametry and Bing terrain data?
Exactly, the sim won't look very good, but it will work, and you'll have proof it's not GSX, but something on MSFS servers.
Thank you!
-
If offline services, including Bing World Graphic, will be turned off, trees will be planted on the apron of the airport, the entire airport will be covered with trees like at ORBX Prague Airport, so only with Bing turned on and then can I expect CTD? Great, so because of the MSFS problem and online services, MSFS is unusable
https://forum-static.cdn.orbxdirect.com/monthly_2022_02/1436348132_LKPRtrees.jpg.693909bdc3cbd3c747c8bae53a90b138.jpg (https://forum-static.cdn.orbxdirect.com/monthly_2022_02/1436348132_LKPRtrees.jpg.693909bdc3cbd3c747c8bae53a90b138.jpg)
-
And what this has anything to do with GSX ?
If there wasn't a problem with MSFS servers, there wouldn't be any crash, hence no need to disable online services to begin with.
-
And what this has anything to do with GSX ?
If there wasn't a problem with MSFS servers, there wouldn't be any crash, hence no need to disable online services to begin with.
Unfortunately, it's currently a problem to have services turned on and use GSX, so when it's written everywhere that online services need to be turned off to prevent crashes, I'm just showing what they did to the airport. That's why I'm not saying it's GSX's fault!! It's the fault of MSFS, which completely crashed the simulator.
I didn't write anything about GSX in the picture, unfortunately this outage caused GSX problems and that's what it's about. Asobo Studios should solve it as soon as possible because CTD is with a lot of their users with purchased MSFS /specifically in Europe on servers, in the USA it seems to work/
btw.I apologize again, I should have put a link to an image, not a large image on a large surface, sorry and thank you for the edit.
-
So today, after 2 flights, I successfully did not have CTD and GSX run all the time, I mean Coatl. So in conclusion: The crashes are caused by online services, Live weather, photogrammetry was turned off during the flight. Bing terrain data must be turned on so that there are no trees on the apron, tried and with this no crash. So either Live weather or photogrammetry = CTD, not GSX!!
So a lot of people unjustifiably point the finger at Virtuali, on the contrary, it works /GSX/. And I can thank Virtuali for a job well done, similar to the drives for GSX and Level 2 purchases for FSX. Thumbs up!!
-
So either Live weather or photogrammetry = CTD, not GSX!!
We have already gather so much evidence that there wasn't any doubt about this. The only issue left here to discuss is convincing users to TRY for themselves, to be convinced.
I read some comments online that, some of those YouTubers that initially suspected GSX was the cause of the CTD, and then had to post retraction videos when overwhelming evidence of the contrary started to come out, has been "paid" or "forced" by us to post a retraction! This shows how much is wrong in today's world.
I wonder what will happen when Microsoft will eventually fix the problem...
-
So either Live weather or photogrammetry = CTD, not GSX!!
We have already gather so much evidence that there wasn't any doubt about this. The only issue left here to discuss is convincing users to TRY for themselves, to be convinced.
I read some comments online that, some of those YouTubers that initially suspected GSX was the cause of the CTD, and then had to post retraction videos when overwhelming evidence of the contrary started to come out, has been "paid" or "forced" by us to post a retraction! This shows how much is wrong in today's world.
I wonder what will happen when Microsoft will eventually fix the problem...
I'm also curious how many users will then take it back and make excuses. As I wrote in the text, I appreciate your work /Virtuali/ and thank you for the excellent part of MSFS that gave it a completely different flavor.Unfortunately, it's just a poorly timed release with MSFS problems, but that's a fate that sometimes won't be affected.
-
So either Live weather or photogrammetry = CTD, not GSX!!
We have already gather so much evidence that there wasn't any doubt about this. The only issue left here to discuss is convincing users to TRY for themselves, to be convinced.
I read some comments online that, some of those YouTubers that initially suspected GSX was the cause of the CTD, and then had to post retraction videos when overwhelming evidence of the contrary started to come out, has been "paid" or "forced" by us to post a retraction! This shows how much is wrong in today's world.
I wonder what will happen when Microsoft will eventually fix the problem...
You just had bad luck, you released it at the wrong time, I find that MSFS customers are extremely demanding, I think they don't realize the work to make such an addon. I watched avgeek's stream and messaged him to turn off online data and everything worked perfectly as for everyone now we all know it's not from gsx
-
So either Live weather or photogrammetry = CTD, not GSX!!
We have already gather so much evidence that there wasn't any doubt about this. The only issue left here to discuss is convincing users to TRY for themselves, to be convinced.
I read some comments online that, some of those YouTubers that initially suspected GSX was the cause of the CTD, and then had to post retraction videos when overwhelming evidence of the contrary started to come out, has been "paid" or "forced" by us to post a retraction! This shows how much is wrong in today's world.
I wonder what will happen when Microsoft will eventually fix the problem...
You just had bad luck, you released it at the wrong time, I find that MSFS customers are extremely demanding, I think they don't realize the work to make such an addon. I watched avgeek's stream and messaged him to turn off online data and everything worked perfectly as for everyone now we all know it's not from gsx
I agree, but unfortunately not everyone saw through it.