Products Support > GSX Support FSX/P3D

P3Dv5 CTD with FSL A320 **SOLVED**

(1/6) > >>

DVA12924:
Forgive me if this was already address somewhere in the thousands of threads here. Using P3Dv5.3.17.28160, latest GSX live update, and Imagine sim KATL. Yesterday I used GSX to fly into KATL in the CapSim B757 and deboard without issues. Today when I attempt to load up the FSL A320 at the same parking position in KATL, GSX menu will pull up, does not read correct "pax number (based on aircraft)" because I put in 148 pax and cargo in the FMS and GSX pulls up 20 pax, GSX allows me to select the jetway to the desired door and then begins to move the jetway. Immediately when the jetway would be done moving to dock with he door, P3D freezes and then a few seconds later a complete CTD of P3D. Since I did not have an issue at all when arriving at KATL at the same parking position but different aircraft, I think it is safe to rule out the scenery or aircraft.

As I said in a prior post about a different topic, I have been away from flight sim for almost a year and with everything being updated, it is possible that I may have missed a simple change in settings in either GSX or FSL A320 to allow the 2 to function properly now. I have not changed any settings on anything, only updated to latest versions, and everything worked without issues the last time I used the FSL A320 over a year ago.

virtuali:
It's probably best not to start a thread with such title before being sure GSX is really the "cause" of a problem. Especially when you seem to draw the wrong conclusion from your own report:

"Since I did not have an issue at all when arriving at KATL at the same parking position but different aircraft, I think it is safe to rule out the scenery or aircraft"

No, it's not safe to rule out aircraft. In fact, from your own report, is still possible the problem might well be the aircraft, of just the way you are using it.


--- Quote ---GSX menu will pull up, does not read correct "pax number (based on aircraft)" because I put in 148 pax and cargo in the FMS and GSX pulls up 20 pax
--- End quote ---

GSX IS reading the number of passenger from the aircraft, it's just the aircraft is telling GSX you have 20 passengers.

The reason why I'm 100% sure this is the case, it's because I know the FSL A320 is explicitly setting 20 passengers, when it doesn't know what to set. It was a number we suggested to FSL, because they wanted a way to prevent getting the small Van, when the user didn't set the payload correctly or not at the correct time or not in the correct way so, regardless of the situation, when the FSL doesn't have enough information about the Pax number, it will set to 20 by default, which is slightly higher than the maximum allowed for the Van, so you'll always get the Bus no matter what.

So yes, GSX is doing what it's supposed to do: reading the passenger number from the airplane, you only need to understand why FSL is setting the GSX variable to its default value ( the FSL default, for GSX, the default it's 0, if it's not zero, it means the airplane has set it, because is being reset to 0 each time a new plane is loaded ), instead of the correct one.

Of course, before posting, I checked it, couldn't reproduce it, and made a video:

https://youtu.be/sSTLRYvSLDM

As you can see, I had 93 passengers set in the ATSU, some cargo, called GSX, which confirmed 93 passengers, and after the jetway moved, Deboarding started normally. I don't have any add-on for KATL, so I used the default version but, since you said yourself we can safely exclude the airport ( and I think we can, since if it was a problem with GSX at that airport, it would happen with every airplane ), it's likely there must be something wrong in the communication between GSX and the A320, but I couldn't reproduce it.

DVA12924:
I don't think the title is inaccurate. I'll explain it again:

1. Using GSX with Captain Sim 757, ARRIVED at KATL, de-boarded without any issues.

2. Closed sim and all addons/eternal sim programs and planned next flight.

3. Using GSX with FSL A320, loaded up at the exact same gate I had previously arrived at, loaded data into ATSU, called GSX to start boarding, immediately froze and then CTD when GSX should have given the message that boarding had started as the jetway finished moving.

I was also able to use the FSL A320 without GSX with no issues - with all addons and programs I use for every flight active except GSX - parked at the gate, loaded pax and cargo in ATSU (verified with VA external ACARS system which reads the pax and cargo data from the aircraft), taxied out to runway, took off and flew for 20 minutes after take off with no issues at all. This should easily rule out the aircraft, scenery, and other addons and programs.

So by process of elimination:
Aircraft - no issues without GSX being used - no CTD - not the cause of CTD
Airport scenery - no issues with GSX upon arrival - no CTD - not the cause of CTD
Other addons I use for P3D including external programs - all worked with GSX and other aircraft in prior recent flights - no CTD - not the cause of CTD
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.
So the only program that caused CTD was when GSX was bringing the jetway to the aircraft. How is the title wrong then? The CTD is specific to ONLY when using GSX with FSL A320. No conflicts with any other aircraft or any other addon. I fly with a virtual airline with an external ACARS program that was reading the data I put into the aircraft ATSU without problems. So I know that the data is there.

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.

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. The issue is that there is a CTD caused by GSX when the jetway is reaching the aircraft in boarding. Despite being away for a year, I still follow checklists including for getting the aircraft set up in the sim and loading pax and cargo. These steps were the exact same steps I took when I was previously active and did not cause any CTD with GSX and the FSL A320. This is why I stated that perhaps GSX changed a way it interacts with the FSL aircraft and is now causing a CTD when previously it had not.

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. Perhaps this can help you figure out where the conflict is and assist in resolving it. But I can say without a doubt that the issues happens ONLY when using GSX, ONLY when using the FSL A320 (I don't have other FSL aircraft to test with), and at ANY scenery. The only common variable for the CTD is GSX connecting the jetway to the FSL A320.

Captain Kevin:
But have you tried using GSX on the A320 without doing it through the airplane.

DVA12924:

--- Quote from: Captain Kevin on May 03, 2022, 01:26:10 pm ---But have you tried using GSX on the A320 without doing it through the airplane.

--- End quote ---

What are you asking? I open and use GSX from the GSX menu (Ctrl+F12 on my system). How else would you use GSX?

Navigation

[0] Message Index

[#] Next page