FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: Seralia on August 10, 2024, 03:52:56 pm
-
Hey
I do often multiple trips.
First Flight from TXKF to KPBI, everything works fine with GSX it set my Fuel and Pax (370).
All 370 Passangers visible and boarding, and still in Plane while Cruise.
1. I landed in KPBI and deboarded all Passenger, - Airplane empty.
2. I request Caterings - works fine
after that i request Refuling - it was refuling after i set my fuel to 1000 and than back to Flight planned fuel from round about 26000 kg - Gsx is refuling
3. I loaded new simbrief plan
4. I request Boarding. GSX set my Pax and Payload correct in FMC. It starts the Boarding, when it was finished i start and check my Cabin. There are only 4 or 5 Passengers in the hole Plane, but it set 370 by itself in the FMC.
How could this happend, that the Passengers are not in the Cabin?
I attached the Log File, maybe u can find an Error, maybe u can told me what iam doing wrong, expect the Simbrief loading after request of refuling i Know that was the wrong order ^^
greetings
-
I'm guessing this is your issue.
https://www.fsdreamteam.com/forum/index.php/topic,31976.0.html
-
I have the exact same problem, and it's not related to the link posted by Kevin.
I do multiple trips in a row with the 737 and most of the time on the second or thirs the pax are broken. A few arrive in the beginning, then nothing more. The numbers in the text window keep going up, but no more passengers arrive. Boarding os completed, but of the 170 pax only a handful are actually on the plane.
-
Yes, thats exactly the Porblem.
Bute when i landed and press Deboarding My Plane is full again and all Passengers are deboarding... wierd2
-
After the first few pax get off the bus, the counter keeps climbing, but no more pax get out of the bus.
(https://i.postimg.cc/kMtvdDNp/20240811172121-1.jpg) (https://postimg.cc/6TtvrWmr)
(https://i.postimg.cc/mgTYMwvv/20240811172129-1.jpg) (https://postimg.cc/nCw9fvc2)
(https://i.postimg.cc/jd0QqKZd/20240811172323-1.jpg) (https://postimg.cc/SjdzVBBw)
(https://i.postimg.cc/Fsyb7qBb/20240811172353-1.jpg) (https://postimg.cc/vcmxKPMD)
According to the text, the aircraft has more than 100 people on board, but they never got off the bus.
If I restart coault, it works properly.
Can you look into it?
-
Issue stil present with 3.1.2.
Moreover, after deboarding a couple of passengers are still seated and do not leave the plane.
Are you looking into it Umberto?
-
I could only comment on the first post, which has some errors which SHOULD be fixed in the current version, since he was using 3.1.0
If you want to be supported, you need to post your error logs as well, because each airplane is different, and that particular error could possibly happen only on a plane with two corridors like the 777.
-
Here's the log.
I flew from ELLX to LGKR and back.
As usual, on the second flight a few pax come, then nobody else comes, but the counter goes up fast.
I see this in the log:
Exception in passengerDescriptor_Boarding empty range for randrange() (0,0, 0)
Then there's this for when the second bus arrived:
Exception in passengerDescriptor_Boarding
Same error for deboarding:
Exception in passengerDescriptor_Deboarding
The crew disembarked correctly, even with the broken passengers.
NOTE: having the seated pax feature enabled or disabled doesn't make a difference: still no pax on second flight.
Now some pictures:
Deboarding starts, but I can only see a few pax that got on in LGKR
(https://i.postimg.cc/hj5Cqym5/20240820125148-1.jpg) (https://postimg.cc/62CVrhYr)
Nobody deboarding
(https://i.postimg.cc/hGKZ87gp/20240820125510-1.jpg) (https://postimg.cc/18YKsX8q)
Deboarding complete with pax still on
(https://i.postimg.cc/cJT9F4LZ/20240820125545-1.jpg) (https://postimg.cc/06M0QvSH)
Crew deboarding works...
(https://i.postimg.cc/C5ncMGHL/20240820125632-1.jpg) (https://postimg.cc/H8HwB7hf)
... but the pax still stay here.
(https://i.postimg.cc/nzzdgbXm/20240820125905-1.jpg) (https://postimg.cc/Y45fLPf2)
-
Please don't send that many pictures ( it's not as if we don't "believe you"... ) and, instead, send your diagnostic log, which is not a textual description of it. You need to ATTACH the *actual* Couatl.LOG file, not just describe the lines you think are important. That's for us to decide, that's why we need the full log, ZIPPED and ATTACHED to a post, not quoted in a message.
-
But I did attach the log, no idea why it's not visible. I'll try again now.
-
One more log, this time ELLX-LIEE-ELLX. Same issues as usual on the second flight.
-
Were the log files helpful?
-
Yes, there were some errors, but I can't say why they happened, we'll of course check this. Is this happening only on multiple leg flights ?
-
Yes, there were some errors, but I can't say why they happened, we'll of course check this. Is this happening only on multiple leg flights ?
I'm on my second leg and have just noticed this reported behaviour.
-
Yes, there were some errors, but I can't say why they happened, we'll of course check this. Is this happening only on multiple leg flights ?
Yes, as said from the beginning, it only happens on the second, third, fourth flight. Never on the first one. Restarting Coault fixes it as a temporary workaround.
The problem is NOT connnected to the seated passengers, because it also happens without them. I have tried the 737, 738 and BBJ1 variant. All show the same issue.
Let me know is there is some way I can help.
-
This bug is still present with 3.1.6.
Did you have time to look into it? Is there some other kind of log I can generate to help you find the issue?
Do you suggest reinstalling GSX?
It is very annoying, I'd like it to work like it used to before.
-
Today it worked. Same plane as usual, same livery as always. PMDG 738 Luxair. Today the boarding for the second flight worked flawlessly.
Still on 3.1.6, nothing changed. I really wish I could understand what's the trick to make it work.
-
I have noticed this bug is still present in 3.17
-
I have noticed this bug is still present in 3.17
The last poster provided his error log, and his last message was the problem didn't happen on his last flight. Please post your log, to confirm you have the same problem.
-
This bug is still present.
Attached is log. Simbrief updated after final pax disembarked, same error encountered as previously documented.
-
Hi there, I'm back and so is the problem.
On my last flight I also had a slight variation: pax still on board after deboarding was completed.
As usual, PMDG 738 in Luxair livery, latest version of GSX, which at the moment is 3.2.0.
Log attached.
-
Attached is log. Simbrief updated after final pax disembarked, same error encountered as previously documented
Your posted an .ERR file, which is the panic log that only happens if there's an error, but it only shows GSX read the correct number of passengers from Simbrief, then you restarted it before we could see anything meaningful.
You should have enabled logging and post your Couatl.LOG instead, which is more detailed and might show if the airplane later changed the passengers number after GSX loaded it correctly from Simbrief.
-
On my last flight I also had a slight variation: pax still on board after deboarding was completed.
According to your log, the problem was the jetway that didn't dock completely, so deboarding was only simulated, see this line:
"Jetway not close enough to any door. You won't see Passengers."
A possible reason for this is the jetway docking on L2 because of your position (something GSX can't control), but Fenix having removed it and specified L2 to be the rear passenger door instead. This made GSX assuming there's no L2 so, a jetway docked there won't be seen close to any door.
It's possible that Fenix removed L2 assuming that GSX could in some way affect where the jetway docks, but that's not how jetways works in MSFS, the jetway docks where it can, and the only thing that controls this are the [Exits] section in the airplane.cfg, if they wanted to prevent jetways to dock on L2, they should remove the exit from the aircraft.cfg and the GSX profile as well.
But of course, if from your parking position, docking on L1 wouldn't work, the jetway in that case would have been stay undocked, resulting in the exact same issue of Deboarding only simulated.