FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Plexi1 on March 23, 2012, 02:26:07 pm
-
I am experiencing a new problem since GSX 1.3, deboarding never ends because it always waits for bagagge unloading to end but it never ends. I can see the bagagges being unloaded onto the bagagge vehicles, the vehicle drives away and thats it.
-
Have the same problem, this with the new loaders. I have to do a reset to clear it.
-
Had juyt one flight with the NGX, but there this happened to me, too ...
Could only cancel GSX
-
I had same problem, but after boarding. boarding finished, the front baggage loader on the NGX backed away, but didn't leave, the aft one remained, and then the GSX screen said boarding completed, waiting for baggage UNloading.
-
Same thing as Buggsy.
I had skipped initial deboarding and started with catering, then went to boarding, FWIW.
I reset GSX then pushed back....
-
Same here with the PMDG MD-11.
Joe
-
I think I am experiencing related problem. I started with fuel request. That went OK. Then I requested Catering and that seemed to be OK but when I requested passenger boarding I noticed first off that one sound track says something that sounds like "emolia". What does that mean? Some foreign language? But I digress...
After passengers were loaded I received a text accross the screen stating, "Passengers Boarded. Baggage unloading in progress." I noticed that front baggage truck had backed away but rear one was still at the cargo door. I requested pushback and as soon as I chose the direction, I noticed that baggage was then being unloaded from the rear cargo hold even though all doors had already been closed. (The aircraft was B737-800wl and airport was VECC stand with no jet bridge). I restarted GSX and tried it again from the point of "request boarding" and this time all seemed to proceed correctly but again after boarding had concluded I received the same erroneous text message but this time both trucks had backed away and I was prompted to close Cargo and Passenger entry doors.
I will try to duplicate the first scenario but clearly an error in the conclusion of boarding text message is indicated.
Craig
-
Don't worry about the "Passengers Boarded. Baggage unloading in progress", this is just text wrongly placed, not an indication of problem in the program.
-
I had skipped initial deboarding and started with catering, then went to boarding, FWIW.
Thanks for the info. The problem actually occurs only in this case. If you don't skip deboarding or if you skip catering, it works.
I had same problem, but after boarding. boarding finished, the front baggage loader on the NGX backed away, but didn't leave, the aft one remained, and then the GSX screen said boarding completed, waiting for baggage UNloading.
The aft loader didn't back away because it is still waiting for the baggage train. It's the train that is stuck. By the way, the loaders won't leave the parking in any case, they just go back to their initial position on the parking. As for the "baggage unloading" message, well... it's just a wrong cut&paste.
I'm on it. Will be fixed shortly in the next live update.
-
the problem here is not the text but the cargo loader, it stays attached to the plane and does not back off, tested with the CLS MD-81
-
i also noticed this with the captain sim 767, the loaders went into position and then the front cargo train came and loaded the carts very well then the train went back to its parking spot but the rear train never came to load the carts, so the front loader backed up after loading and the rear loader stayed in position and i got the message, " passenger boarding complete. Baggage unloading in progress" but the second cart like i said never came to load the rear cargo. any ideas why this might have happened? thanks.
-
Got it. Umberto will prepare a Live Update with the fix in a few minutes. Stay tuned.
-
interesting, I hope it fixes another problem I just found also. When I call the catering truck on the CLS-MD81, both belt loaders drive to the plane, the bagagge trucks pass the loaders without holding and drive away and then the catering truck appears. The belt loaders never leave the plane anymore afterwards.
and this not only happens with the MD-81 but with severall other planes also
-
interesting, I hope it fixes another problem I just found also. When I call the catering truck on the CLS-MD81, both belt loaders drive to the plane, the bagagge trucks pass the loaders without holding and drive away and then the catering truck appears. The belt loaders never leave the plane anymore afterwards.
and this not only happens with the MD-81 but with severall other planes also
That is the correct behaviour. It has been like that since the first version of GSX.
-
erm and how do I get the belt loaders to leave the plane ?
and if this behaviour exists since the first version, why can I see catering trucks in the manual without any cargo loaders at the plane ? Even the video on youtube shows the catering vehicle without any cargo loaders.
-
erm and how do I get the belt loaders to leave the plane ?
They'll go away when you'll ask for departure clearance.
and if this behaviour exists since the first version, why can I see catering trucks in the manual without any cargo loaders at the plane ? Even the video on youtube shows the catering vehicle without any cargo loaders.
It was like that since the first *released* version, but the screenshots in the manual were taken when GSX was still in beta and this changed right before release, and our youtube video was made 11 months before GSX was released.
In any case, we already posted a fix, together with other things, as a Live Update.
-
hmm, okay, I had this different in mind, testing the update right now, thanks Umberto
Ha, both loaders now get bagagges and both leave the plane as soon as boarding is completed (this did not work before)
;D
Thank you very much :)
-
erm and how do I get the belt loaders to leave the plane ?
and if this behaviour exists since the first version, why can I see catering trucks in the manual without any cargo loaders at the plane ? Even the video on youtube shows the catering vehicle without any cargo loaders.
The loaders will leave the plane after boarding or if you ask for departure. The video on youtube was done with a pre-release version that didn't have this feature, AFAICR.
-
yes thanks for clarifying this but my problem was that they did not leave at all, when boarding was complete, the loader just stood where it was and when I requested departure, it told me that it was waiting for the boarding to finish, which never happend and the only way to solve this was to reset GSX, but now it works :)
-
yes thanks for clarifying this but my problem was that they did not leave at all, when boarding was complete, the loader just stood where it was and when I requested departure, it told me that it was waiting for the boarding to finish, which never happend and the only way to solve this was to reset GSX, but now it works :)
+1.....I had the same problem at YMML Gate E3 last night. Had to reset to get rid of him just so "Pushback" could be called and activated.
Rgds,
-
Don't worry about the "Passengers Boarded. Baggage unloading in progress", this is just text wrongly placed, not an indication of problem in the program.
Actually it's not just a text problem! What's happening is when I'm deboarding the loaders unload the train leaves, (The loader stays as it should) and it never completes. If I try to start the catering process, it tells me to wait until the deboarding process finishes, and no catering trucks ever appears. The problem still exists after today's live update.
Thanks
Tom
-
I also have this issue.
The other Issue i have that now in Australia you have introduced Virgin Australia and Jetstar which is great! but I have three different companies servicing my plane at one time (eg fwd baggage loader is Jetstar and the aft loader is VA while Qantas is the air stairs).
-
Actually it's not just a text problem!
I repeat and confirm the the message problem WAS just a wrong text, so it was just a cosmetic issue, not an indication of the problem, but I haven't said there wasn't any *other* problem, because obviously there was, otherwise we issue the update ? I only said that, so people won't keep reporting it as an hint how what the problem could be, because THAT was just a wrong label.
What's happening is when I'm deboarding the loaders unload the train leaves, (The loader stays as it should) and it never completes. If I try to start the catering process, it tells me to wait until the deboarding process finishes, and no catering trucks ever appears. The problem still exists after today's live update.
It doesn't happen here, I can see the deboarding completing normally, and it worked even before the update. Before the update, the problem happened only if you selected catering first, then boarding.
Since I can't reproduce it, please describe exactly your sequence of operation and, airplane used, airport and gate.
-
i have the same problem. If you debord the bagage debording never ends and you can not start catering. Also if you board , bagage loding never ends and you could not start pushback, you get the message bagage loading is still in progress and you have to wait for other services to complete
-
It doesn't happen here, I can see the deboarding completing normally, and it worked even before the update. Before the update, the problem happened only if you selected catering first, then boarding.
Since I can't reproduce it, please describe exactly your sequence of operation and, airplane used, airport and gate.
-
A question to all of you having this problem: have you installed the PaintKit ? If yes, it's possible this is the issue: the PaintKit has been updated too, so you need to download it again and install it.
Note that this will overwrite any customization you made so, it's best if you backup all your customized sim.cfg files before installing the updated Paintkit.
-
A question to all of you having this problem: have you installed the PaintKit ? If yes, it's possible this is the issue: the PaintKit has been updated too, so you need to download it again and install it.
Note that this will overwrite any customization you made so, it's best if you backup all your customized sim.cfg files before installing the updated Paintkit.
I checked it with the paint kit but the problem is still there. I use a projectAirbus A321-232 and the problem was at Miami (KMIA) and La Guardia (KLGA). I think there is a problem with the rear cargo loader because it the load is finished the front cargo loader leaves the aircraft but the rear one still stands on the aircraft.
-
I had this problem with the CLS-MS81 at Boeing Field Gate22, the front loader left the plane but the rear one just stood there and waited but since the update yesterday, this works for me now
-
If the cargo loader doesn't leave is NOT a problem. Is it supposed to remain there, in order to be sure it won't interfere with the catering approach path, which might happen if it returned back to its starting point as soon the deboarding is finished.
So, you shouldn't assume deboarding doesn't end, just because you still see the loaders, because only the train is supposed to leave, the loader will leave only when you ask for pushback clearance.
It always been like this, even before the update, the only different it's that before the update there was only the rear loader, but it stayed there too even after deboarding.
-
If the cargo loader doesn't leave is NOT a problem. Is it supposed to remain there, in order to be sure it won't interfere with the catering approach path, which might happen if it returned back to its starting point as soon the deboarding is finished.
So, you shouldn't assume deboarding doesn't end, just because you still see the loaders, because only the train is supposed to leave, the loader will leave only when you ask for pushback clearance.
It always been like this, even before the update, the only different it's that before the update there was only the rear loader, but it stayed there too even after deboarding.
okay but the problem is not solved because GSX also told Loading/unloading baggage in progress
-
okay but the problem is not solved because GSX also told Loading/unloading baggage in progress
As I've said, it's not happening here, the deboarding ends just fine so, there must be something specific to your configuration.
Again, please describe *exactly* what you are doing:
- The exact order of operations
- The airport
- The gate used
If possible, try to confirm if it happens on a DEFAULT airplane on a DEFAULT airport, or if there's a difference because, knowing that, might help understanding what's going on in your system.
And, if you had some vehicles customized with the PaintKit installed.
-
If the cargo loader doesn't leave is NOT a problem. Is it supposed to remain there, in order to be sure it won't interfere with the catering approach path, which might happen if it returned back to its starting point as soon the deboarding is finished.
So, you shouldn't assume deboarding doesn't end, just because you still see the loaders, because only the train is supposed to leave, the loader will leave only when you ask for pushback clearance.
It always been like this, even before the update, the only different it's that before the update there was only the rear loader, but it stayed there too even after deboarding.
it would have been no problem for me if it just stood there but I was unable to request clearance because when I did this it was just waiting for boarding to finish which never ended, it works for me now, but not for others as it looks.
-
it would have been no problem for me if it just stood there but I was unable to request clearance because when I did this it was just waiting for boarding to finish which never ended, it works for me now, but not for others as it looks.
What do you mean "it works for me now" ? If you mean "before the update", that's plainly obvious: the update was supposed to fix just that.
-
for me this particular problem was fixed with the update, I just wanted to help explain what happend because some others still seem to have this problem
-
The problem appears to be the rear loader. If there is only one loader the boarding or deboarding process does not clear. Meaning you can't proceed to the next process. If there are a front and rear loader both processes does clear, allowing you to go to the next step, however after the boarding process, the front loader backs away, but the rear loader stays, so when you go to pushback it still is in place and the planes wings and engines hit it.
-
I hadn't flown using the 1.3 update until today. It looks to me like I am also having the problem of the never ending loading. I was using PMDG's 738NGX and PHNL Gate 11. Passenger boarding and the front loader proceeded without problems. However, the rear loader did not complete it's task. When I requested preperation for deboarding, the menu read that it was waiting for boarding to finish first.
-
I think you are confusing the updates: the 1.3 update is one thing, but there was *another* small update after that, which is not applied if you don't check for it, or wait 24 hours since the last update.
I've just checked the described situation at PHNL, Gate 11 with the PMDG 737-800, and boarding ends normally, both loaders go back to their starting positions when they are done. No difference if I start requesting catering first, or go directly to boarding, works in both cases.
-
That was with the 1.3 main update, as well as the live update. I just uninstalled, and redownloaded the GSX installer reinstalled It says it installed version 1.3.1, tried it again and still have the same problem. Yhe problem I' seeing is with the aircraft with loaders (Wilco A330, Captain Sim 767), I haven't tried the 737NGX with 1.3.1 yet. I'll make a video of it so you can see what' happening!
-
I think you are confusing the updates: the 1.3 update is one thing, but there was *another* small update after that, which is not applied if you don't check for it, or wait 24 hours since the last update.
I've just checked the described situation at PHNL, Gate 11 with the PMDG 737-800, and boarding ends normally, both loaders go back to their starting positions when they are done. No difference if I start requesting catering first, or go directly to boarding, works in both cases.
I did not realize there was another update after v1.3. I never got a warning from GSX Live Update, so I will have to look at this and give it a try.
-
I'll make a video of it so you can see what' happening!
There's no need to, it's not very useful having a video, I believe you are seeing that, but to fix the problem, we need to have it here first.
Do you have GSX repainted vehicles ? Uninstalling will not remove them, and they must be updated too for 1.3, if they aren't, it's possible an vehicle from the old paintkit might cause problems.
-
I did not realize there was another update after v1.3. I never got a warning from GSX Live Update, so I will have to look at this and give it a try.
As I've said (and as explained on the manual) the Live Update notification is not immediate as soon as we release it, the automatic notification check is made every 24 hours. If you want to check there's a new update without waiting, you need to explicitly check using the "Check updates" menu option.
-
No I never did install the paint kit. I did install the extra vehicles and liveries update you provided though!
-
No I never did install the paint kit. I did install the extra vehicles and liveries update you provided though!
That shouldn't be a problem, because the 1.3 installer will overwrite them all.
-
Hi Umberto,
I too have the same issues as everyone else. It is somewhat confusing because the user interface is advising of two different services. I have included screens so hoping you guys can sort it out. The UI is advising pax have been deboarded, Baggage unload in progress. Requesting catering service, the UI advises catering service requested. Waiting for deboarding to be complete. As you can see in the screens, the baggage carts have gone. I waited over 20 minutes to see which service would complete and nothing ever did. I ended up resetting GSX and started with requesting catering service and skipped deboarding pax and GSX continued as normal. These screens are of the default 737, at default KCAK. Gates 5 and 3. The screen of gate 5 you can also see one catering truck going outside of the normal vehicle path and drive through the airplane. The other service vehicles do not take that route. They stay within the marked lane you can see in the screens. The last screen is off the multiple livery issue others have reported as well. Hope that is the additional detail you were asking for in regards to this issue. I have installed the latest paint-kit from the product page. However, I have no custom livery's/vehicles as of yet. I also have the latest updates as well.
Regards,
Rob
-
I just did a live update and tested this - working fine here, deboarding completes normally.
-
I think i could be a problem with the airport. I check some airport and bagagge unloading is working at Munich (EDDM) Frankfurt (EDDF) Madrid (LEMD) but it isn't Working at Heathrow (EGLL), Kennedy (KJFK), La Guardia (KLGA), Miami (KMIA), Philadelphia (KPHL).
On every airport i use the AFCAD-Files from Ray Smith
-
Nice theory but I am having the same problem on FSX default airport. I was using the NGX B739 and could not get past the deboarding sequence. When I started with Catering-Fuel-Passenger boarding sequence, it completed sequence but left the rear conveyor in place and did not move the left stairs far enough to the left to allow clearance for the wing on pushback. I closed and restarted FSX and tried the entire tests again with same results using same airport and aircraft
HOWEVER, when I switched to a NGX B738(wl) version (but using same airport and parking spot) and started the sequence from "deboarding", it all completed correctly. When I boarded passengers, the boarding completed BEFORE the baggage trains even arrived! The message: "Boarding completed. Baggage loading in progress" appeared and true enough the baggage WAS still loading this time. When completed the trains moved back and the message "Boarding completed" appeared followed by BOTH conveyors moving back this time. Only problem still present: rear stair still not far enough to left to allow left wing clearance on pushback.
So, you think it is airport problem...my test indicates it is aircraft type problem. Either way it IS A PROBLEM and needs fixing!
Craig
-
HOWEVER, when I switched to a NGX B738(wl) version (but using same airport and parking spot) and started the sequence from "deboarding", it all completed correctly.
It completed because that is the correct sequence, notice how deboarding is above catering in the menu? There isn't a problem to fix, even real world aircraft deboard before catering and fueling.
-
The problem was NOT with the sequence! It DID NOT WORK PERIOD with the B739. It never finished deboarding! But, my point was that it DOES WORK correctly when I switched to the B738 and it does so even when I start with catering. And BTW, in my 30+ year airline career I never had to "deboard" passengers before I began my first flight of the day. They did not sleep overnight in the plane! LOL :D
-
And BTW, in my 30+ year airline career I never had to "deboard" passengers before I began my first flight of the day. They did not sleep overnight in the plane! LOL :D
Now tell that to FSX, LOL It always starts with engines running, either at the active or a gate, so you're either about to take off or at the gate about to shut down. Even your aircraft.cfg file says you're full. :D
-
Obviously that is the way you choose to use it. But for anyone who wants to simulate RW situation, the option to start at a gate with all engines off and cold and dark has always been available. You just need to save the file after you have shut down. Why would anyone start with the engines running and on the runway? The whole point of sophisticated simulations like the ConcordeX, PMDG B744/NGX, etc., is to simulate the complicated system checks and startup sequences that we do in RW. But we are digressing here, Hamilton. That is not the point of the OP. We have a problem and it is not dependent on the sequence. If you notice the title of the original post. It implies that the OP DID start with deboarding but the sequence "locked-up" and would not allow to continue to next step. The same happened with my tests. BTW, the manual states that sequence can be started other than at "deboarding" and was the case prior to V1.3.
Craig
-
Ok I ran a whole slew of tests and this is what I found.
1. All aircraft, fully supported by GSX (ie: PMDG 737-800NGX, CS-767) work fine, except at PHNL (Default/Afcad) for some reason the rear cargo loader/conveyer doesn't back away, after boarding complete. I have a feeling it has something to do with the size of the gates, their large.
2. If the aircraft has a gsx.cfg file, same result, although I'm having other issues with setting coordinates, on other doors with it. (I'll post in another thread the coordinate issue.)
3. Any aircraft that is not supported, and uses the FSX aircraft.cfg are the ones that deboarding doesn't complete, The aircraft I tried this with is the Wilco A330-200 (Merged with Thomas Ruth's external model After this test, this was the model I created the GSX.CFG file that worked). The Overland aircraft Boeing and Airbus, and the 737-900NGX, which I had thought was supported like the 800NGX, but it isn't. What's also strange is I don't even get the conveyer belt trucks with that one, just 1 tram, which goes the motions, after it pulls away deboarding is still in process.
-
I just did a live update and tested this - working fine here, deboarding completes normally.
Just checked for a live udate. GSX advises update already installed. Thinking of uninstalling and reinstall using the full installer package instead of the add-on mgr to see if this issue can be resolved. Previous version was flawless.
Rob
-
Hi All,
I had the same problem with the v1.3 yesterday after having done the Live Update. What was curious was there was no updated manual installed, still v1.2. Also when I looked in Control Panel, GSX still reproted an old version.
So I went to the full installer and everything works fine. Even the manual was updated! Before I had problems at both Zürich and KJFK but all is resolved.
The ULD animation is really cool!
Cheers
Mark
-
I tried this and it did not work for me. I uninstalled everything related to GSX and FSDT. I downloaded the full package from the product page and reinstalled. Still stuck on the deboarding passengers/baggage unload in progress. Left it there while I went to work thinking maybe it would complete at some point in the day. Just got home and we are still deboarding pax and unloading bags. Don't have a clue what to do at this point.
Rob
-
I realized that I had installed the UPDATES but not the UPGRADE to 1.3. I had downloaded the wrong file. Wish they had just put the link in this support forum as others do, but... Point is I now have completely uninstalled and reinstalled using the correct upgrade installer and not only does the -900 not complete the baggage handling but now I have the same problem on the -800 that I never had before. Umberto was working with me throughout the day but his tries were all successful using same model and same locations with all different load weights. He also claims that the trains vary the number of carts they haul depending on the load. In my experience I have never seen anything but always 3 carts behind each train. Now I do not know what to do either. Someone on the Dreamteam must know what "triggers" it to move past the "baggage loading/unloading in progress" point. In the original, the baggage handling always completed within a minute or so and that was announced: "baggage loading/unloading completed" and the wait was for the passengers. Several complained that usually the wait should be for baggage handling to make scenario more realistic. I agree, but whatever they tweaked is causing it to lock up on my machine and from this string I can tell that others are having the same problem. Why Umberto is not able to replicate it is beyond my understanding. To his credit he has been trying all day with me. The program at this point seems unusable. I am debating whether or not to return to the RTM version. It seems it was one of the update fixes that introduced the problem. It was not present (to my knowlege) with the original RTM release. Of course we would no longer have the double loaders or the bulk loaders.
-
I realized that I had installed the UPDATES but not the UPGRADE to 1.3
There's no such thing as an 1.3 upgrade. The only GSX installer is the full 1.3 installer. The only update it's the Stand-Alone Addon Manager, and the end result would be exactly the same: updating you to the most current version.
I had downloaded the wrong file.
You can't download the wrong file. You can, instead, *ignore* the prompt to download the Stand-Alone Addon Manager that is suggested by the Live Update program.
Wish they had just put the link in this support forum as others do, but...
When there's a major update, which was the case with the 1.3 update, when you select the option to update, the Live Update will launch the browser for you, already pointed to the Stand-Alone Addon Manager download page so, it's even easier than having you to look for the same link on the forum.
Point is I now have completely uninstalled and reinstalled using the correct upgrade installer
Since an upgrade installer for 1.3 doesn't exists, I wonder what you installed. Or, do you mean the Stand-Alone Addon Manager ?
and not only does the -900 not complete the baggage handling but now I have the same problem on the -800 that I never had before
Both the -800 and -900 are working.
He also claims that the trains vary the number of carts they haul depending on the load
That's what they do.
In the original, the baggage handling always completed within a minute or so and that was announced: "baggage loading/unloading completed" and the wait was for the passengers.
This is only dependent on the GSX time settings, that can be changed by users. The *passengers* are controlled by that, but the baggage train aren't.
Why Umberto is not able to replicate it is beyond my understanding
The issue is, several people that posted here said the problem was fixed after applying the current Live Update.
It seems it was one of the update fixes that introduced the problem
The large 1.3 update introduced the problem. But the small Live Update that we posted the day after it, fixed it. I can replicate this situation.
It was not present (to my knowlege) with the original RTM release. Of course we would no longer have the double loaders or the bulk loaders.
That's why they aren't comparable at all, the differences due to double loaders are simply too many, to be able to point out a specific thing.
But the whole point is, I've made something like 50-60 different test in all kind of strange situations, changing airplane, airport, gate, station load, number of passengers, timings, and I'm still unable to replicate the issue.
-
I agree. I can't understand why the same issues aren't replicated. Something is going on with the update. I had no issues with the previous version. The only thing I have done differently was install the update. I have tried several different scenarios and I can't get any further using default AC with default airports. Here is something to try, I am curious what the results might be. While I was parked at the gate waiting to see if the baggage unload would ever end, I started the engines on the default 737. GSX immediately advised that the baggage unload had completed. The green bar across the top displayed the msg. The pushback tug and belt loaders disappeared. I shut down the engines and called up the UI. It showed baggage unload completed and I was able to continue with the rest of the services. I realize this is totally unrealistic and one should not have to do this, but maybe it might add another piece to the puzzle about what is going on.
Rob
-
I just ran the latest live update (Today) and the problems with deboarding not completing seemed to be resolved now, in addition the 700-900NGX now appears supported. I also checked the issue at PHNL, and that also appears to be corrected!! Thanks Umberto!!
-
That is encouraging. I just reinstalled everything using the full 1.3 install and also the live update and tried -900 and the -800 NGX and neither would complete. I am going to uninstall and reinstall and try again since you now are having sucess. BTW I am using Ultimate Traffic 2. Are you also? Maybe that is the snake in the bush(?)
Craig
-
I have Ut2 also, so I don't think that's it!! Hope you get yours sorted out though!!
-
BTW I am using Ultimate Traffic 2. Are you also? Maybe that is the snake in the bush(?)
I have UT2 installed and usually make tests with it, but I don't normally keep it enabled. However, it would be fairly easy to check this yourself, by simply terminating the UT2Services.exe with the Task Manager, before trying.
We had some issues in the past with UT2 clobbering the Simconnect pipe with so many requests, that a feature we used in KDFW to adjust the terrain that required Simconnect, didn't work for a couple of users because of UT2 for that reason, our module didn't get a change to "talk" with FSX, because UT2 talked too fast...
We sidestepped the issue in a different way for KDFW, by not using Simconnect for that feature but, unfortunately, GSX can't be done without it. But it would be useful to know if this is the problem.
-
Umberto,
If you are still following, I think I might have it. In my situation I am moving the AC back to the "T". (Nose wheel on the "T") When you start a flight or when GSX parks you, It is always forward of the "T". I move the jet back to the "T" to use the jetway. I just ran a test leaving the jet where FSX put it when starting a flight from the gate. In this case I used gate 4 at KCAK. In instances using the 737 and other default AC GSX performed normally. As soon as I moved the jet back to the "T", the baggage unload would hang. I used to do this in the previous versions of GSX without issue but maybe something has changed in v1.3. I hope that helps. I would suggest you re-run your test moving the jet back to the "T". I don't know if that helps the others having issues.
Regards,
Rob
-
That's interesting: how do you move it ? With slew ?
And when, exactly, you move the airplane ? Using slew is supposed to trigger a reset, with all vehicles immediately disappearing.
-
Hi Umberto,
I either use the engine reverse or FSX pushback "shift P". I back the jet up to the "T" for looks and to use the jetway. I start GSX and proceed. I have done this with previous versions with no problems so I didn't think of even mentioning it. My fault......should have explained in better detail. I never thought moving the jet would be the issue. I move the jet back after GSX calls for engine shutdown. When using GSX I use function shift P to back the jet up. When starting at the gate, the engines usually running, so I reverse back to the "T" and then shutdown and start GSX.
Regards,
Rob
-
I think it might be a problem only if you used slew to back up. Reverse thrust should be absolutely safe.
Default Pushback might be a problem, but it should caused issues in the *previous* version since we used to intercept the Shift+P key to call our own pushback instead, but don't anymore since a couple of releases.
But of course, I'm trying that right now, at KCAK, Gate 5 with default A321, moved there using the FSX menu, selected Shift+P to back up on the parking tee, and selected deboarding with GSX, no problems at all.
Can you try the same with the default A321 ? And, please, can you tell me exactly the total cargo load weight ?
-
Maybe you found something: I WAS able to replicate the problem, but *only* with the PMDG NGX and *only* if I backup from the default parking position to the parking tee, using the default Pushback key.
Still don't have the slightest idea why it does that, but at least we have a base to further testing. Will surely give more information tomorrow.
-
I reinstalled again and it offered me only 1 live update and I know there was one immediately after the v1.3 release and some were reporting a new one today. My live-update module says latest is already installed. I think there is another one that is just not occuring yet.
Anyway tried the defautl PMDG -900wl and set payload to empty to replicate one of Umberto's tests. This time since there were no passengers it stopped deboarding within a minute or so. It still sent baggage trains but with only 1 cart each and it did unload bags. The rear train finished and left before deboarding completed and when I received the "deboarding complete. Baggage unloading in progress" message it made sense since the front train was still loading up the last cart. After front train left then within a few seconds the message "deboarding complete" appeared and I was free to select next process. I know this is how it is supposed to work.
I reset GSX and this time put 1/2 payload weight and passengers. This time sent 2 trains with 3 carts each. Baggage finished early while deboarding still in process. When deboarding finally ended I still got the message "deboarding completed. Baggage unloading in progress", but there WAS NO baggage being unloaded so nothing to complete. The message never changed to "deboarding complete" message so I was unable to move to next process.
Is my baggage process ending sooner than it should? Is that what is causing the problem in v1.3. Back in previous before major upgrade the message "baggage unloading completed" would occur as the train pulled away. When deboarding finally finished the message "deboarding completed" would finally occur and I was good to go to the next step.
Umberto, did you lengthen the baggage procedures so that they would still be active AFTER deboarding (or boarding)? If so then the message would indeed make sense but in all me tests (except for payload empty) the baggage routine only lasts a few minutes but the passenger routines take much longer and are still in progress way after baggage routine has completed, not the other way around. Is this normal? From your comments in the B737-900 thread, it sounded as though your baggage routines were lasting longer that boarding/deboarding. If so then it may be a clue to why my process never complete.
BTW, I am NOT moving the aircraft from its position (which is aligned perfectly with the AFCAD footprint since I have modified airport parking in the airports as I fly to them) before I start GSX. How can that be a factor in the completion of the board or deboard sequence?
I realize that you have really put in a long day trying to help us with this crazy problem and it is indeed greatly appreciated. Many thanks.
Craig
-
Good Morning Umberto,
I did as you requested and this is what I have. The first test was with the default A321, Location KCAK: Active runway: Static weather(Fair): Selected daytime 12:30PM. FSX spawned the AC on runway #1 engines running. Called up the GSX UI selected parking Gate 5, no follow me vehicle. Taxied down the runway and turned off on taxi way Bravo almost directly in front of the gate. Followed the director's instructions and parked where GSX wanted the plane to stop and shut down the engines as requested. Unable to use the jetway as the AC is too far forward of the parking "T". I then selected deboarding from the GSX UI. The GSX service vehicles went into action and serviced the AC. GSX completed normally and I proceeded through the menu of options ending with push-back. Ended the flight.
Loaded another flight using the same AC and parameters only this time selecting to start at Gate 5 KCAK. The AC spawned at Gate 5, engines running. I started the flight applying brakes so as not to put the nose of the AC in the building. Using thrust reverse, I moved the AC back so the nose wheel was on the "T". I shut down the engines, opened the main cabin door and activated the jetway. After the jetway was attached, I called up the GSX UI and selected deboarding. All service vehicles appeared, I opened the cargo doors, and GSX went into action. GSX advised that "Deboarding Passengers now, baggage unload in progress". A few moments later, GSX advised "Passengers deboarded, baggage unload in progress". The AC was unloaded, the pallet tug and baggage tug left the AC and thats where the hang up is. GSX would proceed no further. The UI advises "Passengers unloaded. Baggage unload in progress". If you select any other services, the UI responds with " XXXXXXXX requested, waiting for deboarding to complete". Using the options of "Reset Position", or "Restart Couatl" from the menu is the only way of getting things moving again. At this point there are 2 options, One, you can start GSX again this time skipping deboarding and starting with Catering service. GSX will complete normally. Or, I found out you can start the engines again and move the AC back where it was originally spawned forward of the "T". I didn't even close any doors. Start GSX over again and it will complete all services normally. I started another flight same as above, spawning at Gate 5 engines running. This time I shut down the engines and used "Shift+P" to move the AC back to the "T". Again, GSX would hang at the same moment displaying the same messages. I used all default settings and made no adjustments to the radius, deboarding times, and payload/fuel. Something else of note, when GSX would hang, I started the engines. I immediately received a "Baggage unload completed" message from GSX. The only problem being all the service vehicles disappeared. But you could start GSX over again without moving the AC forward starting with catering service and GSX would complete normally. Weight and payload is as follows:
A321
Payload: 14340 pounds
Fuel: 7635.66 gallons
Gross Weight: 159160 pounds
Max Gross Weight: 187392
Max Allowable Fuel: 7790.00
I also performed all the above using the default 737 at KCAK using GATE G3. Same parameters just a different gate. The results were identical. I ran the tests again not using the custom repaint just to be safe.
B738
Payload: 22850 pounds
Fuel: 6830.35 gallons
Gross Weight: 154323 gallons
Max Gross Weight: 155500 pounds
Max Allowable Fuel: 6875.00 gallons
Conclusion: If you leave the AC where GSX wants to park it, or where FSX spawns it when starting from a gate or parking position, one should be OK. This does not usually work. As mentioned in many other posts, most AFCADS are really bad and one needs to move the AC to get the nose out of a building, or the nose wheel back on the tarmac, utilize jetway, etc. GSX was never this precise before. For me, in previous versions I always used shift+P to move the AC back. Depending on type of AC, sometimes thrust reverse was not available or did not work. When I first tried shift+P, I was concerned that GSX would start the pushback process. This was not the case. GSX ignored it, the AC would go back to a visually correct parking position and all would be well. I had no other issues using default, payware, freeware AC. The only issue I had was corrected in the first release with the follow me vehicle. Thats why I was so dumbfounded. GSX was working perfectly until I installed v1.3 Then it dawned on me the other night when you were asking for "precise details" I did not mention moving the AC back to the "T". I would have never thought moving the AC would cause any issues because it's something I have always done using GSX. I hope a little lee-way can be put back in. I hope this helps Umberto. If anything, it's as you said "at least we have a base to further test" Maybe this helps other people reporting this issue. If I can do anything else, please let me know. More than happy to help.
Regards,
Rob
-
Based on your tests, Rob, I did a final uninstall/reinstall without my antivirus just to make sure I was not getting anything improperly installed and then tested default B738 by SPAWNING it at both a gate and a free-stand and then verifying with the AFCAD file for the airport that it was DEAD-CENTER on the footprint. I ignored the jetway and DID NOT move the aircraft in any way. Since the problem was not present prior to v1.3, it is questionable that it is a position problem entirely. But GSX must poll an internal variable to determine when baggage handling has completed. That process became more complex now that TWO loaders must be individually polled. From the different load tests I have run, it seems that when the front loader completes first with passengers still in progress, the program is unable to now determine when the rear loader has completed. If the passenger loading completes first, however, then it correctly waits for the baggage handling to complete and then gives the "completed" message and all is fine. (I have been able to duplicate THAT scenario using a ZERO payload.) If this were a position issue that would not be the case.
-
As I've said in the other identical thread, it doesn't matter if you move the airplane or not, or if you park in the center or not. The only thing that matters is that, due to the relationship between the distance of the rear door and the parking radius, the rear loader find itself outside the parking when it's still loading.
Also, it would be best if you stop posting about the same issue in multiple threads, because the only result is that force me to reply on all threads saying the same things (so no threads ends up unanswered), which doesn't obviously help to speed up the release of the fix.
-
Hi Umberto,
That makes sense to me. Believe it or not, I actually understand that explanation. I read the comments in the other thread as well. I was going to post my other tests results with a few smaller regional jets, but no need for that now. There was more room to move the smaller jets around within the parking area and still have GSX perform normally. I also tested the larger jets at different default airports with larger parking "as defined by GSX" and GSX performed as it should.
CRAUDS: The one thing I didn't change in any test I did at various airports was change the weight or cargo. Hopefully the new live update will take care of your issue as well. Could you post your results here. From what I have read that particular AC is a really nice payware add-on to have.
Thanks Umberto for your time.
Regards,
Rob