Products Support > GSX Support FSX/P3D
P3Dv5 CTD with FSL A320 **SOLVED**
virtuali:
Also, after looking at your video, I'm 100% sure it's NOT GSX, and it's easy enough to recognize it:
You wrote the CTD happened when the jetway "touches". Well, it's NOT happening when it touches, it's happening a few seconds BEFORE, when it's still in the middle of its movement.
And, at this time, GSX is not doing ANYTHING! On a scenery that comes with its own SODE jetways, meaning they are NOT created by GSX, the sequence of operations works like this:
- SODE has communicated to GSX a list of jetways created by SODE when you entered the airport, so GSX will know it shouldn't create any jetways there.
- When you select the jetway from GSX, GSX will communicate to SODE the airplane door coordinates, according to GSX config for that airplane, and then will ask SODE to move the jetway.
- During the ENTIRE jetway movement, SODE is controlling the jetway by sending commands through Simconnect, and GSX is only waiting for SODE for a message indicating "I've docked the jetway".
- The message from SODE will come AFTER the jetway hood animation has completed, but your CTD happened BEFORE that so, clearly, it couldn't possibly be GSX, that was still waiting for SODE, while SODE was animating the jetway.
So, the only thing your video has proved, is the CTD happened at a time when GSX wasn't doing anything. And, since it work with another airplane, it clearly can't be an issue of communication between GSX and SODE, because this system is proven to be reliable.
Also, you started your video by saying you don't have any add-ons other than GSX and FSL. Well, that's clearly not the case, since your P3D title bar shows you have Wideserver running, and the red name of your main window says the camera is from Chaseplane, so you have at least these two running, according to what I can see.
DVA12924:
I said "touching" originally because I was in the cockpit view and couldn't see where it actually was. My fault. What I do not understand is why does the same jetway work when not called by GSX but directly from SODE but does not work when used by GSX?
Did you see the video of where the jetway connected fine to the FSL A320 using the SODE menu and not GSX menu? So how can it be SODE? There is something not communicating properly here.
I am not saying that the issue is with ALL users of GSX and FSL A320, I have said numerous times throughout this thread "my system" and even in the OP I said there may have been a change to something over the last year that I am not aware of which is now causing the issues. All I know is that I updated everything when returning to flight sims, and everything worked fine until I tried to attach a jetway to the FSL A320.
I will try with an airport that does not have it's own SODE jetways and see what the result is.
I cannot post this in the SODE support forum because as I said, the jetway connects to the aircraft fine from the SODE menu, so this is telling me that SODE is working as it should. I also thought to check if I had updated SODE, but version 1.7.1 from June 2020 is the latest and the version I have installed.
Here is a video at KSAT which is unedited at all and still uses the GSX replacement jetways for the disables default P3D jetways:
https://youtu.be/403UWjtXWOw
virtuali:
--- Quote ---I said "touching" originally because I was in the cockpit view and couldn't see where it actually was. My fault. What I do not understand is why does the same jetway work when not called by GSX but directly from SODE but does not work when used by GSX?
--- End quote ---
I don't know, because I don't know if SODE does something different at that time. The only SURE thing, is GSX is not doing *anything* while the jetway is still moving.
--- Quote ---I am not saying that the issue is with ALL users of GSX and FSL A320
--- End quote ---
A more accurate description of the issue would instead being it's only happen to you, and nobody else.
--- Quote ---All I'm trying to do is figure this out. I don't care to argue any longer so can you PLEASE provide some support in what I need to be looking at to try to resolve this?
--- End quote ---
Try with an airport with GSX jetways, which still are SODE, but created by GSX and animated by SODE.
DVA12924:
--- Quote from: virtuali on May 04, 2022, 12:41:20 pm ---Try with an airport with GSX jetways, which still are SODE, but created by GSX and animated by SODE.
--- End quote ---
Please refer to the rest of that post which you ignored that has that test along with a video. Perhaps if you spent less time trying to belittle and degrade people and more time looking at what is provided to you would have seen that already. Here is the link again:
https://youtu.be/403UWjtXWOw
You keep saying that GSX is not doing anything during that time. But we know already that using SODE menu to call the jetway does not cause CTD (in a video above you probably ignored) but when using GSX it does. So if eliminating GSX takes away the CTD, then you cannot say that GSX does not play a part in the problem in some way. I cannot say if the problem is how GSX is sending the info to SODE, or if it is how SODE is sending the info to GSX, or how either program recieve the data from the other, but either way, I did not code either program so therefore cannot say where the disconnect is - but regardless if you take GSX out of the equation, then the problem does not happen so therefore GSX absolutely MUST play a part in the CTD in some way or another. That is why we turn to those who DID write the code so we can attempt to resolve the problem. I'll say it again - Calling the jetway using the SODE menu directly does not cause any issues at all, it is only when the jetway is called from GSX - that right there should tell you that SODE is not the problem alone, but perhaps how the 2 programs are interacting with each other on this particular aircraft. Where to look to see if that is the case is where I must turn to you so you can ask me to try doing things to identify the problem. If it will make you feel better, I can post on the SODE support forum and show the videos to them that using SODE and bypassing GSX works just fine but Umberto at GSX insists it is not a GSX problem and has nothing to do with the CTD, despite no CTD happening if not using GSX.
Now that you have been provided for a 2nd time the video link showing the test you requested, what would you like me to try now?
virtuali:
--- Quote from: DVA12924 on May 04, 2022, 06:13:46 pm ---Please refer to the rest of that post which you ignored that has that test along with a video. Perhaps if you spent less time trying to belittle and degrade people and more time looking at what is provided to you would have seen that already. Here is the link again:
https://youtu.be/403UWjtXWOw
--- End quote ---
I didn't checked both videos but yes, they indicate the problem always happens while the jetways is moving, when it's completely outside GSX's control. In fact, this video further proves the crash is NOT caused by GSX, because it makes the FIRST VIDEO I posted way more relevant, because there I used the FSL on a default airport using GSX jetways.
So, while before we could have *some* doubts, because you were using a 3rd party airport with its own SODE jetways, and I had a default airport with GSX/SODE jetways, this 2nd video of yours is made under the same conditions of mine, so at least we can be sure the problem is not GSX, but something ELSE you have installed, and I don't.
--- Quote ---if you take GSX out of the equation
--- End quote ---
You said it doesn't happen with any airplane other than the FSL A320 so no, on YOUR system at least, even taking the FSL out of the equation is another way to solve the crash. Does this means the FSL is the cause ? Yes, by your own reasoning, but then it should happen to everybody using the FSL, so no.
--- Quote ---You keep saying that GSX is not doing anything during that time. But we know already that using SODE menu to call the jetway does not cause CTD
--- End quote ---
There's an easy explanation for this. As I've said, I don't know exactly what SODE does while it's moving the jetway and how it calls GSX back but, if SODE had an issue ( more likely, something you have installed is causing a conflict somehow ) just before it needs to call GSX back, this can mislead you "GSX has a part in it" JUST because SODE needs to do something it normally doesn't do, that is calling GSX back to tell the jetway has docked, which it likely doesn't do when the jetway is called from its own menu.
Of course, we know the communication between GSX and SODE always work, you said it yourself you don't have any issues with any other airplane, but that doesn't mean I'm sure it's the airplane. In fact, I'm quite sure it's not, otherwise it would crash with MY FSL as well.
So, the only possible explanation is a combination of FSL + GSX + SODE + something else you have installed and I don't, that somehow is disrupting the communication between SODE and GSX.
Have you tried checking the SODE error log with the SODE platform manager while this happens ? Maybe it can tell you something.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version