FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: p3dx3 on September 04, 2016, 08:22:49 pm
-
Tropicalsim MDPC 2016 in FSX Steam. DX9. I cannot find any logs telling me what happened. After landing, I opened the GSX menu, selected my gate, Gate 11, selected Swissport, and FSX hard froze, I could hear the sound running in the back ground but the picture was frozen. I could not close FSX I had to restart my computer. There were no log entries in the Windows Error Reporting tool. I loaded up after rebooting, and sat at the gate, requested services, and did not get a freeze. Any ideas what happened? I do not have a prompt to update GSX but will download the newest installer again anyway, I last ran the installer 2 days ago or so. Thank you.
-
Tropicalsim MDPC 2016 in FSX Steam. DX9. I cannot find any logs telling me what happened. After landing, I opened the GSX menu, selected my gate, Gate 11, selected Swissport, and FSX hard froze, I could hear the sound running in the back ground but the picture was frozen. I could not close FSX I had to restart my computer. There were no log entries in the Windows Error Reporting tool. I loaded up after rebooting, and sat at the gate, requested services, and did not get a freeze. Any ideas what happened? I do not have a prompt to update GSX but will download the newest installer again anyway, I last ran the installer 2 days ago or so. Thank you.
I have the same thing in USSS P3D GSX(latest) Somebody have any suggestions
-
Since GSX cannot obviously freeze FSX, since it's running entirely outside of it (under the Couatl interpreter), the only possible reason is that, an object created by FSX on behalf of GSX, is making the sim crash, most likely because you have a video driver or a video settings problem or even an audio driver problem.
To fix a video driver problem:
- Be sure your video driver is updated
- Set your video driver to default settings.
To fix a problem with FSX settings and tweaks:
- Remove the %APPDATA%\Microsoft\FSX\FSX.CFG file, so FSX will create a new one with all default settings on the next restart.
-
I have had similar to this, screen froze but sounds still playing and FSX non responsive, but it turned out to be a coincidence. It was an OOM. hit Ctrl+Shft+ENTER to get out of FSX and OOM message reveals itself. This may be your problem, just an idea.
-
It is a new install, and if it was a driver or oom problem it would show up in the logs somewhere like Windows Error Reporting.
-
It is a new install, and if it was a driver or oom problem it would show up in the logs somewhere like Windows Error Reporting.
No, it's exactly the opposite. If it's a driver issue, since drivers runs with a permission level higher than anything else, they are able to freeze Windows even BEFORE it has a chance to log an error Event.
I'll repeat it again: GSX, by itself, CANNOT FREEZE FSX, it's theoretically impossible, since it runs entirely external to it, there's no way for GSX to access the FSX process.
An OBJECT created by the sim, on behalf of GSX, could freeze the Sim or even the whole Windows, but not because the object is "bad", only because there's a problem with a video driver setting or tweak, or an FSX setting or tweak, which is causing a problem TO the video driver, which is the ONLY thing that can crash FSX or Windows.
A SOUND created by GSX, could also freeze the Sim or even the whole Windows, but not because the sound is "bad", only because there's a problem with the AUDIO driver, which is the ONLY (it's a driver) thing that can also crash FSX or Windows.
I'll repeat it again, since you haven't said you ever TRIED to do what I suggested:
To fix a video driver problem:
- Be sure your video driver is updated
- Set your video driver to default settings.
To fix a problem with FSX settings and tweaks:
- Remove the %APPDATA%\Microsoft\FSX\FSX.CFG file, so FSX will create a new one with all default settings on the next restart.
Don't touch anything, and try the same airport and the same gate, using a DEFAULT airplane so, at least, we might be reasonably sure it's not a memory-hungry airplane that is OOM-ing the sim.
-
It was fine when sitting at the gate, it only froze when taxing from the runway to the stand and on the taxiway selecting gsx and the gate I wanted. You are far more knowledgable than me, but if it was a hard freeze of the whole system yes, it would not log. But I could hear fsx in the back ground, and I could alt tab, and ctrl+alt+del and select task manager. So windows was still operating and it would have logged any errors.
This is a new fsx:steam install with little addons, and the only tweaks are basic affinity mask nothing else.
-
But I could hear fsx in the back ground, and I could alt tab, and ctrl+alt+del and select task manager. So windows was still operating and it would have logged any errors.
That means Windows itself didn't crashed. I replied based on your report that you had turn off Windows. You could probably terminate FSX instead.
But that doesn't change the issue: even if Windows didn't entirely crash, you cannot assume the error reporting system would still work. Fact that it didn't, further indicates the problem happened inside the only thing in your system that has an higher priority of a Windows Service ( the Windows error log it's a Windows *service* ), which is a DRIVER, either video or audio.
This is a new fsx:steam install with little addons, and the only tweaks are basic affinity mask nothing else.
That doesn't mean anything. You still haven't said if you have tried the two fixes I proposed: set the video driver to default, and reset the FSX.CFG without ANY tweaks.
-
I needed to hard reset the computer because the fsx screen stayed frozen but I could hear sound. I couldn't force close it.
I have a fresh fsx config file it is a new install.
-
I needed to hard reset the computer because the fsx screen stayed frozen but I could hear sound. I couldn't force close it.
I already explained in my previous post that this doesn't mean anything, it could STILL be a driver issue, even if there was no blue screen.
I have a fresh fsx config file it is a new install.
Then it means, in your case, you would instead need a tweak. However, is not very clear from your message if:
- It happened ONCE
OR
- It happens 100% of the time with GSX on that airport ONLY
OR
- It always happens, on any airport, when you call GSX
-
It now happened again. Landing at Tropicalsim TNCA. Taxi off the active, open up GSX, select my gate, gate 7, and the FSX screen freezes. I am flying the FSLabs if that helps. If there was a driver issue, Windows would log that. Because only FSX froze, not the whole system. I could not close the FSX application so I had to restart from the task manager window.
The new changes to GSX is freezing my system. I'll enable logging in GSX to see if any cause can be found.
-
That was bizarre. Restarted computer. Started Steam, then ASN, then FSX.
Loaded default Trike at TNCA Gate 7, Tropicalsim 2012 scenery.
Go to the GSX menu so I can enable logging, and FSX crashes.
These 2 dll errors are in the Windows log
Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: d3d9.dll, version: 10.0.14393.0, time stamp: 0x57898e34
Exception code: 0xc0000005
Fault offset: 0x000daf93
Faulting process id: 0x764
Faulting application start time: 0x01d209f168986a2b
Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\Windows\SYSTEM32\d3d9.dll
Report Id: 6cb4e6e1-865c-4daf-acd2-8e6e32d0d807
Faulting package full name:
Faulting package-relative application ID:
Faulting application name: couatl.exe, version: 3.1.0.3536, time stamp: 0x57bf02a2
Faulting module name: ntdll.dll, version: 10.0.14393.103, time stamp: 0x57b7e09e
Exception code: 0xc0000374
Fault offset: 0x000d9841
Faulting process id: 0x160
Faulting application start time: 0x01d209f177f69cc4
Faulting application path: D:\Steam\steamapps\common\FSX\fsdreamteam\couatl\couatl.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: d148f306-0918-4483-b872-e71841b6b442
Faulting package full name:
Faulting package-relative application ID:
-
Crash every time I go to the in game GSX settings menu. I downloaded the latest GSX installer to be sure I was on the latest version. SODE installed okay. No exe or dll xml issues. Very bizarre.
I was in windowed mode and this is my screen right after it tries to open the gsx settings menu
http://i.imgur.com/WsGdvfV.jpg (http://i.imgur.com/WsGdvfV.jpg)
I can provide any info you need to trace this problem and see if it is my computer or GSX. I have a new install on a new hard drive of FSX Steam. in Win10 Pro Anniversary Edition. Latest updates for all including latest whql Nvidia drivers.
-
Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: d3d9.dll, version: 10.0.14393.0, time stamp: 0x57898e34
This clearly indicates the problem is a video driver problem. We cannot obviously have any effect on DirectX, since the only thing that GSX does, is to ASK Simconnect to create objects on its behalf.
Faulting application name: couatl.exe, version: 3.1.0.3536, time stamp: 0x57bf02a2
Faulting module name: ntdll.dll, version: 10.0.14393.103, time stamp: 0x57b7e09e
This indicates that Couatl.exe has crashed BECAUSE FSX crashed first. It's the effect, not the cause. If FSX crashes abruptly, Couatl cannot receive the message from Simconnect that is supposed to close, so it cannot do some clean up of its allocated resources, resulting in this crash. But the cause is the first (VIDEO-related) crash that happened in FSX, not Couatl, which is only the victim of that crash.
You still haven't replied to my last question:
- It happened ONCE
OR
- It happens 100% of the time with GSX on that airport ONLY
OR
- It always happens, on any airport, when you call GSX
-
I said the crash requesting airport services on landing happened once, then it happened again at a second airport.
The crash of fsx trying to edit gsx settings happens all the time at every airport and using every airplane. I cannot get to the gsx settings menu.
The driver is causing the crash, but can you say the reason this crash is happening after I go up to the in game menus and gsx... settings? something in gsx is causing that.
-
I said the crash requesting airport services on landing happened once, then it happened again at a second airport.
Which "second airport" ? So, basically, it happened only TWICE, in TOTAL ? Meaning, it's NOT a reproducible case, that happens everytime on the same conditions ?
The driver is causing the crash, but can you say the reason this crash is happening after I go up to the in game menus and gsx... settings? something in gsx is causing that.
I was referring to the crash in the airport, first.
However, even in this case, you are confusing the effect with the cause. GSX uses a standard library for its dialog boxes, called wxWidgets, which is used by thousands of product, so GSX doesn't obviously have any interaction with your screen or drivers. The wxWidgets will then call the Win32 api to create dialogs.
So, it seems that your system has a problem with a standard win32 dialog, maybe you have issues with some of the default controls .DLLs. Don't say "it's a clean installation", because something might have gone missing/corrupted.
Also, it's not very clear, if your report of the DirectX 9 crash was related to the GSX settings crash. If it's not, please post the relevant Event viewer crash that happens in THAT case.
What's sure, is that NOBODY, EVER reported a crash when entering the GSX settings.
-
I have not had time to do test flights. I've done 3 flights and 2 of them crashed after landing when I requested ground services.
I have a new FSX Steam install, with the only tweak adding affinity mask. I have only a small number of addons and airports. ASN. FTX Global, Vector, and addon airports like your JFK and LAX. Flightbeam SFO.
I tried both versions of the uiautomationcore.dll file and neither fixes the crash when accessing the GSX settings menu.
I have no other problems in FSX Steam. Only GSX is causing me issues and only in the past week.
This is your program. I would appreciate some help finding the cause of this. I deleted my Virtuali appdata folders. Nothing works. What can I post here or email you to help find the cause of this problem? Since the freezing happens when accessing only GSX, it is a conflict with my system and GSX. Just because you have not heard others say anything doesn't mean it is cannot be your program.
-
I have not had time to do test flights. I've done 3 flights and 2 of them crashed after landing when I requested ground services.
Then please try GSX on a default airport.
I tried both versions of the uiautomationcore.dll file and neither fixes the crash when accessing the GSX settings menu.
This means the Event Viewer related to the crash in the settings (which I've asked), indicates a crash in the uiautomationcore.dll ?
I have no other problems in FSX Steam. Only GSX is causing me issues and only in the past week.
GSX is not causing you any problems, it's the opposite way around: your FSX and your installation are causing problems TO GSX.
Since the freezing happens when accessing only GSX, it is a conflict with my system and GSX
It's a conflict IN your system, that is AFFECTING GSX
Just because you have not heard others say anything doesn't mean it is cannot be your program.
It's not. It's your system, which is causing a problem TO GSX. And yes, just because NOBODY, ever reported a crash like that, it's proof enough.
However, you don't take my word for it. We can always have a Teamviewer session where, like in ALL other cases, where users were absolutely sure "it was GSX", after we had a TM session, I could always find what real cause was. PM for details.
-
I am not an expert and especially not an expert of your program. I have experience in the tech field so I am not tech illiterate. It could be a combination of my system with gsx. Or something with Windows 10. I will message you after my flight I am about to do. Thank you for the help. Could it be a dll conflict with FSLabs?
-
Freeze again, landing at LatinVFR TJSJ. Is there a bug or texture problem with ground services only at certain airports? With codes starting T or M maybe?
-
Is there a bug or texture problem with ground services only at certain airports? With codes starting T or M maybe?
Missing textures would usually cause just a black vehicle, not a crash.
-
Is there a bug or texture problem with ground services only at certain airports? With codes starting T or M maybe?
Missing textures would usually cause just a black vehicle, not a crash.
Could it be some misconfiguration or bug in the code for grabbing parking spots at certain airports? Or a conflict in the fslabs Airbus? I am only guessing here. It happens at all the airports I've flown to this week in the Caribbean. But not at airports on the mainland like your JFK. This started after the gsx update to pull data from the afcad file for selecting ground services.
Are you available to help me I private messaged you. I am available tomorrow morning 7am zulu time and all day after.
-
Could it be some misconfiguration or bug in the code for grabbing parking spots at certain airports?
Nothing in the GSX code can crash FSX, the worse it can happen in the GSX code (which, I remind you, runs ENTIRELY outside FSX, so it cannot affect it in any way), is that the Couatl interpreter might crash itself, but that's precisely the benefit of having it as an external program, that it CANNOT crash FSX, no matter what.
It happens at all the airports I've flown to this week in the Caribbean. But not at airports on the mainland like your JFK.
Ok, this is useful to know, that's why I asked if it happened everywhere.
This started after the gsx update to pull data from the afcad file for selecting ground services.
GSX read the AFCAD data to select the operator since it was released in 2012.
-
Wasn't there a recent change in the logic? From all the sim.cfg files listing ground handling based on airport codes, to only afcad airline codes? I once had different ground options like Swissport and Menzies but today only get them based on the parking codes in the afcad file. And FSX isn't crashing, it is only frozen, something in the background is still going, but the screen is frozen. Sorry I was not clear before, the freeze does not happen in any FSDT, Flightbeam, or Flytampa airport I have gone to in America. The freezes have happened to the Caribbean airports I have been flying to this past week. MMUN, TNCA, TJSJ, TXKF, MDPC that is why I guessed something with the ground handling in those regions. And I have been flying only the FSLabs Airbus, they have a lot of DLL files running in the background too. I would appreciate help tomorrow if you are able to, it is night time and I have things to do. Thank you.
-
Wasn't there a recent change in the logic? From all the sim.cfg files listing ground handling based on airport codes, to only afcad airline codes?
No change in logic, at all. You only have the ability to *override* the parking codes found in the AFCAD, which GSX always read since it was released. Doesn't obviously make any difference if the parking codes are being read from the AFCAD only, or even from your eventual overrides, since in both cases everything that happening, it's happening inside Couatl SO IT CANNOT CRASH FSX, as I've already explained so many times by now. Why keep arguing and insisting about the supposed "code changes". NOTHING in the GSX "CODE" can crash FSX, period.
I once had different ground options like Swissport and Menzies but today only get them based on the parking codes in the afcad file.
If you haven't made any overrides, it's working as it always were. I probably understand what the source of your confusion lies to: we added the distinction between cargo and non-cargo companies, so you won't have unrealistic situations of having passenger companies on cargo parkings.
However, there's a new fad going around with some developers, that flags *everything* as cargo or military cargo, most likely to get rid of default ground vehicles, something that might have been achieved by using the "ga ramp" type, in order to preserve the difference between cargo and non-cargo. Which is why, we added also the ability to override the parking TYPE too, so you can restore the proper parking type, without having to edit the AFCAD.
Since I believe LatinVFR used this method, I guess you are getting some random operators, because GSX could find a cargo operator, with the whole airport flagged to be cargo.
But this is totally irrelevant to your issue: NONE of this could cause a CRASH IN FSX!! The worse effect you would ever see of this change, is that you would have strange operators, which can of course be fixed by restoring the parking types as they are supposed to be.
And FSX isn't crashing, it is only frozen, something in the background is still going, but the screen is frozen. Sorry I was not clear before, the freeze does not happen in any FSDT, Flightbeam, or Flytampa airport I have gone to in America. The freezes have happened to the Caribbean airports I have been flying to this past week. MMUN, TNCA, TJSJ, TXKF, MDPC that is why I guessed something with the ground handling in those regions
I understood exactly, fact is, it doesn't happen here, and nobody else reported it. I asked to a beta tester that has the TJSJ scenery from LatinVFR that you said it always crashed, to check this, and he doesn't see anything strange. I tried the default TJSJ scenery, and no crashes whatsoever. No freezes, nothing.
And I have been flying only the FSLabs Airbus, they have a lot of DLL files running in the background too. I would appreciate help tomorrow if you are able to
Of course, everything is possible, but I cannot see how or why it could happen JUST in the Caribbean. I already answered about being available for a TM session, no use discussing it here, send a PM.
it is night time and I have things to do.
It's midnight for me as well, and I am replying to you...
-
This is the first time I am using Steam for flight sim, but did you try landing at those airports in the FSLabs and request a gate? Are you available for help? I am here the next 8 hours
-
This is the first time I am using Steam for flight sim, but did you try landing at those airports in the FSLabs and request a gate?
I was given an early beta of the A320, but it has been a while ago, so I'm sure it's quite different from the release version. During their beta testing, we were in touch with FSLabs and their testers, to include some extra features just for that plane, and nobody reported a crash, ever.
Are you available for help? I am here the next 8 hours
As I've said, send a PM.
-
Hello :),
i join the battle here, because i've the same problem with my GSX. It's really recent but i don't believe it's linked to plane. I fly with FSLabs A320 and i've this freeze with pdmg 737 too.
Last night i landed with it and asked for ground services from taxiway after leaving the runway. Freeze, no move, but sound alright.
I can't explain it.
I've not any FSDT Airport, so i'm working with default.
Thanks for your support,
Regards,
Sebizart.
-
i join the battle here, because i've the same problem with my GSX. It's really recent but i don't believe it's linked to plane. I fly with FSLabs A320 and i've this freeze with pdmg 737 too.
I've just had a Teamviewer session with 413x3, and we established the problem didn't had anything to do with GSX (as expected). His Windows error log was full of crashes from EZCA.exe, and d3d9.dll.
During a test, it was enough to open the EZCA menu to have FSX crashing. In another test, the sim crashed when switching between Windowed and Full-screen mode, without doing anything.
He tried stopping the FSLabs service from the Services list and removed the FSLabs modules from the XML files, and the crashes stopped. The FSLabs service runs regardless of the airplane selected so, if there's a conflict with it and another module, it will might happen with every plane.
We thought there MIGHT be a conflict between EZCA and the FSLabs service, and this somehow affect GSX too, maybe because they both (by default) use the F12 key so, a crash in EZCA (caused by other causes), might cause problems to GSX when it tries to use the F12 key, which was "taken" by EZCA without being "given back" to the sim, because it crashed.
-
Hello :),
i join the battle here, because i've the same problem with my GSX. It's really recent but i don't believe it's linked to plane. I fly with FSLabs A320 and i've this freeze with pdmg 737 too.
Last night i landed with it and asked for ground services from taxiway after leaving the runway. Freeze, no move, but sound alright.
I can't explain it.
I've not any FSDT Airport, so i'm working with default.
Thanks for your support,
Regards,
Sebizart.
I believe we found the issue and it is the FSLabs services that run even when flying another airplane. Next time you fly the PMDG, make a copy of your dll.xml file, remove the FSLabs entries, in windows stop the FSLabs service, and start FSX and fly the PMDG airplane. That should not crash your sim for now and hopefully FSLabs can respond with an answer or a patch.
Thank you Umberto for the great support sorry to waste your time!
-
Thanks for your help guys,
Now we're waiting for FsLabs update.
Regards,
Sebizart
-
Thank you for the help again. I found info about EZdok long ago, they say the crash logs can be ignored. http://www.simforums.com/forums/ezdok-crash-and-error-nder-windows-10_topic54085.html
-
Thanks for your help guys,
Now we're waiting for FsLabs update.
Regards,
Sebizart
To prevent GSX freezing, taxi to the gate without selecting a gate in the GSX menu, I do not know why this doesn't freeze, since you are still selecting services. But selecting services after parking at the gate it does not freeze. Which is why I originally thought it was a GSX problem. But maybe it could be a conflict with GSX and the FSLabs.
-
But maybe it could be a conflict with GSX and the FSLabs.
As I've already said to you, we have been in contact with FSLabs and their testers for a while, and nobody ever reported a problem between the two. In fact, we even added a couple of special features for the customization we made for the A320.
So no, I don't think there's a conflict between GSX and FSLabs, I guess it's more likely, in your case, a conflict between FSLabs service and EZDok camera, which cause a crash in FSX which is AFFECTING GSX too (obviously, because an abrupt FSX crash will cause issues to all running addons)
-
But the crash happens taxing to the gate and requesting services, not AT the gate. It is very odd. I made some changes to my system and am flying only in window mode for now and I'll see if it fixes that.
-
But the crash happens taxing to the gate and requesting services, not AT the gate.
Doesn't make any difference to GSX, it's creating exactly the same objects using exactly the same code. But I guess the position of the airplane MIGHT make a difference using Ezdok (which IS what's filling your Event Viewer with crashes), and we already verified that, without the FSLabs service, there were no crashes.
Everything in your situation seems to indicate some kind of conflict between the FSLabs and Ezdok camera. And yes, they BOTH are way more critical that GSX would ever be: one it's a Windows service, which runs with an higher privileges than a normal executable, and the other needs to write into the FSX memory to update the camera position.
Maybe there are issues of tread safety at play here. Two programs trying to write the same memory addresses at the same time, which is fairly tricky and full of potential pitfalls:
https://en.wikipedia.org/wiki/Thread_safety
In any case, we already established that GSX didn't had anything to do with the crashes, since they happened (we both witnessed this while in Teamviewer) even WITHOUT even calling the GSX menu.
-
I worked with one of the FSLabs developers and he showed me the crash was caused by a bug they are working to fix in FSLabs Spotlight. It crashes the sim when changing window sizes, full screen to window mode, and back. So I now use just window mode and never change to full screen and it does not crash. I am going to fly later today after work back to a scenery that once caused a problem TJSJ, and request services after landing. Hopefully it will not crash.
-
I worked with one of the FSLabs developers and he showed me the crash was caused by a bug they are working to fix in FSLabs Spotlight.
We already realized it was something in that module. But that doesn't automatically make it a GSX problem.
And, if you remember our Teamviewer session, I asked to call GSX and select a gate when you were on the runway, as if you were just landed, and it didn't crash.
-
And, if you remember our Teamviewer session, I asked to call GSX and select a gate when you were on the runway, as if you were just landed, and it didn't crash
Maybe the bug only happened when using GSX at the departure airport, pushing back and flying then arriving and calling GSX a second time. I have not had a chance to fly hope to more this week.
-
Maybe the bug only happened when using GSX at the departure airport, pushing back and flying then arriving and calling GSX a second time. I have not had a chance to fly hope to more this week.
It doesn't make any difference. As I've said, so many times already, GSX CANNOT, by definition, cause a crash in FSX, because it runs entirely OUTSIDE of it, under the Couatl.exe interpreter.
A separate executable program CANNOT, by definition, access another executable memory space, which is the ONLY thing that can cause a crash.
As I've said, an object created *BY* FSX (on behalf of GSX), MIGHT cause a crash, but only if you have a problem with video drivers, because surely all the GSX objects are 100% correct and SDK-compliant, and if there was a problem with them, we would have thousands of reports by now.
-
It happened again, 2 new flights in 2 days. 2 freezes. Last one right now after landing at ORD. I do not understand how you can tell me this is not something with GSX when the FSX screen freezes but the sounds still play in the back ground. How can it not be GSX? The freezing happens THE SECOND I select my gate, select my ground handling, then select my catering. then... FREEZE. So please explain to me how it is the fault of something else like EZDOK.
-
I do not understand how you can tell me this is not something with GSX when the FSX screen freezes but the sounds still play in the back ground. How can it not be GSX?
I already explained it to you many times, the problem is that you don't want to accept the explanation. You are AGAIN confusing the symptom with the cause. Fact it's happening after you use GSX, doesn't mean the CAUSE is GSX, it's just that your problem, caused by something else, cannot be discovered because nothing else in your sim is doing anything to trigger it, but that doesn't mean GSX is doing anything "wrong".
Since you don't seem to understand, I'll make you a list of situations that CAN crash your sim, being a fault of OTHER stuff, and will appear ONLY if you select GSX, misleading you "it's GSX":
1) You might have a bug in your audio drivers that don't properly support OpenAL, which is a standard library used by hundreds of games which GSX also uses. Since an audio driver CAN crash FSX, if you have this issue, you will notice a crash the moment you start GSX, because the created vehicles will start playing sounds, and a bugged audio driver might crash, misleading you "it's GSX, because it happened when I selected it"
2) You might have a bug in your video drivers that don't properly support some totally standard features used by GSX (and not many others addons), like vertex skinned animations. Since a video driver CAN crash FSX, if you have this issue, you will notice a crash the moment you start GSX, because the created vehicles will start using these animations, and a bugged video driver might crash, misleading you "it's GSX, because it happened when I selected it"
3) If it happens after a flight, a MEMORY-HUNGRY airplane you are probably using might have a memory leak that requires some time to eat up all your VAS so, after you land and then you call GSX, the additional memory requirement caused by asking for new vehicles + their textures + their sounds, has caused the sim to OOM. Since the Windows memory allocator CAN crash FSX, if you have this issue, you will notice a crash the moment you start GSX, because the created vehicles will use some memory so, if you already were CLOSE to memory exhaustions because of the memory-hungry airplane you are using, the sim will crash, misleading you "it's GSX, because it happened when I selected it"
That's just a very short list of the most obvious things.
Since in our Teamviewer session you weren't able to show me ANY GSX crash when just GSX was running, and from your report it seems to happen after a flight, I'd say you are likely in case #3.
If you can show me a reproducible case of FSX crashing as soon GSX is selected, with no other addons running and with a default plane on a default airport, at the beginning of a flight, I'd be totally interested in another Teamviewer session to see if first hand.
-
It does not make sense why another program would be to blame when the freezing starts the second after I request ground services after landing. It is now happening every single time I land and request services. It happened yesterday at your ORD scenery, and today at Orbx KJAC. It is some bug or problem with GSX after landing, since I do not get that freeze when at my departure airport and requesting services, or as I tested when you were on Teamviewer, starting at the runway and requesting services. It only happens when flying from one airport, with requesting services, departing, then landing at another airport and once I request services again, FREEZE. This has become aggravating since it happens ever, single, time.
There are no other freezes at any point in the flight, so it just cannot possibly be caused by anything besides GSX. The fact that I can taxi to the stand, and shut down, then request services, and I do not get a freeze, again, is more proof that the fault is with GSX.
I am not a programmer, and this is your program, it is not a VAS issue either, my vas is well within limits and I am using FSX Steam that dumps unneeded scenery textures.
Yes I could not show it to you, because as I said there, the freezing bug only happens after a flight, do you want me to have a Teamviewer where you are connected for an hour long flight? I can do that but I do not know what you would find except FSX will freeze and I will have to restart because I cannot unfreeze the screen.
I attached the log which does not show anything, it abruptly ends at "Marshaller distance readout disabled by user preferences"
-
It happened again, 2 new flights in 2 days. 2 freezes. Last one right now after landing at ORD. I do not understand how you can tell me this is not something with GSX when the FSX screen freezes but the sounds still play in the back ground. How can it not be GSX? The freezing happens THE SECOND I select my gate, select my ground handling, then select my catering. then... FREEZE. So please explain to me how it is the fault of something else like EZDOK.
These so called freezes are probably caused by FSLabs A320 IAE. Have you tried a default plane?
-
It happened again, 2 new flights in 2 days. 2 freezes. Last one right now after landing at ORD. I do not understand how you can tell me this is not something with GSX when the FSX screen freezes but the sounds still play in the back ground. How can it not be GSX? The freezing happens THE SECOND I select my gate, select my ground handling, then select my catering. then... FREEZE. So please explain to me how it is the fault of something else like EZDOK.
These so called freezes are probably caused by FSLabs A320 IAE. Have you tried a default plane?
Then that is still a bug in gsx conflicting with the fslabs. Calling airport services then freezing right after would point to a problem with gsx.
-
More proof there is some bug in GSX and not my fsx. After landing and taxing from the runway, this time in the menu I selected "restart couatl" and after everything loaded again, I selected my gate, ground provider, and catering service. No crash!
-
More proof there is some bug in GSX and not my fsx. After landing and taxing from the runway, this time in the menu I selected "restart couatl" and after everything loaded again, I selected my gate, ground provider, and catering service. No crash!
A simple question: If this is a bug in GSX, why are you the only one with this problem?
-
More proof there is some bug in GSX and not my fsx. After landing and taxing from the runway, this time in the menu I selected "restart couatl" and after everything loaded again, I selected my gate, ground provider, and catering service. No crash!
A simple question: If this is a bug in GSX, why are you the only one with this problem?
Not every setup is similar, not everyone with a problem reports it. Finding bugs is not about am I the only one. Why are you acting so hostile? I am trying to help Umberto figure out this issue so it can be fixed.
-
Using the restart couatl service in the menus only worked once. When I landed after my 2nd leg back, and tried the "restart couatl" again, FSX froze like it did when I was requesting ground services. So this is a problem with the couatl service on my system, not another addon like EZDok. Umberto any suggestions? Delete all files and reinstall everything? Or just reinstall GSX? I deleted my airport cache before and ran the latest GSX installer but nothing has fixed it. On a restart after this freeze my Intel 82579 Gigabit Network Controller was corrupted and I needed in the device manager to install the drivers again. Win10 Pro all the latest updates. And latest Intel drivers too.
-
Then that is still a bug in gsx conflicting with the fslabs Calling airport services then freezing right after would point to a problem with gsx.
You haven't replied to the question: does the crash happens with a default airplane ?
-
On a restart after this freeze my Intel 82579 Gigabit Network Controller was corrupted and I needed in the device manager to install the drivers again.
Clear, final, and definitive PROOF the problem doesn't have ANTYHING to do with GSX, and it's CLEARLY a driver problem which, as I've said, so many times already, it's the ONLY kind of software that can crash your system so badly.
Another possible explanation, which adds another possible cause of a problem that doesn't have *anything* to do with GSX, but might easily mislead thinking it's caused by it, is that there IS some INDIRECT interaction between "GSX" (not really GSX, of course), FsLabs and your network card, and it's the fact they all use Esellerate.
Without having the slightest idea how it works, internally (other than being sure it works for everybody else), Esellerate does have access to your network card, most likely to get the MAC number in order to recognize an hardware change.
Which means, a BUGGED network driver, or a problem with its settings, MIGHT crash the system when accessed. And Esellerate access it. And Esellerate it's one thing in common that both GSX and FSLabs used.
This could explain why:
- You said (or at least I *think* you implied) it happens with FsLabs, mistakenly accusing "GSX to conflict with FSLabs", which is obviously not true.
- The system crashed hard
- You said yourself your network driver became "corrupted" after the crash.
- It happens only after a some time: maybe it needs a certain amount of communication over the network to show up.
- NOBODY ELSE has reported it, along the 49 pages of this thread, where YOU are the only one reporting THIS specific crash.
-
How can it be proof that it has nothing to do with gsx when restarting your couatl service also caused the crash? And if no one else is reporting a bug, does not mean the bug does not exist. That I have never heard given as a reason for why something cannot be a bug.
-
How can it be proof that it has nothing to do with gsx when restarting your couatl service also caused the crash?
It's only a proof that what ELSE is causing it, is exposing a problem in your system that you cannot notice until you do that. Not that Couatl *itself* it's the cause.
For example: if you have a corrupted .BGL somewhere, this is NOT obviously caused by GSX, but it's a problem nonetheless that you would want to find and fix, but you won't NOTICE IT unless you either fly that scenery and see that something it's missing OR you "Restart Couatl", which will likely cause an error that you wouldn't have noticed otherwise, but you will thank mistakenly assume "it must be Couatl", JUST because in order to notice it, you must do something related to it.
quote]And if no one else is reporting a bug, does not mean the bug does not exist.[/quote]
Of course it's not, but it's a very strong evidence it's NOT a "bug", but a problem that happens only in YOUR system. If if was a bug, someone else would have noticed it by now. We are always awaiting for new reports, of course...
-
Of course it's not, but it's a very strong evidence it's NOT a "bug", but a problem that happens only in YOUR system. If if was a bug, someone else would have noticed it by now. We are always awaiting for new reports, of course...
How can it not be a bug when I am getting crashes using your product? If I do not enable GSX I can fly all day long. If I arrive at an airport and request services I get a crash. if I restart Couatl at my arrival airport, I get a crash. I am not understanding how it isn't a problem. And so others are not getting this issue, why does that not make it a bug? As you know there are so many different variables with each system. And I did not have this issue using FSX Acceleration my crashing has started now after using FSX Steam.
Different airplane, PMDG 737. Same result, First couatl crashes
Faulting application name: couatl.exe, version: 3.1.0.3536, time stamp: 0x57bf02a2
Faulting module name: couatl.exe, version: 3.1.0.3536, time stamp: 0x57bf02a2
Exception code: 0xc0000005
Fault offset: 0x00109f42
Faulting process id: 0x214
Faulting application start time: 0x01d228952d90cc27
Faulting application path: D:\Steam\steamapps\common\FSX\fsdreamteam\couatl\couatl.exe
Faulting module path: D:\Steam\steamapps\common\FSX\fsdreamteam\couatl\couatl.exe
Report Id: 80adc38d-e6fd-461c-8120-b2530ddd4e7a
Faulting package full name:
Faulting package-relative application ID:
then FSX crashes about 30 seconds later
Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: ntdll.dll, version: 10.0.14393.206, time stamp: 0x57dacde1
Exception code: 0xc0000005
Fault offset: 0x0003f959
Faulting process id: 0x15bc
Faulting application start time: 0x01d2289519ab441e
Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 3df1cd8a-157a-4769-b519-adb40eb2f41a
Faulting package full name:
Faulting package-relative application ID:
-
I uninstalled FSLabs Airbus and FSLabs Spotlight and still am crashing even when trying to edit airports in the GSX menu. I want to set "has jetways" to all the gate parking at an addon airport but the second I go up to the menu it crashes FSX.
Restarted and loaded default trike at the gate, go up to the GSX menu and select edit airport
crash.
Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: d3d9.dll, version: 10.0.14393.0, time stamp: 0x57898e34
Exception code: 0xc0000005
Fault offset: 0x000daf70
Faulting process id: 0x2c0
Faulting application start time: 0x01d228b135778753
Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\Windows\SYSTEM32\d3d9.dll
Report Id: ef48b0d4-60b9-43e9-92ec-bbd80d25b141
Faulting package full name:
Faulting package-relative application ID:
then
Faulting application name: couatl.exe, version: 3.1.0.3536, time stamp: 0x57bf02a2
Faulting module name: ntdll.dll, version: 10.0.14393.206, time stamp: 0x57dacde1
Exception code: 0xc0000374
Fault offset: 0x000d9841
Faulting process id: 0xaf0
Faulting application start time: 0x01d228b14edad570
Faulting application path: D:\Steam\steamapps\common\FSX\fsdreamteam\couatl\couatl.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 797a14c0-8755-46b6-99ce-f4cf880b7df2
Faulting package full name:
Faulting package-relative application ID:
I give up. Time to retire FSX and save up for P3D for the holidays I guess.
-
Had some time to look around at the different airports I have installed, and by chance I noticed the airports FSX did not crash at are airports with an afcad file using Flight1's AFX. Many airports I have use afcad files from the freeware program ADE. Orbx airports I fly to like KPSP and KBZN use ADE. And Flightbeam KDEN also uses that. I started at FSDT KLAS and the afcad file does not use ADE it opens with AFX... and no crash.
So I wonder if something is wrong with GSX using only airport sceneries with afcads from ADE. This could be the root cause of all my issues after all. Any thoughts on that Umberto?
-
How can it not be a bug when I am getting crashes using your product?
Because you are the only one reporting it.
If I do not enable GSX I can fly all day long
As I've explained, several times, your bug is AFFECTING GSX, is not CAUSED by it. Your bug is MAKING Couatl crash, it's not Couatl which is making the sim crash.
If I arrive at an airport and request services I get a crash. if I restart Couatl at my arrival airport, I get a crash.
As I've already said, several times, if it happens only after a flight, you are probably consuming your memory so, when GSX ASK the SIM to create some objects, then just don't fit in RAM. That's NOT a "GSX bug"!!!
And so others are not getting this issue, why does that not make it a bug?
That's the strongest indication of all.
As you know there are so many different variables with each system. And I did not have this issue using FSX Acceleration my crashing has started now after using FSX Steam.
Further proving the problem doesn't have anything to do with GSX, which works exactly the same in the two sim, just it uses different folders, but not a single bit of code is different.
-
So I wonder if something is wrong with GSX using only airport sceneries with afcads from ADE. This could be the root cause of all my issues after all. Any thoughts on that Umberto?
Mostly everybody use sceneries made with ADE, which is by far more popular than AFX. I'd say more than 90% of the 3rd party sceneries out there are made with ADE.
In fact, it's AFX which is NOT supported on FSX:SE, and it's AFX which is using a slightly different file format than usual (although it's totally supported by GSX), because it embeds a signature for licensing purposes. So, if the problem was the file format, it should affect sceneries made AFX, rather than ADE, which is the de-facto standard.
But of course, if you sceneries made with ADE are *corrupted* for some reason, then GSX will surely crash, but it will do it EVERY time, NOT just after a flight. Since you weren't able to show me a crash when just starting a flight, when we had the Teamviewer session and it seem from your reports that it happens only after a flight, the AFCAD itself cannot be the cause.
Again, it might just be that sceneries made with ADE, probably because they are freeware sceneries made to replace a default airport, might simply be lighter on memory, so you arrive there with no memory issues, so you are not mislead into thinking that GSX is crashing your system because you called the services (and then it tried to create additional objects) when the memory was critical.
Note that, the absolute quantity of memory is not relevant. What counts is the amount of CONTIGUOUS memory available, which I'm not sure you can check but, in essence, if an application (FSX itself NOT Couatl, since it's FSX that has been asked to create an object, on behalf of GSX, but it's FSX which is doing ALL the work) requires, let's say, 100MB or memory, you might have 300 MB free, but if the largest *contiguous* fragment it's only 90MB, you WILL OOM.
I'm saying this, because NTDLL.DLL errors ARE related to memory allocation.
-
But I am not running out of memory. I started at the gate in a default Trike aircraft, with over 1gb free of VAS. I can show you later this week the crashes I can now reproduce 100% of the time using sceneries like FlightBeam KDEN and Orbx KPSP that both have afcad files created in ADE not AFX.
-
But I am not running out of memory. I started at the gate in a default Trike aircraft, with over 1gb free of VAS.
Which is why I've said:
Note that, the absolute quantity of memory is not relevant. What counts is the amount of CONTIGUOUS memory available
-
That still does not make much sense to me, why would I have memory issues when starting on the ramp with a default aircraft? When I can fly routes using the PMDG aircrafts that are heavy on VAS multiple legs at a time without any issues as long as I do not call up GSX. Either there is something wrong with GSX dealing with afcad files created in ADE, or something in my ADE is broken when compiling afcad files that is causing GSX to crash when reading them.
-
That still does not make much sense to me, why would I have memory issues when starting on the ramp with a default aircraft?
That's the only explanation which is consistent with what we observed so far:
- When we had the Teamviewer sessions, you were never able to show me a crash with GSX, once you disabled the modules from FS Labs, by simply placing the plane on an airport and call GSX there.
- You later said it only happens after landing.
Since GSX doesn't behave different, and it creates the same objects, the only possible explanation that makes an "after a landing" different, is the memory usage and fragmentation caused by the flight itself.
When I can fly routes using the PMDG aircrafts that are heavy on VAS multiple legs at a time without any issues as long as I do not call up GSX.
If the memory-hungry airplane already placed you CLOSE to exhausting VAS, calling for additional objects it's the proverbial "straw that broke the camel's back" which placed you in an OOM situation.
Either there is something wrong with GSX dealing with afcad files created in ADE
Which cannot be, otherwise we would have thousands of similar reports, since 90% of the AFCAD out there are made with ADE.
or something in my ADE is broken when compiling afcad files that is causing GSX to crash when reading them.
You never said it only happens in AFCAD YOU made yourself! Is this the case ?
-
I will keep testing it looks that my system was the issue. FSX Steam installs a version of the uiautomationcore and I tried v16386 in my Windows 10 install. 2 days of successful flights after moving from v18000 of the .dll file. I am sorry Umberto for wasting all your time!
-
I will keep testing it looks that my system was the issue.
This was abundantly clear right from the start, surely after we had our TM session...
FSX Steam installs a version of the uiautomationcore and I tried v16386 in my Windows 10 install. 2 days of successful flights after moving from v18000 of the .dll file. I am sorry Umberto for wasting all your time!
Several years ago, GSX installed what it was universally considered a safer version of the uiautomationcore.dll automatically, so users won't mistakenly assume that "GSX crashed their FSX" but then there was an uproar of protests, so we removed this in later versions, so now we must take the risk that, by NOT doing that, users will STILL mistakenly assume that "GSX crashed their FSX"...It's a battle we really cannot win.
The only sensible solution would be: update to P3D, because FSX is becoming a big mess of unreliability. One of the first thing LM got rid of, was the user interface, which uiautomationcore.dll is part of.
-
Okay but steam installs that same safe version. I had to use v16386 and remove the steam installed v18000. Did not think that had to be done I thought steam had everything fixed.
-
Okay but steam installs that same safe version. I had to use v16386 and remove the steam installed v18000. Did not think that had to be done I thought steam had everything fixed.
So, it seems the Steam installer installs the same version we USED to install in our old installers (dated 2013). If you read that long thread here:
http://www.avsim.com/topic/421820-wrong-version-of-uiautomationcoredll/
You'll see that, while most of the users reported v18000 is the safest, it's still not 100% confirmed, because *some* users said it worked better with other versions.
But in any case, it's not relevant to our installers anymore, since we don't install that .DLL anymore since September 2013: it's just too risky to do it, because there's no sure fix. You seems to be in the minority of those that found their FSX more stable with the older v16386 version.
-
Came back and installed this scenery again. Edited the afcad in ADE
There is an error with a taxi sign name, ADE refuses to compile.
I[GG]m09-27
GG changed to G and compiles
This was crashing GSX I would not be shocked. The scenery is TropicalSim MDPC 2016