FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: RVxSpeed on May 24, 2020, 10:24:16 am
-
Hi,
Greetings. I am just going to get down to the facts. I am experiencing crash near all of the middle east airport(all paid or freeware no default). The reason i am blaming GSX is because if i don't run GSX the sim works just fine.
Aircraft used: PMDG 747.
Issued airports so far:
Armi Project Riyadh
BDOaviation Jeddah
T2G Hamad
Flytampa Dubai
MFSG Dhaka
-
And what kind of error message do you get.
-
And what kind of error message do you get.
No error. Straight to CTD.
-
When you are crusing higher than 10k feet and/or faster thank 250 kts, GSX is completely disabled, so it cannot cause any crash.
-
When you are crusing higher than 10k feet and/or faster thank 250 kts, GSX is completely disabled, so it cannot cause any crash.
Yes it happens during ground activity. Like pushback,catering.
-
Yes it happens during ground activity. Like pushback,catering.
My reply about cruising was in relationship to your sentence "I am experiencing crash near all of the middle east airport", so I assumed you were flying.
Please clarify better, is the crash happening immediately after you select a GSX service ? Or while an activity is performed ? How's your VRAM usage at that time ?
-
Yes it happens during ground activity. Like pushback,catering.
My reply about cruising was in relationship to your sentence "I am experiencing crash near all of the middle east airport", so I assumed you were flying.
Please clarify better, is the crash happening immediately after you select a GSX service ? Or while an activity is performed ? How's your VRAM usage at that time ?
VRAM usage is well below like 500MB upto 1GB remain on the status indicator. Like i said this is happening at random. Like catering, pushback or even sometime when doing parking.
-
VRAM usage is well below like 500MB upto 1GB remain on the status indicator. Like i said this is happening at random. Like catering, pushback or even sometime when doing parking.
500 MB of spare VRAM is already too close to be considered safe because, you cannot possibly know if something might require more of that at the same time. Also, that figure it's only a total number, but it doesn't mean the sim can allocate 500MB or VRAM immediately. VRAM can be fragmented so, even if you have 500 MB free, it's possible the largest continuous fragment might be way smaller than that so, for example, if the largest chunk of VRAM available is only 50 MB and, for example, a GSX vehicle you called requires 60 MB of VRAM, it might still crash the sim due to VRAM exhaustion, so you can still be mislead "GSX has made the sim crash", when in fact the real reason of the crash was your settings are too high for your system, so you put yourself into a situation with too little VRAM available to be safe.
So yes, 500 MB of spare VRAM is just to enough, and it's clear your problem wasn't caused by GSX, but running with too many add-ons and/or too high settings for your system.
Try lowering your settings to reach at least 2GB of free VRAM, and see if it happens again.
-
VRAM usage is well below like 500MB upto 1GB remain on the status indicator. Like i said this is happening at random. Like catering, pushback or even sometime when doing parking.
500 MB of spare VRAM is already too close to be considered safe because, you cannot possibly know if something might require more of that at the same time. Also, that figure it's only a total number, but it doesn't mean the sim can allocate 500MB or VRAM immediately. VRAM can be fragmented so, even if you have 500 MB free, it's possible the largest continuous fragment might be way smaller than that so, for example, if the largest chunk of VRAM available is only 50 MB and, for example, a GSX vehicle you called requires 60 MB of VRAM, it might still crash the sim due to VRAM exhaustion, so you can still be mislead "GSX has made the sim crash", when in fact the real reason of the crash was your settings are too high for your system, so you put yourself into a situation with too little VRAM available to be safe.
So yes, 500 MB of spare VRAM is just to enough, and it's clear your problem wasn't caused by GSX, but running with too many add-ons and/or too high settings for your system.
Try lowering your settings to reach at least 2GB of free VRAM, and see if it happens again.
Yes with latest update of windows now i am getting more vram allocation & it's more than your 2GB limit. Still getting crash. Even it crash as we speak while i asked GSX for pushback. Also the reason i am insisting GSX is causing this CTD is becasue if i don't use GSX & use pushback by PMDG service it doesn't crash. Maybe it's an airport related issue?
This is the error from event viewer:
Faulting application name: Prepar3D.exe, version: 5.0.24.34874, time stamp: 0x5eab3677
Faulting module name: VCRUNTIME140.dll, version: 14.25.28508.3, time stamp: 0x5e155520
Exception code: 0xc0000005
Fault offset: 0x000000000000137b
Faulting process id: 0x4cd4
Faulting application start time: 0x01d63591fa8b6d21
Faulting application path: F:\Prepar3D v5\Prepar3D.exe
Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Report Id: 6c4930ac-8a13-4ff3-b493-62d7aaa466e5
Faulting package full name:
Faulting package-relative application ID:
-
Today i got video proof for you.
This flight using same settings & addons without GSX running.
Verdict: The flight ended perfectly. No CTD.
&t=1136s
&t=1s
This Flight using same settings & addons with GSX running.
Verdict: It crashes while deboarding.
Although today's failing module is different.
Faulting application name: Prepar3D.exe, version: 5.0.24.34874, time stamp: 0x5eab3677
Faulting module name: KERNELBASE.dll, version: 10.0.19041.207, time stamp: 0x746c1866
Exception code: 0xc0020001
Fault offset: 0x0000000000023e49
Faulting process id: 0xa2c
Faulting application start time: 0x01d6367af96ae0d9
Faulting application path: F:\Prepar3D v5\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 7fc0f006-3d9d-4d71-ad4c-201e21dd52ae
Faulting package full name:
Faulting package-relative application ID:
-
Today i got video proof for you.
This flight using same settings & addons without GSX running.
Verdict: The flight ended perfectly. No CTD.
This Flight using same settings & addons with GSX running.
Verdict: It crashes while deboarding.
You haven't proved anything in that video. It's not the "same settings", it's not even the same AIRPORT and, the flight you think crashed because of GSX, when you landed at OMDB, you had 1GB of VRAM LESS than the flight that did't crash, at VGHS.
I assure you GSX doesn't take that much RAM so, the only thing you proved that, when 1 GB less, which can possibly caused by the combination of GSX + a different and more detailed airport, simply exhausted your VRAM. As I've said, it's not really the amount of spare VRAM, but the amount of the biggest *contiguous* chunk of memory that can be used.
If you want to do a proper test, you must really use *exactly* the same settings and, with "same settings", I mean the same airport, the same gate, everything.
-
Today i got video proof for you.
This flight using same settings & addons without GSX running.
Verdict: The flight ended perfectly. No CTD.
This Flight using same settings & addons with GSX running.
Verdict: It crashes while deboarding.
You haven't proved anything in that video. It's not the "same settings", it's not even the same AIRPORT and, the flight you think crashed because of GSX, when you landed at OMDB, you had 1GB of VRAM LESS than the flight that did't crash, at VGHS.
I assure you GSX doesn't take that much RAM so, the only thing you proved that, when 1 GB less, which can possibly caused by the combination of GSX + a different and more detailed airport, simply exhausted your VRAM. As I've said, it's not really the amount of spare VRAM, but the amount of the biggest *contiguous* chunk of memory that can be used.
If you want to do a proper test, you must really use *exactly* the same settings and, with "same settings", I mean the same airport, the same gate, everything.
Ok if you are so much confident about vram usage i will use vanilla or lowest settings & i can bet that using GSX will crash. I am pleased that you have developed the most advanced ground handling program that is available to the simulation market. But that doesn't mean you should be aggressive towards customer. Anyway it will take time as my office has started. But i will definitely prove this to you. I hope that you have better explanation than blaming on VRAM if i am able to prove it to you.
-
Hi,
I have performed the test. Seems like i am right. You wanted the exact same setting & exact same position & exact everything. Here you go. I am also attaching log file for investigation.
Crash Using GSX:
No Crash without GSX
-
I have performed the test. Seems like i am right. You wanted the exact same setting & exact same position & exact everything. Here you go. I am also attaching log file for investigation.
Nothing in your video proves the crash was caused by GSX, because the crash happened AFTER GSX said "Have a good trip". At that time, GSX has completed all its work and is not doing anything. Also, the GSX log you attached doesn't show any errors in GSX, and it logged the simulator just disconnected, likely because it crashed for some other reason.
Want to make it sure it's not GSX ? Try with another airplane and without all those other add-ons you are using.
-
The crash happens when GSX switches off & releases it's service. I am not using many addons here. I still insist you get this fixed. There are lots of people having CTD because of this. My statement is plain & simple. If i don't run GSX i don't get CTD. If i run GSX the simulator crash. Please fix this.
-
The crash happens when GSX switches off & releases it's service.
Again, nothing proves the *cause* is GSX. If it was, it would crash for everybody, but nobody has reported this. It might simply because at that time, something else is happening. I see your sound stuttering while it was crashing but GSX is not obviously using the audio card just to turn off its objects.
I am not using many addons here.
Sure you are. You are using a 3rd party airplane, a 3rd party airport, a 3rd party flight planner, and a 3rd party online plugin ( IVAO ), those are the only ones that were obvious from the video.
There are lots of people having CTD because of this.
I don't see anybody else reported it in the only place that would be useful. If they do, we might check what other add-ons they have and see if the problem is really caused by GSX.
My statement is plain & simple. If i don't run GSX i don't get CTD. If i run GSX the simulator crash. Please fix this.
No, it's not simple. Correlation is NOT causation.
You have a crash when using GSX but, that doesn't mean it's caused by GSX. It might simply caused because, with GSX in COMBINATION with some other add-on, there might be issues that are not GSX's fault that is causing a crash in the sim, which are misleading you it's "caused" by GSX.
The only thing you should do, if you really think the cause is GSX, is:
- Disable ALL add-ons. Proper P3D addons are extremely easy to disable, since they appear in the Options->Add-on menu and can be disable without uninstalling them. Leave JUST the FSDT Addon Manager there, and nothing else.
- If you have other non-compliant add-on that still use the legacy dll.xml/exe.xml method, you must edit these files to add them, or uninstall them.
- Use GSX with a default airplane, on a default airport.
-
So just to make it clear you are not going to do anything about it even though i have solid prove. Yes maybe there is a conflict between an addon & GSX. The sound sutters if i use GSX service. If i don't run GSX service i don't get sound stutter. Still you are asking a lot of things to a PAID customer for a problem that is with your product. A good developer never approaches like this. Instead of asking me or customer why don't you run the test by yourself & i am sure it will crash. I have already posted this issue in social media & i can confirm I AM NOT THE ONLY ONE WHO IS HAVING THIS EXACT SAME ISSUE. I have found at least 3 reports. It's not also PMDG aircraft either. There is also report of Aerosoft A320.
-
Also you are having less compaint or no complaint at all is because people still thinks that P3D V5 is still no much unstable that it might be the actual simulator itself. So they didn't even bother try to use without GSX & check if they can HAVE CRASH FREE FLIGHT WITHOUT USING A PRODUCT WHICH DEV DOESN'T SUPPORT.
-
So just to make it clear you are not going to do anything about it even though i have solid prove.
The issue is, you have NOT any solid prove GSX is the cause of the problem.
I have already posted this issue in social media & i can confirm I AM NOT THE ONLY ONE WHO IS HAVING THIS EXACT SAME ISSUE. I have found at least 3 reports. It's not also PMDG aircraft either. There is also report of Aerosoft A320.
Posting "on social media" is totally useless. This is the one and only place to post reports so, as I've said, if other users have similar problems, they should post here, and we'll of course asking to test in the only what that makes sense to test:
- Testing with ONLY GSX running. If this first test will go well ( I'm fairly sure it will ), we can assume the problem is not GSX alone, but a possible conflict with another add-on.
- If the above is the case, the next step in the test would be adding other add-ons, one by one, until the conflicting one is found.
-
Also you are having less compaint or no complaint at all is because people still thinks that P3D V5 is still no much unstable that it might be the actual simulator itself.
And that's precisely why you cannot also say *for sure* the problem is "caused" by GSX, or there's anything we can or should fix.
So they didn't even bother try to use without GSX & check if they can HAVE CRASH FREE FLIGHT WITHOUT USING A PRODUCT WHICH DEV DOESN'T SUPPORT.
The product is obviously supported but, until you can show evidence that GSX is causing a crash on the sim alone with no other add-ons loaded, it's impossible to say GSX is the cause.
Awaiting for your test with zero add-on now. As I've said, it's fairly easy in P3D to turn off everything without uninstalling.
-
Yeah & also before releasing of P3D V5 HF1 i had to run FSDT updater everytime before i run the simulator otherwise i had the simulator crash just calling the GSX service. GSX definitely have issues.
-
Yeah & also before releasing of P3D V5 HF1 i had to run FSDT updater everytime before i run the simulator otherwise i had the simulator crash just calling the GSX service. GSX definitely have issue.
Which means it was FIXED AFTER HF1 ? And that's precisely what proves, other than it was a problem in the simulator, which HF1 fixed ?
I had another look at your video, since the issue with sound stuttering seems to tell something and, in fact, what is really happening in your video is NOT that GSX is crashing the sim when it "removes its objects", or GSX is making the sound stuttering.
In your "crash" video, after you switched from the IVAO plugin back to the sim, what seems to be the parking brake release sound is being heard, and the windows sound volume icon appears, which means something has changed the sound Volume.
THAT made the sound stutters, not GSX. The vehicles were removed not because GSX was removing them, but because whatever audio-related thing happened there MADE the sim crash, which closed the connection with GSX and, when the sim disconnects from an add-on, it will automatically destroy every objects created by that add-on.
-
Whatever i will mark GSX (latest version) NOT COMPATIBLE WITH P3D V5.0.24.34874
-
Whatever i will mark GSX (latest version) NOT COMPATIBLE WITH P3D V5.0.24.34874
GSX is fully compatible with P3D V5, that's a fact. Re-read my previous post about the sound problem, which might have mislead you thinking it was GSX.
-
Im just shaking my head. As always virtualis "customer support" is maybe not incorrect but always very unfriendly.
Are you interested in the correct user friendly lie, or the correct "unfriendly" truth ?
I have had the same encounter with him on different support queries. Its always a user error and if he's not having the problem, its not the FSDT product that is causing the fault. Or: No one else reported it. You read those statements all over the forum. Thats why I decided not to buy any more FSDT products and hopefully some other developer will come up with a better ground service than the buggy GSX.
That problem is, this is exactly what it really happens, most of the time. Including here. The last video of the OP confirms that: the simulator crashed because something acted on the audio card, and that MADE the simulator crash and that MADE GSX crash, resulting in GSX objects being removed.
The OP assumed that what made the sim crash was "GSX removing its objects", as if there was some kind of bug in "removing" object that made the sim crash. But at that stage, GSX is NOT removing anything, the removal was a consequence of the crash of the simulator caused by whatever made the audio volume change when the OP switched from an external program back to the sim.
And yes, of course, as explained so many times, GSX or Couatl CANNOT crash the sim, since an external .EXE cannot crash another .EXE. But something that handles the audio card CAN of course crash any application, because an audio driver CAN crash the sim.
And when the sim crashes, what will happen is exactly what was shown in the video, in this sequence:
- The simulator crashed because some audio issue. Clearly proven by the audio stuttering AND the audio volume icon moving.
- The simulator crashing abruptly MADE Couatl crash because of the abrupt interrupt in communication, so the user was mislead thinking "it's a Couatl crash", because it saw a Couatl crash in the Event Viewer, which is normal, since the simulator crash MADE it crash.
- When an add-on lose the connection to the sim, all its objects will disappear. That mislead the user assuming it was caused by "GSX removing its vehicles", when in fact at that time GSX is not removing anything. The objects disappeared because the simulator crashed because of the audio issue, Couatl crashed because the simulator crashed, and the GSX objects disappeared because the connection with the sim has been lost.
This is what REALLY happened so not, it's not "user's fault", which I obviously never said that, but it's NOT a GSX problem.
When we have a problem in GSX, we ALWAYS FIX IT, and this has been proven so many times along the years, that is not even worthy discussing it. When a problem is NOT a GSX problem, we clearly explain why it isn't, providing ample evidence.
-
Thank you for your answer - I honestly wasnt expecting that, so thank you for that!
As I stated, your support was not wrong or incorrect its just the attitude behind it. I know for a fact that dealing with customers - especially flightsim customers - can be nerve-wracking. Of course you cannot support something when its not GSX's fault - but what I mean is, that you should consider your product working among other addons because that is what happens in reality. If a product runs on a clean sim and doesnt with other addons you simply cannot state that your product is fine and its the fault of all the others. That is the attitude Im talking about - and not especially with this OP and his problem.
I think we should work together not against each other. Of course you cant fix another developers product - but I hope you can see what I mean.
-
I just got this today, while pushing back using GSX. This is the first time this has happened.
Faulting application name: Prepar3D.exe, version: 5.0.24.34874, time stamp: 0x5eab3677
Faulting module name: VCRUNTIME140.dll, version: 14.25.28508.3, time stamp: 0x5e155520
Exception code: 0xc0000005
Fault offset: 0x000000000000137b
Faulting process id: 0xa24
Faulting application start time: 0x01d63cbfd339e1c7
Faulting application path: K:\P3D v5\Prepar3D.exe
Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Report Id: 93f261b4-8f97-4769-8c8f-d5ab543c44c8
Faulting package full name:
Faulting package-relative application ID:
This also
Application: Prepar3D.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFF6044137B
Thanks for your support.
-
sorry to pile on. I'm getting these crashes (intermittent) when requesting pushback or stairs. Pics of event crash. This occurs in multiple different aircraft at multiple different airports. The only consistent thing is gsx.
https://imgur.com/a/3CPGVGg
-
If you can't fix your product do not blame others. I already reported this & let me be clear with you this time THE SOUND ISSUE ONLY OCCURS IF I RUN GSX SERVICE. Your statement "When we have a problem in GSX, we ALWAYS FIX IT" is not true is a complete lie. This is just based on the user that i got to interact in social media. People have real lives to live. They don't have an eternetly coming into this forum knowing that support team doesn't even recongnize a problem as a problem.
-
Thank you for your answer - I honestly wasnt expecting that, so thank you for that!
As I stated, your support was not wrong or incorrect its just the attitude behind it. I know for a fact that dealing with customers - especially flightsim customers - can be nerve-wracking. Of course you cannot support something when its not GSX's fault - but what I mean is, that you should consider your product working among other addons because that is what happens in reality. If a product runs on a clean sim and doesnt with other addons you simply cannot state that your product is fine and its the fault of all the others. That is the attitude Im talking about - and not especially with this OP and his problem.
I think we should work together not against each other. Of course you cant fix another developers product - but I hope you can see what I mean.
Yes thank you for explaining this correctly. Actually umberto should a a remark on GSX(may have compatibility issue with other addons in P3DV5) that way people like me won't get triggered.
-
You see Umberto people are having issues with GSX. I am not the only one. So i stand with my statement. GSX is not fully compatible with P3DV5 using other addons. I sincerely hope as this is a paid product you will be kind enough to fix compatibility issue. If you want to run diagnose on my PC using remote tool. You are most welcome. But please for once fix this issue. We have come far a lot since P3DV5 is superior in performance gain. Don't want to stuck myself for having a not compatible ground service product.
-
If you can't fix your product do not blame others.
Nobody has obviously blamed "others". I'm only saying the audio problem you have is NOT caused by GSX.
I already reported this & let me be clear with you this time THE SOUND ISSUE ONLY OCCURS IF I RUN GSX SERVICE.
That doesn't mean it's caused by GSX, it's a problem with GSX, or it's something we could fix in GSX.
GSX is NOT changing the audio volume by itself. Something else is doing it and, of course, it's not normal that, just changing the volume would cause the simulator to crash.
Your statement "When we have a problem in GSX, we ALWAYS FIX IT" is not true is a complete lie.
It's the undeniable truth, proved by years of constant updates and fixes WHEN the problem is GSX.
This is just based on the user that i got to interact in social media.
Social media is full of flat-earthers and people that don't believe we went on the moon either so, I wouldn't use those them as examples of reliability.
People have real lives to live. They don't have an eternetly coming into this forum knowing that support team doesn't even recongnize a problem as a problem.
So, are you trying to say that, instead of coming on the ONLY place it would make sense to report a problem "because they have a life", they instead post on "social media", because their "life" is there ?
I know you don't like the cold hard fact that, other than you, NOBODY HAS EVER REPORTED THAT KIND OF CRASH HERE, which doesn't play well with your fixation that GSX is the cause if your crash, because if it was, we would be obviously FLOODED by similar reports here.
So, instead of accepting that evidence the problem must be in something with your setup, you are trying to say people discuss it on "social media" instead...
Going back to sound, there is a KNOWN issue which ( of course ) is NOT caused by GSX, and results in sound being lowered/raised when the simulator windows goes in and out of focus, which is what you did in your video, see the discussion here:
https://www.avsim.com/forums/topic/547541-prepar3d-v44-lowering-the-sound-from-background-apps/
As you can see in the thread, that's not a problem caused by GSX, of course. It's Windows *itself* that lowers/raise the volume and, you are ( again ) misled it's "happens with GSX only", just because GSX it's just another background app that results in its sound volume being changed BY WINDOWS when switching the in-focus window.
Normally, on a system that doesn't have any problems, the only think that happens is the volume changes so, what you really should ask yourself is:
WHY, when Windows acts by itself on the volume, what normally results in just the sound volume being lowered/raised, something that as you can see on the Avsim thread happens to everybody with NO crashes, on YOUR system it crashes the sim ?
That thread suggest a solution to prevent windows doing that so, maybe, if your audio card drivers don't respond well to that ( audio drivers CAN crash the sim, GSX CANNOT ), disabling that option might fix the problem for you.
-
Hey Umberto. Looks like from PG2 tangjuice and myself have the same issue which looks different than the OP's. Should we start a new thread?
-
So i stand with my statement. GSX is not fully compatible with P3DV5 using other addons
You are now changing your version, since you are probably starting to realize the problem is not caused by GSX, but an issue with your audio, so you are not adding "with other add-on".
By your reasoning, one can just as well said "That OTHER add-on is not compatible with P3D V5, using GSX". Assuming it's another add-on, which I'm not really sure, I only sure it cannot be GSX, because GSX cannot make the sim crash.
But please for once fix this issue.
Since the issue is NOT caused by GSX, because GSX cannot make the sim crash, it's nothing we can fix. But yes, if you want to have a remote session, that's perfectly fine, since I might be able to find what is the real cause of the problem. PM if interested.
-
Hey Umberto. Looks like from PG2 tangjuice and myself have the same issue which looks different than the OP's. Should we start a new thread?
Yes, since this thread was clearly related to an issue with audio.
-
Per the suggestion of a user on P3D v5 forums the visual studios C++ fixed my issues. I don't know if this will work for everyone but it's worth a try. https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads.
-
So, Umberto i did send you a PM. You didn't respond. So are you afraid on solving an issue caused by a product that you have released & made the comment "Compatible with V5"?
-
Per the suggestion of a user on P3D v5 forums the visual studios C++ fixed my issues. I don't know if this will work for everyone but it's worth a try. https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads.
Worked perfectly. I had the same issue with P3Dv5 crashing when attempting a pushback with GSX. I installed as many versions of visual C++ (x64) as i could. I also unchecked ECAM rendering in the configurator and the problem went away. Thanks for actually getting to the issue instead of arguing with the customers about the cause*cough* *cough*
-
Hello, Is anyone home? I am a paid customer. Requesting support. Getting crash while pushing back from VGHS. Without GSX no crash.
-
Thanks for actually getting to the issue instead of arguing with the customers about the cause*cough* *cough*
Not sure what you are trying to say here. Your report proved, once again, the crash didn't had anything to do with GSX.
-
This is my absolute favorite bug right now.
FSDT doesn't know why this is happening.
LM doesn't respond on the forums.
Users are f***ed.
-
This is my absolute favorite bug right now.
I'm not sure what bug you are referring to. The OP posted a video trying to "prove" GSX caused a crash, because he saw GSX objects disappearing, so he assumed GSX "caused" a crash when it removed its objects.
Instead, what really happened in that video was:
- He switched to another program
- When he came back to the sim, the default Windows audio volume icon came up, as if Windows was adjusting the volume when returning back to the sim.
- This caused a sound stuttering, which MADE the simulator crash.
- The simulator crash automatically resulted in GSX objects being removed, because GSX was abruptly disconnected from the sim and when a client disconnects, the object created by it will be automatically removed BY THE SIM, but this mislead the OP thinking "it was GSX", because he saw the GSX objects disappearing, and assumed the crash was caused by GSX, when the real reason was Windows adjusting the volume level, and this making the sim crash for some reason.
There are several threads about Windows doing this when switching back and forth between apps, but it doesn't NORMALLY cause a crash, it's only annoying because the volume keeps changing. This is the first time I see a crash caused by this but, again, it cannot possibly be GSX, it's just the fact Windows is acting on the volume.
This "feature" can be DISABLED, of course so, maybe, it might fix the crash too.
-
Sorry, I had a moment of frustration and only glossed over the thread...I'm continuing to experience the VCRUNTIME140.dll CTD with GSX when I open the control window.
-
Sorry, I had a moment of frustration and only glossed over the thread...I'm continuing to experience the VCRUNTIME140.dll CTD with GSX when I open the control window.
So, your problem doesn't have anything to do with this thread and the video posted about the sound issue. It's surely related to a problem or a conflict in your VC++ runtimes libraries, which might be fixed by uninstalling them and reinstalling them, as you can read in tangjuice81 post.
-
Sorry, I had a moment of frustration and only glossed over the thread...I'm continuing to experience the VCRUNTIME140.dll CTD with GSX when I open the control window.
So, your problem doesn't have anything to do with this thread and the video posted about the sound issue. It's surely related to a problem or a conflict in your VC++ runtimes libraries, which might be fixed by uninstalling them and reinstalling them, as you can read in tangjuice81 post.
I guess I'll try uninstalling/reinstalling, though I've already done the repair option. I'm just confused because it ONLY happens in V5. Never had this problem with V4.
-
I guess I'll try uninstalling/reinstalling, though I've already done the repair option. I'm just confused because it ONLY happens in V5. Never had this problem with V4.
The don't use the same version of the runtimes. P3D V4 uses the 2017, while V5 uses the 2019. Note that, today the VC installer is called "universal CRT", which covers 2015, 2017 and 2019 versions in a single redistributable.
-
Are you going to actually solve the issue that is being asked in this thread from the beginning?
-
Are you going to actually solve the issue that is being asked in this thread from the beginning?
As I've, several times already, the last video you posted clearly proved the problem wasn't caused by GSX.
What caused your sim to crash was the audio driver when you switched back and forth from the sim to the external flight planner. This caused the Windows audio volume to change, which caused the audio to stutter and MADE the sim crash ( because GSX CANNOT crash the sim, while your audio drivers CAN ) and, of course, when the sim crash, GSX will lose connection to it, so all its objects will be removed, and this mislead you thinking it was GSX crashing while it was removing objects.
As I've said, the feature to automatically change the volume when switching between apps CAN be disabled in the Windows audio settings so, perhaps, if you try that, this might prevent the audio drivers to crash the sim.
And please, stop saying "it doesn't happen without GSX", because that's not an indication the problem is caused by GSX or we can or should fix it. For several reasons:
- The first one, because in the "not crash without GSX" video, you didn't do the same switching between the flight planner and the sim
- The second reason is, even if you could switch from another app back to the sim with no audio crashes without GSX, that still doens't mean GSX is the cause. The feature ( which can be disabled ) that allows Windows to change the volume when jumping between apps, will do that for all the loaded executables, and that includes GSX own Couatl.exe program so, Windows is probably trying to change the volume of Couatl.exe itself and, BECAUSE there's some kind of bug in your audio driver, possibly related to OpenAL support, it's POSSIBLE your audio driver cause a crash only when trying to change the GSX volume. Again, it's a fault of your audio driver, we don't have any control over it if your audio drivers crashes the sim when Windows tell it to change volume.
Many users reported the change on audio made by Windows to GSX, but ONLY as a minor annoyance in that the GSX sounds go down in volume, so they usually disable that feature, but nobody ever reported a crash because of this, you are the only one that had a crash caused by the audio volume going Up/Down automatically by Windows, which seems to suggest you must have some kind of issue that affects audio, like 3rd party audio card utilities, bad audio drivers, bad OpenAL support in your audio drivers, something like that.
-
The audio up/down is done by me. Not by windows. I have a z5500(search google) sound system which always stays at max sound output. I use my keyboard volume button to increase/decrease volume. That might give you the expression of windows is changing volume automatically.
I am telling you once again please use a descent tone while talking to a customer. Specially paid one. You have created a software which i bought from online store. You are suppose to provide support for it. I already have multiple proof of vidoes shows that shows running GSX causing the sim to crash. Instead of arguing with me i insist you come & provide a remote session in resolving this issue or test in your workstation to see if there is any actual issue with the product.
Also i was doing a complete fresh re install of GSX. Doing so the following error came up. I selected ignore in order to continue the installation. I am going to ask you to provide an explanation for this error(since the error is completely visible & it's happening while installing GSX so you can't blame any addons or simulator for it).
Finally if you can't provide support & be an ignorant developer please mention it in your product "No support will be provided" or simply mention "P3DV5 not fully compatible with GSX".
-
The audio up/down is done by me. Not by windows. I have a z5500(search google) sound system which always stays at max sound output. I use my keyboard volume button to increase/decrease volume. That might give you the expression of windows is changing volume automatically.
So, you changed the audio manually, your video shows that as soon as you do that, the audio stutters, caused the sim to crash and how this can possibly be "caused" by GSX ?
Regardless if Windows or you change the audio, if that might cause a crash to the sim, it's still not GSX's fault. Could you please try the same procedure without touching the audio ?
I am telling you once again please use a descent tone while talking to a customer
I'm not sure what you are trying to tell here. We are not "talking", I'm writing, and I'm providing you with totally accurate information based on your report. There's no "tone" involved here and I can't see anything in my totally techincally and entirely neutral sentences that could be mistaken as a "tone".
You have created a software which i bought from online store.
Which comes with a Trial version, which can be used for an unlimited number of time on some airports, and the whole point of offering a Trial version, is precisely to make you absolutely sure it works on YOUR system, before purchasing it.
You are suppose to provide support for it.
Which I'm keep doing, by spending my time always replying to you, trying to make you understand what's your real issue might be. Because, if you keep fixating about GSX being the problem, you'll never find out what really is.
I already have multiple proof of vidoes shows that shows running GSX causing the sim to crash.
No, you posted multiple videos of what YOU think is proof GSX is "causing" the crash, when in fact it's not. Your statement about assuming GSX "must" be the cause, because you thought GSX was removing its objects is the most clear proof of what is misleading you. GSX is NOT supposed to remove anything at the stage. The objects were removed by the simulator itself, because moments before its crash, CAUSED by something related to audio, it lost connection to GSX and when a Simconnect client disconnects, the simulator will automatically remove all the objects created by it.
Instead of arguing with me i insist you come & provide a remote session in resolving this issue or test in your workstation to see if there is any actual issue with the product.
I was trying to suggest looking into audio first, before doing that, so you could fix the problem yourself.
Also i was doing a complete fresh re install of GSX. Doing so the following error came up. I selected ignore in order to continue the installation. I am going to ask you to provide an explanation for this error(since the error is completely visible & it's happening while installing GSX so you can't blame any addons or simulator for it).
Of course I can provide an explanation of that error and, of course, it doesn't have anything to do with your problem. It's a known issue that sometimes, due to various permission difference across systems, the GSX installer is prevented from installing a font that is already installed. But precisely for the reason the font is already installed, you can safely ignore the error and continue.
Finally if you can't provide support & be an ignorant developer please mention it in your product "No support will be provided" or simply mention "P3DV5 not fully compatible with GSX".
Since GSX is perfectly compatible with P3D V5, and everybody use it happily with it, you should ( again ) stop repeating this, and speaking about "tone", what about that "ignorant developer" of yours ? If you cannot write something without being offensive, you should even dare to mention "tone" in the first place. No, being "paying customer" doesn't give you the right to call me ignorant, or even imply I might be.
-
You have created a software which i bought from online store.
Which comes with a Trial version, which can be used for an unlimited number of time on some airports, and the whole point of offering a Trial version, is precisely to make you absolutely sure it works on YOUR system, before purchasing it.
The software was running fine in V4. There was no complaint about it. I never had any issue with it. But starting with V5 all of this CTD happening just after installing GSX.
No, you posted multiple videos of what YOU think is proof GSX is "causing" the crash, when in fact it's not. Your statement about assuming GSX "must" be the cause, because you thought GSX was removing its objects is the most clear proof of what is misleading you. GSX is NOT supposed to remove anything at the stage. The objects were removed by the simulator itself, because moments before its crash, CAUSED by something related to audio, it lost connection to GSX and when a Simconnect client disconnects, the simulator will automatically remove all the objects created by it.
It's not i think. It's already proven. Nobody should take my word for granted. I am still insisting if i run P3DV5 with all of the mother addons available for the sim. The sim will not crash. But if i run GSX. It will crash while performing various GSX activities like pushback,catering,boarding,deboarding.
Another thing it's a software. Not a god. Your product may cause an issue or conflict even if it's with 0.001% of the customer base that you have. Even if it's that minor it's still an GSX issue. Which is your concern. So saying that nobody else is having this same issue is not acceptable.
-
The software was running fine in V4. There was no complaint about it. I never had any issue with it. But starting with V5 all of this CTD happening just after installing GSX.
But again, since nobody ever reported this problem with P3D V5, it's clear GSX works with P3D V5 with no issues. The ONLY thing that could POTENTIALLY crash the sim in V4, which was Render to Texture with DirectX 11, is completely disabled in V5 for the time being.
It's not i think. It's already proven. Nobody should take my word for granted. I am still insisting if i run P3DV5 with all of the mother addons available for the sim. The sim will not crash. But if i run GSX. It will crash while performing various GSX activities like pushback,catering,boarding,deboarding.
But if it really did, it would happen to everybody, not just you.
Another thing it's a software. Not a god. Your product may cause an issue or conflict even if it's with 0.001% of the customer base that you have. Even if it's that minor it's still an GSX issue. Which is your concern. So saying that nobody else is having this same issue is not acceptable.
None of the information you provided ever proved the problem is caused by GSX. Instead, I provided ample explanation why it's probably related to audio because, as I've said so many times already, a problem with an audio driver CAN crash the sim. GSX, by itself, CANNOT.
I am still insisting if i run P3DV5 with all of the mother addons available for the sim. The sim will not crash. But if i run GSX. It will crash
That doesn't prove anything and it's the wrong approach to the situation. If the problem is caused by a conflict with another add-on, which only happens if GSX is installed, that doesn't mean GSX is the cause, it only means there's a conflict with another add-on.
What you should have done, instead, is to install P3D V5 with NOTHING ELSE OTHER THAN GSX, and see if you still have the crash, and see if you stop the crash by disabling GSX. Then you would have a point, worth investigating.
-
What you should have done, instead, is to install P3D V5 with NOTHING ELSE OTHER THAN GSX, and see if you still have the crash, and see if you stop the crash by disabling GSX. Then you would have a point, worth investigating.
So let me just hear you right. You want me to test in vanilla scenario for a product that was developed by you? Why would i or anyone else would do that. Shouldn't you be the one who is suppose to re test to see if everything else is ok. Let's say i am using PMDG 747 in every scenario. The crash only happens with using this aircraft. Then if i report it to PMDG they will say since their pushback(it's already proven that if i use PMDG default pushback the sim doesn't crash) system works fine it's not their concern why using GSX with PMDG causes the crash. Then what? You will just say that it's PMDG problem.
Instead of wasting hours of arguing can we please just move on to actually resolve the issue once & for all. I don't have the mindset nor the time to continue arguing with a dev for a product that clearly have issue.
Please do the testing using the following scenario.
Aircraft: PMDG 747
Airport: MFSG DHAKA(https://secure.simmarket.com/mfsg-hazrat-shahjalal-international-airport-vghs-2019-fsx-p3d-fs2004.phtml) it's V5 supported & i have updated files from the devs.
Weather Engine: Active Sky P3D Beta 5
Crash test scenario:
1. Sim Crash when pushback from various position.
2. Sim crash when deboarding.
-
So let me just hear you right. You want me to test in vanilla scenario for a product that was developed by you?
Obviously yes, and it's clearly a good suggestion. Why, exactly, the fact the addon was "developed by us" make it any less valid ?
Why would i or anyone else would do that.
For the obvious reason to understand if, since your problem was clearly audio-related, there's a chance of conflict caused by audio drivers, when another product use its own custom audio routines.
Shouldn't you be the one who is suppose to re test to see if everything else is ok.
Obviously not. We cannot test with the infinite variations of multiple add-ons out there.
Let's say i am using PMDG 747 in every scenario. The crash only happens with using this aircraft.
Is this the case ?
Then if i report it to PMDG they will say since their pushback(it's already proven that if i use PMDG default pushback the sim doesn't crash) system works fine it's not their concern why using GSX with PMDG causes the crash. Then what? You will just say that it's PMDG problem.
Wrong assumption.
I wouldn't say it's PMDG "fault", it might be a conflict which might very well be a bug in your audio drivers ( again, is happening TO YOU ONLY, don't you think lots of users use the PMDG 747 + GSX ? ) which happens only due the way they might handle custom audio. Not their fault, neither GSX's, if your audio drivers might have problem handling two different apps using audio at the same time.
Instead of wasting hours of arguing can we please just move on to actually resolve the issue once & for all. I don't have the mindset nor the time to continue arguing with a dev for a product that clearly have issue.
The problem is that GSX clear DOES NOT "have issue", surely not any that can cause the sim crash. You keep repeating this but, repeating something wrong doesn't make it right, regardless how many times you repeat it.
Please do the testing using the following scenario.[/quiote]
Aircraft: PMDG 747
Weather Engine: Active Sky P3D Beta 5
I won't do that, since I won't use anything that is clearly advertised as Beta. The best I can do, is to test GSX + the PMDG 747 at one of our airports, like KORD, just to use something that is very detailed.
-
You keep saying sound sound sound. Here you go. Another video. This time the volume wasn't touched. Yet here you go with the crash. There was also not any external to internal & vice versa view change. If i repeat the same thing without GSX explain that why it won't crash?
Since you also decline to test to prove that there is a flaw in your product which i have clearly identified. I am also declining to do a vanilla test. You didn't mention anywhere in your product that it may or may not work with all other addons available in simulator. I don't understand one thing. Why it's so hard for you or anyone to understand a simple logic.
Every other addons installed running GSX service=Crash
Every other addons installed running without GSX service=No Crash
I don't think there is any necessary for anyone to test it in vanilla scenario. We in the sim community made a golden rule on troubleshooting. If we find out our sim crashing. We disable everything and re enable addons until we are able to reproduce the same scenario. It has been the golden rule in flight simulation for years in the community. So in this case rulling out GSX service results in a complete stable simulator. Since the product is supported & developed by you. You should be the one finding what's causing the issue & resolve it.
-
Since you also decline to test to prove that there is a flaw in your product which i have clearly identified. I am also declining to do a vanilla test.
Don't think it was so much the testing itself he's refusing to do as much as it is testing with Active Sky P3D Beta since, as the name implies, it's still in beta, so it could just as easily be Active Sky Beta that's causing issues, which would make it a little difficult to rule anything out.
-
I don't think there is any necessary for anyone to test it in vanilla scenario.
That's exactly what you should do, instead.
We in the sim community made a golden rule on troubleshooting. If we find out our sim crashing. We disable everything and re enable addons until we are able to reproduce the same scenario. It has been the golden rule in flight simulation for years in the community. So in this case rulling out GSX service results in a complete stable simulator. Since the product is supported & developed by you. You should be the one finding what's causing the issue & resolve it.
Exactly: you just made my point, and managed to counterdict your previous sentence.
- You first said "I don't think there is any necessary for anyone to test it in vanilla scenario"
- Then you say "we disable everything"
Instead, you never "disabled everything" and started with JUST GSX and the sim. Failing to do that, will prevent you to find a problem that happens only because of the COMBINATION of add-ons.
-
It's because i don't need to disable everything. If disabling GSX resolves the issue. Then the problematic addon is found & should be addressed first before moving with other.
-
It's because i don't need to disable everything
Yes you do, and you know it very well, since you said "we disable everything".
. If disabling GSX resolves the issue. Then the problematic addon is found & should be addressed first before moving with other.
Wrong, again.
If disabling GSX without disabling "everything" first resolves the issue, you can't say if the problem is caused by GSX or a conflict with another add-on, which even if it happens, you cannot say if it's "caused" by GSX or we can even fix it from our side.
-
Since you also decline to test to prove that there is a flaw in your product which i have clearly identified. I am also declining to do a vanilla test.
That's not the case. I tested the PMDG 747 many times but right now, I'm waiting for PMDG to reply to my ticket, since I had to reinstall Windows from scratch, and need a reactivation, but I'll test it again as soon as I can use it.
-
There was also not any external to internal & vice versa view change. If i repeat the same thing without GSX explain that why it won't crash?
Saw this video and, from your Event Viewer, it's fairly obvious the problem doesn't have ANYTHING to do with GSX. What crashed this time was your video driver. You are trying to use P3D V5 with an 8MB video card with almost every graphic and terrain slider to the right, which everybody knows is almost impossible without getting a crash.
It's very possible the few extra memory required by the GSX vehicles ( everyting you see takes SOME VRAM ) it's enough to cause the crash, but that's not GSX's fault if you keep your settings so high that you were already using 6.2 GB out of 6.9 GB you have, that's only 10% of free spare memory, which is not nearly enough to run P3D V5 safely.
As LM explained several times, it's not just a matter of how much free VRAM you have, what matters is the size of the largest countinous block, which might be way less than you see there. Yes, Video memory fragmentation is an issue in DX12.
I'm fairly sure if you tried with lower settings, so you could have more spare VRAM, it will not crash.
-
There was also not any external to internal & vice versa view change. If i repeat the same thing without GSX explain that why it won't crash?
Saw this video and, from your Event Viewer, it's fairly obvious the problem doesn't have ANYTHING to do with GSX. What crashed this time was your video driver. You are trying to use P3D V5 with an 8MB video card with almost every graphic and terrain slider to the right, which everybody knows is almost impossible without getting a crash.
It's very possible the few extra memory required by the GSX vehicles ( everyting you see takes SOME VRAM ) it's enough to cause the crash, but that's not GSX's fault if you keep your settings so high that you were already using 6.2 GB out of 6.9 GB you have, that's only 10% of free spare memory, which is not nearly enough to run P3D V5 safely.
As LM explained several times, it's not just a matter of how much free VRAM you have, what matters is the size of the largest countinous block, which might be way less than you see there. Yes, Video memory fragmentation is an issue in DX12.
I'm fairly sure if you tried with lower settings, so you could have more spare VRAM, it will not crash.
Yup,
I am running RTX 2080 Super graphic cards, and when loaded with ORBX base and vector, the graphic card is consuming 2-4 Gbyte of VRAM, on average.
If you are also running any additional airport add-on or other add-ons, then you will push it to 4-6 Gbyte of VRAM.
Cheers,
Chris Truong.
-
Here you go Mr. Umberto another video of crash free without using GSX. This time i am using Ground Crew X.
I don't know if you are aware of it. But LM has a built in fail safe scenario. In the event of an sim crash imminent P3D turns off EA(which is in beta) & turns some settings down automatically. I was wondering if your product is so much heavy(compare to other addons) which will eventually crash due to VRAM exaustion. Why don't you develope something similar like turning off PBR of GSX services in order to NOT MAKE THE SIM CRASH during GSX Operation.
Also the video you posted on AVSIM forum. Clearly shows that you are using GSX with another product developed by you. I don't think you ever mentioned that your product may or may not work with 3rd party addons.
This is from your GSX product page:
Works with every airport, both default and 3rd party
So here is the thing:
- You should stop arguing with me as a customer to justify that your product has no issue which i have proven several times instead of your meaningless logic.
- You should modify your program not to make the sim crash even if that meaning to disable certain features like PBR on vehicles. I will be more happy not to have PBR & live a crash free sim experience.
- You should agree with the statement that "GSX is not fully compatible with P3D or may cause issue when using other 3rd party addons".
Oh another thing i forgot to mention. You said your product worked flawlessly since 2015? I remember when LM used to give micro updates. The sim won't even load without updating coutal engine. How we were so certain? Disable coutal engine from addon manager then the sim would load. We had to wait days for the update to come before we could even open our simulator. So yeah your product always had issues. It's high time you listen to customer problem instead of arguing with them which will result in going no where.
Until you fix your product i am going to continue using Ground Crew X to live a crash free sim experience.
-
Here you go Mr. Umberto another video of crash free without using GSX. This time i am using Ground Crew X.
So I'll post again the video you asked for:
showing GSX working perfectly with a detailed airport and a detailed 3rd party airplane
I was wondering if your product is so much heavy(compare to other addons)
The product is NOT "so much heavy". Which of course, can be seen in my video, in which the VRAM occupation goes from 5.9 GB BEFORE calling GSX, to 6.2 GB after calling it. I say taking only 300 MB of VRAM for a full set of vehicles is not "heavy" and totally reasonable. A detailed airplane takes about 1.0GB by itself. Just TruSky alone can take in eccess of 1.0GB.
OBVIOUSLY, if you are already too short of VRAM, even 300 MB might be just enough to cause a crash, if you keep most of your sliders to the right, which nobody does, with an 8GB card.
Why don't you develope something similar like turning off PBR of GSX services in order to NOT MAKE THE SIM CRASH during GSX Operation.
LM can do something like that ( turning off settings on the fly ), and even them are not always entirely successful, since the simulator STILL crashes sometimes. We can't do that from GSX, since add-on don't have the ability to change the settings of the simulator on the fly. Not in a documented way, at least, and we don't want to resort to hacks, just because you don't know how to manage your settings.
Also the video you posted on AVSIM forum. Clearly shows that you are using GSX with another product developed by you. I don't think you ever mentioned that your product may or may not work with 3rd party addons.
Wrong again.
First, because I wasn't using GSX "just" with KORD V2, I was also using the Qualitywings 787, for the only reason that I couldn't test the PMDG 747, because I was waiting PMDG to reactivate my copy, so I needed:
- A very large airport scenery, so you couldn't say "GSX doesn't work with big airports that take lots of memory"
- A detailed 3rd party airplane, so you could't say "GSX works only with default airplanes", and I needed an airplane with a P3D V5 installer.
And I wanted to show that, with those two, I could SAFELY use 6.5 GB of VRAM JUST because my card is 11.0BG, and I wanted to show GSX DOESN'T CRASH the sim, not even when used with add-ons that surely takes quite a bit of memory.
Of course, several users on Avsim confirmed they use GSX with the PMDG 747 with no issue and don't worry, I just got my activation back from PMDG today so, be sure I'll post ANOTHER VIDEO on a non-FSDT airport with the PMDG 747.
This is from your GSX product page:
Works with every airport, both default and 3rd party
Which is true, as everybody knows.
- You should stop arguing with me as a customer to justify that your product has no issue which i have proven several times instead of your meaningless logic.
You should stop arguing saying our product make the sim crash, because you have been proven wrong multiple times, here and on Avsim, but many users which all confirmed your logic is wrong, and they use GSX with P3D V5 WITH NO CRASHES
- You should modify your program not to make the sim crash even if that meaning to disable certain features like PBR on vehicles. I will be more happy not to have PBR & live a crash free sim experience.
We won't modify GSX just because you don't understand how to manage your settings. In addition to that, P3D V5 works BETTER with PBR, not worse so, your suggestion doesn't make any sense. There's a whole new class of bugs that appear ONLY with non-PBR objects, so we won't do that.
- You should agree with the statement that "GSX is not fully compatible with P3D or may cause issue when using other 3rd party addons".
I won't, because GSX is clearly fully compatible with P3D V5, and everybody can see that ( thanks to the Trial ) so no, it's not as if we are hiding anything.
Oh another thing i forgot to mention. You said your product worked flawlessly since 2015? I remember when LM used to give micro updates. The sim won't even load without updating coutal engine. How we were so certain? Disable coutal engine from addon manager then the sim would load. We had to wait days for the update to come before we could even open our simulator. So yeah your product always had issues. It's high time you listen to customer problem instead of arguing with them which will result in going no where.
And you are sadly mistaken, again. You must have heard somebody discussing about "the Couatl engine" without having the slightest idea of what it is and what it does. Couatl, as an .EXE, is NOT related in any way to the version of the simulator, which I guess this is what you mean when you say "LM used to give micro updates". Couatl it's just a Simconnect client, so it cannot do anything dangerous to the sim, it simply can't, because he doesn't have access to the simulator memory, like a .DLL ( or a .GAU gauge ) can.
Years ago, when the P3D SDK was less complete than it is now, we USED to require an update of our "Addon Manager" ( that is BGLMANX.DLL ), because we required to access data that couldn't be accessed in a documented way so, each time P3D had an update, we had to update the Addon Manager .DLL ( NOT Couatl!! ), otherwise it would surely crash the sim, since it used to access memory directly to get data it couldn't get in any other way.
This is not any different than any other 3rd party .DLL that STILL does direct memory access, so it MUST update the simulator exact build. FSUIPC, EzDoc camera, Active Sky, FSUIPC, are all examples of modules that will crash the sim if there is a "micro-update" if they don't support it exactly.
With P3D V4, since the SDK has way more features, so we don't have to do that anymore, and the 64 bit version of the Addon Manager is NOT dependent in any way from the simulator version like the 32 bit version was. Do you recall having to wait one of our software updates, just because LM released an "hotfix" ? No, of course, because the 64 bit version of our Addon Manager .DLL doesn't do ANY hack in memory anymore. It used to, and it still does in FSX, but not in P3D4 or 5.
Until you fix your product i am going to continue using Ground Crew X to live a crash free sim experience.
There's nothing to fix in GSX, as being proven so many times. Of course, a product with less objects, less feature, and a visible worse quality of textures and animation, will likely work better if you are not prepared to tone down your settings. But don't worry, if you keep your settings as they are and don't update your hardware, something else will crash your sim.
-
There's nothing to fix in GSX, as being proven so many times. Of course, a product with less objects, less feature, and a visible worse quality of textures and animation, will likely work better if you are not prepared to tone down your settings. But don't worry, if you keep your settings as they are and don't update your hardware, something else will crash your sim.
Yeah proven with not the same settings,airport or even aircraft. Are you trying to say i now need to buy RTX 2080ti just to be able to run your product?
something else will crash your sim
Or i can say that my sim will never crash if i don't run GSX. Under any scenario using the same hardware specially soundcard & gpu. Just had 3 flight without any crash using GCX.
You can keep arguing with me all day long. My statement will remain same:
-Your product GSX is not fully compatible with P3DV5.
- You can't ask customer do a vanilla test. Since you claim that your product works at any airport regardless of it being default,3rd party. It's your responsibility to find out if any specific airport is causing GSX service to cause a CTD.
-I am declining your video since it failed to show the major following scenario:
1. It was done using an FSDT developed airport.
2. It was done using an different aircraft.
-
Yeah proven with not the same settings,airport or even aircraft. Are you trying to say i now need to buy RTX 2080ti just to be able to run your product?
Wrong again, as usual. You should learn to use your settings, because with 8GB you CANNOT use "all sliders to the right".
Or i can say that my sim will never crash if i don't run GSX. Under any scenario using the same hardware specially soundcard & gpu. Just had 3 flight without any crash using GCX.
Because you simply don't understand that, a bit of memory spared because of the graphically inferior product ( which only shows pushback, not a whole fleet of vehicles ) might have been just what you need to use your limited VRAM, casued by your insanely high settings, which are wrong for you hardware.
You can keep arguing with me all day long. My statement will remain same
Your statement has been proven wrong, over and over. You embarassed yourself on Avsim, trying to "get help", and users pointed you out how wrong you were. So you are back here, to prove what ? NOBODY has reported your kind of crash, everybody is using GSX with P3D V5 happily, and everybody knows that just putting all your sliders to the right
-Your product GSX is not fully compatible with P3DV5.
It obviously is. And everybody can confirm that, and the more you keep repeating it, the more you embarrass yourself, if the one suffered on Avsim, where they had to lock the topic exactly because YOUR attitude of not wanting to do a vanilla test, which many users suggested as well.
You can't ask customer do a vanilla test. Since you claim that your product works at any airport regardless of it being default,3rd party. It's your responsibility to find out if any specific airport is causing GSX service to cause a CTD.
Wrong, again. I can surely ask you to do a vanilla test, and it's your fault if you are not prepared to do it, and I'm sure it's because this will PROVE to you the GSX DOESN'T CRASH THE SIM, what crashes the sim are your unreasonable expectations of being able to use P3D V5 with "all sliders to the right" with an 8GB card, something everybody already has figure it out, except you.
1. It was done using an FSDT developed airport.
Which is bigger and more detailed that the airport you used. The point should be obvious.
2. It was done using an different aircraft.
Because I couldn't use the PMDG 747 and I needed an airplane that can be installed in P3D V5 ? I'll post a video with the PMDG 747 on a non-FSDT airport soon enough. What you'll say then, it's not "valid" because I haven't use your airport ?
-
It obviously is. And everybody can confirm that, and the more you keep repeating it, the more you embarrass yourself, if the one suffered on Avsim, where they had to lock the topic exactly because YOUR attitude of not wanting to do a vanilla test, which many users suggested as well.
I am not embarrasing myself at all, you are. It just shows how ignorant you are as a dev. Need proof. Here you go. I am not the ONLY ONE. Enjoy that how dissapointed your customers are that they are not even bother to post on your forum to get the product you sell fix.
Which is bigger and more detailed that the airport you used. The point should be obvious.
The point is not obvious. In software anything could cause any software to crash. "The sim crashes due to memory exaustion"- Get this thing out of your head for a sec & think that what other thing could cause GSX to crash. Maybe a scenery conflict? Maybe an scenary invironment conflict? Maybe afcad issue?
Because you simply don't understand that, a bit of memory spared because of the graphically inferior product ( which only shows pushback, not a whole fleet of vehicles ) might have been just what you need to use your limited VRAM, casued by your insanely high settings, which are wrong for you hardware.
Maybe inferior product but it doesn't cause the sim to crash.
Wrong again, as usual. You should learn to use your settings, because with 8GB you CANNOT use "all sliders to the right".
Wrong again. My settings are perfectly tuned & crash fail safe tested without using GSX service.
-
Need proof. Here you go. I am not the ONLY ONE. Enjoy that how dissapointed your customers are that they are not even bother to post on your forum to get the product you sell fix.
I edited your post, because it contained the usual Facebook nonsense even if, in the same post you said it's "proof", there WAS a SANE comment which told you what you didn't wanted to hear from me, that in your video your AUDIO stuttered, so it was the audio that made the sim crash.
The point is not obvious. In software anything could cause any software to crash. "The sim crashes due to memory exaustion"- Get this thing out of your head for a sec & think that what other thing could cause GSX to crash. Maybe a scenery conflict? Maybe an scenary invironment conflict? Maybe afcad issue?
And how, exactly, an "AFCAD issue" or a bug in a scenery, has anything to do with "GSX crashing P3D V5" ? I show KORD V2 because:
- I'm sure it's compatible with P3D V4 and V5.
- It's bigger and much better looking than your airport.
Maybe inferior product but it doesn't cause the sim to crash.
GSX doesn't crash P3D V5, regardless how many times you repeat it. P3D V5 can crash because memory exhaustion, and this is very well known. Memory is taken by the COMBINATION of all your installed add-on and your settings ( mainly )
Obviously, if you replace a product that does many things and display many objects, with one that does less things and diplays less object, it will use less memory, so you might be able to use it even with your unreasonably high settings.
Wrong again. My settings are perfectly tuned & crash fail safe tested without using GSX service.
But since everybody here, and on Avsim too, told you they can run the PMDG 747 with GSX in P3D V5 with no crashes, this is clearly not the case so yes, you are wrong. In any case, here's another video showing:
GSX with the PMDG 747, at Aerosoft EDDK, in P3D V5, working flawlessly
I'm sure you'll now say Aerosoft EDDK "doesn't count"...
-
With my last video, I think there's nothing left to say, I proved to you GSX works perfectly with P3D V5 and a detailed 3rd party airport, that's abundantly clear now. Topic is locked.