Products Support > GSX Support FSX/P3D
P3Dv5 CTD with FSL A320 **SOLVED**
Captain Kevin:
--- Quote from: DVA12924 on May 03, 2022, 01:53:17 pm ---What are you asking? I open and use GSX from the GSX menu (Ctrl+F12 on my system). How else would you use GSX?
--- End quote ---
I am pretty sure the FS Labs A320 has GSX integration, so unless I misunderstood what that meant, I thought it was possible to use GSX without opening the GSX menu on this particular aircraft. I don't own the aircraft, so I can't verify.
virtuali:
--- Quote from: DVA12924 on May 03, 2022, 07:22:07 am ---GSX - caused CTD when calling jetway to FSL A320 in boarding after pax and cargo data put into ATSU - positive CTD - this is the cause.
--- End quote ---
Except it's not, and please stop again to say "GSX is the cause", because it clearly isn't.
If the crash ( which as I've shown on video, doesn't happen here, with the FSL A320 and GSX ) if it's really happening when "GSX calls the jetways", there's another program at play, which is SODE, because GSX doesn't animated jetways, SODE does.
--- Quote ---So the only program that caused CTD was when GSX was bringing the jetway to the aircraft. How is the title wrong then?
--- End quote ---
See above. You forgot SODE, and the aircraft itself. And why you "excluded" the airplane ?
--- Quote ---I was stating that perhaps some time in the last year GSX may have made some adjustment to how it interacts with the FSL A320 which may be the cause of the CTD for me. Since you are the developer, that would put you in the best position to know if that is the case. I do not have access to the change logs over the last year I was not using or updating anything, and therefore cannot say that is the case myself.
--- End quote ---
We couldn't possibly have changed anything in the way GSX interacts with the FSL, or any other airplane, simply because GSX DOES NOT interact with any airplane. All GSX is doing, is publishing some variables the airplane can read, and act with its own code and procedures.
I'll repeat it again: there's no single line of code we wrote that has any knowledge of a *specific* aircraft. Whatever integration is happening, is happening entirely in the airplane own code. The airplane can control GSX, but GSX can't control the airplane, the only rare case in which GSX takes very little control of the airplane, is during pushback.
--- Quote ---The problem here is not that GSX is saying there is 20 pax. I have the settings so that I can change that number if needed.
--- End quote ---
You said it was a problem, I just told you why they are exactly 20, it's the FSL that set that specific default value, to prevent users using it in the wrong way or at the wrong time to ever get the Van. So, whenever you see 20 passengers, it means you are not following some FSL-specific procedure, because (again) it's NOT a value GSX sets by itself.
--- Quote ---The issue is that there is a CTD caused by GSX when the jetway is reaching the aircraft in boarding
--- End quote ---
Nothing in your report tells the crash is "caused" by GSX.
--- Quote ---In your video, I have set the pax and cargo the same way and when the message "[GSX] Airplane with custom Battery and support for Jetway Power Unit." message SHOULD appear is where P3D initially freezes and the followed a few seconds later by CTD.
--- End quote ---
And what makes you think it's GSX that "caused" this ? It might well be the very well known problem of the sim ITSELF crashing due to just the DISPLAY of the message, LM has confirmed they still haven't found *all* issues with HTML5 menus and texts, so there are some situations in which something that display a menu or a text message, results in the sim crashing, for example it might happen because BOTH GSX and ANOTHER add-on tried to display some text at the same time, so it can't always happen, or it can't happen to me, because I don't have any add-on other than GSX and the FSL.
But it's a known fact both menus and texts are still not 100% stable with P3D V5, and since GSX use them a lot, this often misleads users assuming GSX "caused" a crash, when in fact the sim crashed on its own due to its menu/text system ( it's the same system and the same Simconnect call ). It always happen then, if there's a problem with the menu/text system, people always blame GSX, happened so many times in the past, and not a single time it was ever caused by GSX and 100% of the time it was always fixed with a patch by LM. Now it's better than it used to be, but it's still not 100% rock solid.
srcooke:
--- Quote from: DVA12924 on May 03, 2022, 01:53:17 pm ---How else would you use GSX?
--- End quote ---
Have you tried following the ATSU tutorial supplied with the FSL documentation ?
DVA12924:
Video links at end of this post.
If the problem was with SODE, when why would it work without issues in a different airport? Why would SODE also work flawlessly with the other aircraft I fly (Captain Sim 757, Carenado Saab 340, Aerosoft CRJ 900, PMDG 737, PMDG 747, PMDG 777)?
As I stated, I flew the FSL A320 on a test flight and no CTD. The only single thing different from the test flight in the FSL A320 and the CTD is using GSX. So how does that not clearly say that this is GSX and nothing else? CTD happens ONLY when using GSX to call the jetway to the FSL A320 - at no other time do I get any errors, CTD, or any problems at all EXCEPT when I open the GSX menu and call the jetway. I don't know how I can be more clear with this. I do extensive testing before I point the cause to a specific program or addon and I have eliminated everything else except GSX at that particular point in the use. I can also use SODE directly to call the jetway to the FSL A320 (not using GSX) and it works just fine.
With the original flight in the OP, I switched to the PMDG 737 and had no issues at all for the entire flight. So that again shows ruling out SODE, the scenery, GSX with other aircraft, all the addons and programs used during every flight. And again, the FSL A320 test flight was done using every addon and program used in every flight EXCEPT GSX and again there was no CTD. When using GSX with the FSL A320, 5 times in a row at the exact same point (calling jetway) I got a CTD - take away GSX and no CTD.
There is literally overwhelming evidence to support this. I have created 2 videos showing many tests in which you'll see 2 CTD when using GSX to call the jetway from the FSL A320, 1 non-CTD when using SODE to call the jetway to the FSL A320, 1 non-CTD when using GSX to call the jetway to the PMDG 737, and finally the A320 taxi showing that it is not the aircraft itself. I would LOVE to know how you can say it is not GSX causing the CTD at this point when there is the proof that it only CTD when using GSX to call the jetway to the FSL A320.
The videos needed to be in 2 parts because of a 15 minute max timer on recording and switching between planes to load the A320 over and over took quite a bit of time. If there is anything else you'd like me to try to resolve this issue, I'd love to hear it.
https://youtu.be/iMLrzJwQYeI
https://youtu.be/dH6KD3UZA7A
virtuali:
--- Quote from: DVA12924 on May 03, 2022, 07:12:23 pm ---If the problem was with SODE, when why would it work without issues in a different airport? Why would SODE also work flawlessly with the other aircraft I fly (Captain Sim 757, Carenado Saab 340, Aerosoft CRJ 900, PMDG 737, PMDG 747, PMDG 777)?
--- End quote ---
If the problem was GSX, why it would work without issues with other airplanes and airports ? Why would GSX also work flawlessly with the other aircraft you fly (Captain Sim 757, Carenado Saab 340, Aerosoft CRJ 900, PMDG 737, PMDG 747, PMDG 777)?
Your works.
--- Quote ---So how does that not clearly say that this is GSX and nothing else? CTD happens ONLY when using GSX to call the jetway to the FSL A320 - at no other time do I get any errors, CTD, or any problems at all EXCEPT when I open the GSX menu and call the jetway. I don't know how I can be more clear with this.
--- End quote ---
Because there is when SODE starts moving the jetway. So, there are at least three other possible causes: either SODE or, more likely, the P3D MENU ITSELF, or possibly the airplane code that I know for sure does some interception of the GSX menus, but I'm not entirely sure when this happens.
--- Quote ---With the original flight in the OP, I switched to the PMDG 737 and had no issues at all for the entire flight. So that again shows ruling out SODE, the scenery, GSX with other aircraft, all the addons and programs used during every flight.
--- End quote ---
It surely rules out GSX and the other stuff, it doesn't rule out the FSL A320, on YOUR system. There was a reason why I posted a video with it, to show they work together just fine.
--- Quote ---And again, the FSL A320 test flight was done using every addon and program used in every flight EXCEPT GSX and again there was no CTD. When using GSX with the FSL A320, 5 times in a row at the exact same point (calling jetway) I got a CTD - take away GSX and no CTD.
--- End quote ---
Wrong conclusion, again. If the real cause of the problem is another add-on calling the menu or using the text system *together* with GSX, by removing that add-on, you are mislead thinking the cause was GSX, when in fact it was the fact the other add-on was present *together* with GSX.
--- Quote ---There is literally overwhelming evidence to support this.
--- End quote ---
There isn't a bit of evidence in anything you said to support GSX is the "cause". You are keep confusing cause and effect. I don't doubt you have a crash in that situation, but I'm sure it's NOT GSX.
Because, as explained so many times, GSX runs completely external to the simulator, so it's completely isolated from it, this is not really something open to discussion, it's the way Windows works: an external .EXE CANNOT access memory from another process, thus it cannot cause a crash.
--- Quote --- I have created 2 videos showing many tests in which you'll see 2 CTD when using GSX to call the jetway from the FSL A320
--- End quote ---
So videos are now valid as evidence for you ? Then why you don't ask yourself why it doesn't crash on MY video ? FSL A320, calling the jetway and setting the correct passenger number, which was another issue you had.
And, do you think you are the only one using FSL + GSX and calling jetways ? Don't you think, if the problem was really *caused* by GSX, we would have heard of it already ? I checked the FSL forum as well, there's nothing similar reported there. And, when FSL suspect a problem with GSX, they usually contact me to check it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version