FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: stefangr on August 12, 2024, 05:09:24 pm
-
I am having problems with the boarding of pax - it is taking a very long time before it starts.
I made a test again today @EDDM/Gate 301 (sim-wings pro Munich) with P3Dv5, Project Airbus A320 with JeeHell, latest GSX version installed 3.1.0. This is what it looks like regarding the timing according to my own log:
14:09:53 Jetway requested (status 4)
14:09:53 TextMessage: [GSX] Jetway operating
14:09:54 Stairs requested (status 4)
14:10:32 TextMessage: [GSX] Stairs operation completed
14:10:33 Stairs connected (status 5)
14:11:29 TextMessage: [GSX] Jetways operation completed
14:11:29 Jetway connected (status 5)
14:16:04 Boarding requested (status 4)
14:16:04 TextMessage: [GSX] Boarding requested
14:16:05 Boarding status change (status 5 = is being performed)
14:16:06 TextMessage: [GSX] Boarding passengers now
14:16:18 TextMessage: [GSX] Waiting for your action: open Rear Cargo Door (2)
14:16:27 Cargo door is opened
14:18:50 TextMessage: [GSX] Baggage loading progress 10%
14:19:20 TextMessage: [GSX] Baggage loading progress 20%
14:19:35 TextMessage: [GSX] Baggage loading progress 30%
14:20:06 TextMessage: [GSX] Baggage loading progress 50%
14:20:36 TextMessage: [GSX] Baggage loading progress 60%
14:21:06 TextMessage: [GSX] Baggage loading progress 70%
14:21:21 TextMessage: [GSX] Baggage loading progress 80%
14:21:51 TextMessage: [GSX] Baggage loading progress 80%
14:22:06 TextMessage: [GSX] Baggage loading progress 80%
14:22:21 TextMessage: [GSX] Baggage loading progress 90%
14:22:36 TextMessage: [GSX] Baggage loading progress 90%
14:22:51 TextMessage: [GSX] Baggage loading progress 90%
14:23:06 TextMessage: [GSX] Baggage loading progress 90%
14:23:21 TextMessage: [GSX] Baggage loading progress 90%
14:23:36 TextMessage: [GSX] Baggage loading progress 100%
14:30:13 TextMessage: [GSX] Boarding passengers now
14:30:15 TextMessage: [GSX] Waiting for your action: open Main Exit (1)
14:30:17 Main door is opened
14:30:23 TextMessage: [GSX] Passengers boarding starting
14:31:16 TextMessage: [GSX] 2/163 passengers boarded
[...]
14:34:49 TextMessage: [GSX] 82/163 passengers boarded
[...]
14:38:29 TextMessage: [GSX] 162/163 passengers boarded
14:38:54 TextMessage: [GSX] Boarding completed
Obviously there is an attempt to start the pax boarding at 14:16:06, but there is no request to open the main door. Another attempt is being done at 14:30:13, afterwards the request to open the main exit. Once the door is opened then, I can also see the pax in the jetway. Cargo boarding starts straight away, after boarding is requested, but pax board only 14 minutes later. I am not making any other services than Jetway connect / Stairs connect / Request boarding.
Maybe the couatl.log is giving more hints?
Thanks
Stefan
-
I have the same problem after the latest update it takes roughly 15 mins after asking for boarding until the pax are finally boarding
-
Hello!
Its the same situation with me.
https://www.fsdreamteam.com/forum/index.php/topic,32062.0.html my threat!
Is it correct that the gateconfig.ini is now sometimes writen in the scenery directory and only some changes
at the appdata\virtuali?
Best regards
peter
-
Same problem here with the FSLabs airbus. Boarding of pax starts very, very late... :-\
-
Same for me - it seems a bit random, especially happens during turnarounds. In the FSLabs A320 yesterday, the baggage was loaded but I gave up waiting for passenger boarding to start. Seems to have happened since version 3.0.9. Also refuelling is now borked. The first fuel truck stays for about 15 seconds then another is called when loading the PMDG 747.
Would really appreciate either the updates are tested more thoroughly or we are given an option to roll back.
-
I have the same problem on P3D V5.4
-
Ive had the same issue, ill link a video to show my issue...you can see cargo loaded but passengers arent loading....a few weeks ago it was fine then i updated gsx...
-
I'm noticing the same thing on P3D v4.5. I thought it may have something to do with the baggage train timing, but further testing ruled that out. I'm pretty sure crew boarding plays a role. Whenever I include the pilots and crew in the boarding cycle, everything works normally. If I ask to board "nobody", the baggage loading process runs normally, but the passenger boarding doesn't start (no green pop up and no boarding activity). I think this is why people are noticing it happens sporadically or that it seems to affect turn-arounds.
I've tested this on the Flight1 B200 and the PMDG 737. They both exhibited the same behaviour at two different airports. This wasn't happening before the most recent update; I regularly completed boardings without crew or pilots.
-
I can confirm that the issue has something to do with pilots/crew boarding.
If I try to board pax with pilots/crew deactivated boarding of pax doesn´t start. If I let pilots/crew board then boarding of pax starts right afterwards.
Reproducable with FSLabs Airbus and PMDG 737NGX.
-
Have the same issue, can't see passengers boarding, do You think it could be the lsst update?, I tried boarding also crew and pilots but doesn't work.
Regards.
Erick.
-
It was one of the recent updates that tried to fix the number of baggage containers that has caused the issue. I have rolled back using a backup and don't have the issue any more. I understand that you can avoid the delay in boarding passengers by not boarding any crew first, but I have not tested that as I'm happy with how it was working previously.
-
It was one of the recent updates that tried to fix the number of baggage containers that has caused the issue. I have rolled back using a backup and don't have the issue any more. I understand that you can avoid the delay in boarding passengers by not boarding any crew first, but I have not tested that as I'm happy with how it was working previously.
Can you please share the setup file for that?
-
I restored from a system image and I'm not not sure which files in the addon manager folder were changed. I'm not keen on sending the whole folder as that might include activation keys and it would probably require you to re activate your products etc.. If anyone can identify specific files that were changed by the update I'm happy to send them.
-
Yeap, same issue here. PAX will only board after baggage loading is completed.
-
15min delay for pax boarding following resuest with jetway, baggage loading had completed well before that.
-
Hello Virtuali!
Whats going on with the problem?
Is there solution possible?
Best regards
peter
-
I suspect that the unspoken tactic right now is to stop support for P3D because it's a pain to keep maintaining, with very few sales. It's clearly far better for FSDT financially if you go and buy everything again for MSFG, even if this is immoral. Umberto has been very active in the MSFG sub forum recently commenting on bugs and support issues, but since the P3D update a few weeks ago partially broke the boarding, there has been radio silence. I'm guessing we will we will be given an "end of P3D support" announcement in the next few weeks, or maybe it will remain unspoken. I hope I'm wrong.
It's not totally unreasonable to do this, but if that is the future then FSDT should really withdraw all FSX / P3D products from sale if they won't provide support and break them with updates that can't be rolled back. Just like PMDG's recent behaviour, it means the P3D customers who basically provided FSDT's income for years are being dropped. That's business I guess, we can't really complain as we have had a good product that has worked off and on for many years.
-
I suspect that the unspoken tactic right now is to stop support for P3D because it's a pain to keep maintaining, with very few sales. It's clearly far better for FSDT financially if you go and buy everything again for MSFG, even if this is immoral. Umberto has been very active in the MSFG sub forum recently commenting on bugs and support issues, but since the P3D update a few weeks ago partially broke the boarding, there has been radio silence. I'm guessing we will we will be given an "end of P3D support" announcement in the next few weeks, or maybe it will remain unspoken. I hope I'm wrong.
It's not totally unreasonable to do this, but if that is the future then FSDT should really withdraw all FSX / P3D products from sale if they won't provide support and break them with updates that can't be rolled back. Just like PMDG's recent behaviour, it means the P3D customers who basically provided FSDT's income for years are being dropped. That's business I guess, we can't really complain as we have had a good product that has worked off and on for many years.
The problem with this theory is he doesn't respond to forum posts that quick in general. He might respond to a few posts, and then it might be three weeks before he responds to forum posts again. From what it looks like, there's more support provided in the unofficial GSX support Discord.
-
The problem with this theory is he doesn't respond to forum posts that quick in general. He might respond to a few posts, and then it might be three weeks before he responds to forum posts again. From what it looks like, there's more support provided in the unofficial GSX support Discord.
That has cheered me up a bit, I hope you are correct and my theory is totally wrong. I'm also being impatient given that we are just exiting the holiday season.
-
I suspect that the unspoken tactic right now is to stop support for P3D because it's a pain to keep maintaining, with very few sales. It's clearly far better for FSDT financially if you go and buy everything again for MSFG, even if this is immoral. Umberto has been very active in the MSFG sub forum recently commenting on bugs and support issues, but since the P3D update a few weeks ago partially broke the boarding, there has been radio silence. I'm guessing we will we will be given an "end of P3D support" announcement in the next few weeks, or maybe it will remain unspoken. I hope I'm wrong.
It's not totally unreasonable to do this, but if that is the future then FSDT should really withdraw all FSX / P3D products from sale if they won't provide support and break them with updates that can't be rolled back. Just like PMDG's recent behaviour, it means the P3D customers who basically provided FSDT's income for years are being dropped. That's business I guess, we can't really complain as we have had a good product that has worked off and on for many years.
I'd be surprised given FSDT's history (so appreciated by me for this) of keeping some of the oldest products compatible with the latest versions of P3D (and even updating them with features where reasonable)
Has any interim solutions been found or should I leave my GSX out of date for fear of the same issue?
-
Has any interim solutions been found or should I leave my GSX out of date for fear of the same issue?
Another option is to backup the Add-on Manager folder, then run the update. If you start having issues, you can just copy over the files from the backup back to the Add-on Manager folder and you'll be back to the previous version.
-
Has any interim solutions been found or should I leave my GSX out of date for fear of the same issue?
Another option is to backup the Add-on Manager folder, then run the update. If you start having issues, you can just copy over the files from the backup back to the Add-on Manager folder and you'll be back to the previous version.
Good shout, might try that.
-
Ref to the commend from Captain Kevin.
I did the Addon Manager replaced with a older one from back-up, but no change.
The prob with pax boarding still exist
There must be something else which is going wrong
Peter
-
Question to Captain Kevin:
about which addon manager to save before any update are we talking here?
I found on my pc that: Programme X86: addon Manager,
and another here: C:\user\myname\Documents\P3Dv4 Add ons
Brgds,
Peter
-
For me the option to board the crew before, has been proved as a good work around.
Maybe it is taking 1 minute more to board the crew, but that's nothing compared to wait 15 minutes before passengers start boarding. The pax boarding starts right after the crew has boarded.
-
For me the option to board the crew before, has been proved as a good work around.
Maybe it is taking 1 minute more to board the crew, but that's nothing compared to wait 15 minutes before passengers start boarding. The pax boarding starts right after the crew has boarded.
A workaround maybe, not an option. It took years to get the crew boarding disabled in the first place.
-
Did a flight in the fslabs bus tonight and everything worked as intended. I did update gsx before hand. Not sure if anything actually updated or what, but gsx behaved normally.
-
I did a GSX update today, and start P3Dv4 for a test:
AS A320 fully loaded:
Req boarding: Baggage train arrives with 1!! container:
Pax starting boarding about 3-4 min after bag/cargo (above mentioned container) loading finisched
Pax bus (no gate position) arrived: small van like a 7 seater with 1!!!! pax for me
I guess, the support for P3d is going to an end
Peter
-
I guess, the support for P3d is going to an end
Peter
Which is understandable, that does not mean the product should be expected to not work anymore, we did not bought it as is.
Honestly, while the updates are welcome, I have nothing against FSDT stopping updates for P3D if they break the P3D version, BUT I want to keep a working version, there was no expiry time indicated when we bought GSX.
Hopefully we will get an update that will correct these sooner than later. We currently have no ways of coming back to a properly working version.
-
I am also still getting delays in boarding passengers. Sometimes it works fine right after crew boards other times it gets stuck.
Also the animations are stuttering really bad since the last updated.
-
I did a update today.
After that I have no more pax boarding, and baggage loading is for a A320 (2 container /1 front, 1 rear) and for a 737
two baggage cart. One for each hold
Pax boarding did not happen at all
Crew boarding deaktivated since I got P3Dv4.5.
I am wondering will that ever fixed??
Peter
-
Hello,
with latest update same problem. FSX-SE. Boarding delay.
Kind regards
Peter
-
I installed the addon manager from a backup, about 3 months old.
A/C: AS A320, full pax load: I got 2 container, 1 for the rear, 1 for the front, and 1 !!!!!! Passenger
A/C: iFly B738: 123 pax load: I got 3 Baggage cart for the front, as well as 3 cart for the rear.
3 !!! Busses full with pax.
So the question here is: why it works (for me) with the iFly 737, and does not work at all with the (Aerosoft) Bus
Then I updated FSDT, all worst.
Overwrite the Addon Manager with my old one, works as I mentioned above only for the iFly 737.
Re-installing the AS Bus did not change anything
Peter
-
This is what it looks like regarding the timing according to my own log:
Please provide the actual Couatl.LOG as provided by GSX. Don't quote it, but attach the actual file ZIPPED, because I really need to see the whole file unchanged and not translated by the forum software.
-
There isn't a single person reporting this problem who ever posted a diagnostic log. That is except the OP, who posted his own log for which I cannot offer any support with. Without a diagnostic log, I really can't see what is really going on.
Also, a description of the type of gate (standard Jetway, SODE jetway, no jetway, walk-in gate, etc. ) would be useful.
-
This is what it looks like regarding the timing according to my own log:
Please provide the actual Couatl.LOG as provided by GSX. Don't quote it, but attach the actual file ZIPPED, because I really need to see the whole file unchanged and not translated by the forum software.
I thought I had it attached and not quoted in my very first post of this thread. I attach it again, now zipped as requested.
-
There isn't a single person reporting this problem who ever posted a diagnostic log. That is except the OP, who posted his own log for which I cannot offer any support with. Without a diagnostic log, I really can't see what is really going on.
Also, a description of the type of gate (standard Jetway, SODE jetway, no jetway, walk-in gate, etc. ) would be useful.
In my case it was @EDDM/Gate 301 which is having SODE jetway.
-
I gather from another thread that this issue is fixed, can anyone confirm please?
-
no, it is not. I did an update 1 hour ago and my sim is running right now. Pax are coming too late. Will post log later.
-
The same for me. I made 2 test flights with 3.1.8, the first one was ok, the second one with the known delay problem.
-
Umberto, same issue here. Boarding started with the cargo but passengers never showed up. P3DV5, Fslabs A320, Gate A1 in LAS (Flytampa), SODE Jetway connected... Pls. see attached log in zip file. Should you see anything else pls. let me know!
-
Another quick test... after 3.2.0 update. On the first attempt only the cargo got loaded to the aircraft, no passengers. Restarted Couatl, then passengers boarded with a 5-10min delay. P3DV5, Fslabs A321SL, Gate B3 in MEM (FSDT), SODE Jetway connected... Pls. see attached log in zip file, hope it helps. Very bizarre...
-
I did another update today.
AS A321 202 Pax
Bag loading: 2 Container, 1 for each hold !!!!
Pax boarding ok, 202 passenger boarding !!!
Could not find a Couatl.log file. Windows search did not find one
-
In the GSX settings, under troubleshooting, make sure you actually have it enabled.
-
Hello,
Is there any change to download a specific update for GSX (e.g. March 24) from FSDT?
The reason to ask is, whatever update I get, I still have the problem with loading Pax/Cargo
Peter
-
Peter, this isn't possible. The only thing you can really do is back up the Add-on Manager folder prior to updating, and then if there's an issue, you can always copy the files back.
-
Hi Kevin,
I have done that, but without success.
What about a fresh installation (with my origin (old) setup files for GSX as well as Level 2) and then update the system with the Manager from lets say, Januar 2024.
I know, I will missing samething in this case, but for me is better a working "older" system as a not so well working system which is up to date.
Peter
-
I have the same problem here. The passengers do not start boarding, but if the crew does it beforehand, it works.
I also noticed a few days ago that the status of the doors is no longer checked.
Boarding and deboarding begin even if the doors are closed. (except for cargo)
I have completely re-installed gsx today. The behavior remains the same
-
What about a fresh installation (with my origin (old) setup files for GSX as well as Level 2) and then update the system with the Manager from lets say, Januar 2024.
That wouldn't really work because as soon as you install it, it's going to check for the latest update and install the files anyway.
-
I also noticed a few days ago that the status of the doors is no longer checked.
Boarding and deboarding begin even if the doors are closed. (except for cargo)
I can confirm that. I noticed that too.
-
Made a test today once more @EDDM/Gate A301 (scenery EDDM sim-wings pro Munich) with SODE jetway which is connected to door 1L / P3Dv5 with Project Airbus A320
I have attached the COUATL.LOG as ZIP, as I did in my first post on 12AUG24
In addition to that, I have posted some entries of my own log to illustrate the timeline, as I did in my first post on 12 AUG24.
2 Problems as of today:
a) Pax boarding is starting with a delay of 14 minutes (17:34:28 vs 17:48:32)
b) Pax are boarding through the closed door 1L, there is no request to open 1L.
17:32:45 Boarding requested (all doors are closed)
17:32:57 Jetway requested
17:33:01 [GSX] Waiting for your action: open Rear Cargo Door (2)
17:33:09 Cargo door has been opened manually
17:34:28 [GSX] Boarding passengers now
17:34:28 Jetway is connected
17:34:53 [GSX] Hello, captain! We are ready for pushback.
17:35:49 [GSX] Baggage loading progress 20%
17:40:20 [GSX] Baggage loading progress 100%
17:48:32 [GSX] Boarding passengers now
17:48:34 [GSX] Passengers boarding starting
17:49:21 [GSX] 4/167 passengers boarded
17:57:07 [GSX] 167/167 passengers boarded
17:57:18 [GSX] Boarding completed
I have installed the most current version of GSX which is labelled "Version 3.2.2– October 20th, 2024" according to "Couatl™ Live update release notes" page. At least I suppose I have installed this version since I ran live update after 20th Octoer 2024, but I have not seen the possibility to check the version number of GSX which is actually installed (at least not with a number which would fit to a pattern like "3.x.x.")
-
Made another test today @LOWS/Gate W6 (scenery LOWS Digital Design Salzburg) without jetways, only stairs / P3Dv5 with Project Airbus A320
I have attached the COUATL.LOG as ZIP.
In addition to that, I have posted some entries of my own log to illustrate the timeline.
Pax boarding is starting with a delay of 16 minutes (08:15:09 vs 08:31:05)
Problem regarding boarding through closed doors was not tested since 1L was opened manually before boarding was requested.
08:15:07 [GSX] Boarding requested
08:15:09 [GSX] Boarding passengers now
08:15:37 [GSX] Hello, captain! We are ready for pushback.
08:15:43 [GSX] Waiting for your action: open Rear Cargo Door (2)
08:15:50 Cargo door has been opened manually
08:17:55 [GSX] Baggage loading progress 10%
08:22:26 [GSX] Baggage loading progress 100%
08:31:05 [GSX] Boarding passengers now
08:31:36 [GSX] Passengers boarding starting
08:32:28 [GSX] 11/153 passengers boarded
08:34:53 [GSX] Passengers boarding starting [because of 2nd bus]
08:37:40 [GSX] Boarding completed
I have installed the most current version of GSX which is labelled "Version 3.2.2– October 20th, 2024" according to "Couatl™ Live update release notes" page. At least I suppose I have installed this version since I ran live update after 20th October 2024, but I have not seen the possibility to check the version number of GSX which is actually installed (at least not with a number which would fit to a pattern like "3.x.x.")
-
Hello Umberto,
it would be nice and expected that you would reply to this message and correct the error (asking if the doors are open for boarding/deboarding).
Sincerely
-
Just trying to keep this subject on the first page, hoping that there will be an answer at some time.
Made a test today once more @EDDM/Gate A301 (scenery EDDM sim-wings pro Munich) with SODE jetway which is connected to door 1L / P3Dv5 with Project Airbus A320
I have attached the COUATL.LOG as ZIP, in addition to that, I have posted some entries of my own log to illustrate the timeline.
2 Problems as of today:
a) Pax boarding is starting with a delay of 14-15 minutes (08:09:48 vs 08:24:23)
b) Pax are boarding through the closed door 1L, there is no request to open 1L.
08:08:08 Boarding requested (all doors are closed)
08:08:18 Jetway requested
08:08:24 [GSX] Waiting for your action: open Rear Cargo Door (2)
08:08:34 Cargo door has been opened manually
08:09:48 [GSX] Boarding passengers now
08:09:49 Jetway is connected
08:10:12 [GSX] Hello, captain! We are ready for pushback.
08:11:12 [GSX] Baggage loading progress 17%
08:13:27 [GSX] Baggage loading progress 100%
08:24:23 [GSX] Boarding passengers now
08:24:25 [GSX] Passengers boarding starting
08:25:25 [GSX] 7/150 passengers boarded
08:31:52 [GSX] 150/150 passengers boarded
08:31:54 [GSX] Boarding completed
I have installed the version of GSX which is labelled "Version 3.2.3– October 26th, 2024" according to "Couatl™ Live update release notes" page. At least I suppose I have installed this version since I ran live update on 28th October 2024, but I have not seen the possibility to check the version number of GSX which is actually installed (at least not with a number which would fit to a pattern like "3.x.x.")
-
Just trying to keep this subject on the first page, hoping that there will be an answer at some time.
Made a test today once more @EDDM/Gate A301 (scenery EDDM sim-wings pro Munich) with SODE jetway which is connected to door 1L / P3Dv5 with Project Airbus A320
I have attached the COUATL.LOG as ZIP, in addition to that, I have posted some entries of my own log to illustrate the timeline.
1 problem as of today: Pax boarding is starting with a delay of 14 minutes (09:44:25 vs 09:58:29)
The problem that pax are boarding through the closed door 1L (because there is no request to open 1L) has been fixed obviously. The delay remains.
09:42:44 Boarding requested (all doors are closed)
09:42:54 Jetway requested
09:42:59 [GSX] Waiting for your action: open Rear Cargo Door (2)
09:43:09 Cargo door has been opened manually
09:44:25 [GSX] Boarding passengers now
09:44:25 Jetway is connected
09:44:50 [GSX] Hello, captain! We are ready for pushback.
09:45:33 [GSX] Baggage loading progress 13%
09:49:03 [GSX] Baggage loading progress 100%
09:58:29 [GSX] Boarding passengers now
09:58:31 [GSX] Waiting for your action: open Main Exit (1)
09:58:33 Door 1L has been opened manually
09:58:40 [GSX] Passengers boarding starting
09:59:33 [GSX] 5/216 passengers boarded
10:09:35 [GSX] Boarding completed
10:09:37 [GSX] Waiting for your action: close Main Exit (1)
10:09:44 Door 1L has been closed manually
I have installed the version of GSX which is labelled "Version 3.2.6– November 8th, 2024" according to "Couatl™ Live update release notes" page. At least I suppose I have installed this version since I ran live update on 9th November 2024, but I have not seen the possibility to check the version number of GSX which is actually installed (at least not with a number which would fit to a pattern like "3.x.x.")
-
Oddly enough, you might get a faster response time if you ask in the GSX Discord.
-
thanks. Nice colorful support system there ;)
https://discord.com/channels/1011680327346966590/1305588389621534790/1305588389621534790
-
@virtuali, you can add me to the list of people reporting a long delay in passengers boarding.
In my case it's with FS Labs Concorde and the interaction with that aircraft is extensive.
Several minutes after GSX menu shows pax boarding they eventually start boarding. The delay needs sorting out please.
-
I think you will need to post a log file for any hope of this being looked into, it's been ongoing for a long time. I myself can't post any log files because I restored to an earlier version of GSX prior to the problem being introduced and won't update until the issue is resolved. It seems to be a universal issue for all P3D users, associated with the changes to the code to determine the number of baggage carts. It's a shame because I also can't buy any FSDreamTeam products while the issue is unresolved because the installation runs the GSX updater.
-
@LEdwards2012,
Unlike stefan above my LOG contains no entries for boarding passengers. I suspect the diagnostics log needs enabling. That's now done. More to follow.
-
@LEdwards2012,
Unlike stefan above my LOG contains no entries for boarding passengers. I suspect the diagnostics log needs enabling. That's now done. More to follow.
My attached Couatl.log neither contains anything about boarding (except sounds not played or settings about board pilots/crew). The log I quoted in my post is my own log created by a Lua script which is logging for example all messages from the status bar where GSX is reporting progress, those entries have [GSX] in front of the message.
-
@stefangr,
I have a similar one created by FS Labs for their Concorde. It's shown below. 2m 20s before the first passenger boards. Long walk from the terminal? ;D
[11:35:09] - Boarding Request
[11:35:10] - Boarding State Changed to: 4
[11:35:32] - Boarding State Changed to: 5
[11:36:22] - Refuel State Changed to: 1
[11:37:19] - Boarding Cargo Changed to: 1
[11:37:24] - Cargo Loading Complete
[11:37:24] - Boarding Cargo Changed to: 0
[11:37:29] - Boarding Cargo Percent Changed to: 50
[11:38:13] - Boarding Cargo Changed to: 1
[11:38:14] - Boarding Cargo Percent Changed to: 100
[11:38:23] - Cargo Loading Complete
[11:38:23] - Boarding Cargo Changed to: 0
[11:39:50] - Pax Boarding Changed to: 7
[11:39:50] - Pax Boarding Total Changed to: 7
[11:39:54] - Pax Boarding Changed to: 8
[11:39:54] - Pax Boarding Total Changed to: 8
[11:39:55] - Pax Boarding Changed to: 9
[11:39:55] - Pax Boarding Total Changed to: 9
[11:39:56] - Pax Boarding Changed to: 10
[11:39:56] - Pax Boarding Total Changed to: 10
[11:39:59] - Pax Boarding Changed to: 12
[11:39:59] - Pax Boarding Total Changed to: 12
[11:40:00] - Pax Boarding Changed to: 13
[11:40:00] - Pax Boarding Total Changed to: 13
[11:40:01] - Pax Boarding Changed to: 14
[11:40:01] - Pax Boarding Total Changed to: 14
[11:40:02] - Pax Boarding Changed to: 15
[11:40:02] - Pax Boarding Total Changed to: 15
[11:40:03] - Pax Boarding Changed to: 16
[11:40:03] - Pax Boarding Total Changed to: 16
[11:40:07] - Pax Boarding Changed to: 17
[11:40:07] - Pax Boarding Total Changed to: 17
[11:40:07] - Pax Boarding Changed to: 18
[11:40:07] - Pax Boarding Total Changed to: 18
[11:40:08] - Pax Boarding Changed to: 19
[11:40:08] - Pax Boarding Total Changed to: 19
[11:40:09] - Pax Boarding Changed to: 20
[11:40:09] - Pax Boarding Total Changed to: 20
[11:40:11] - Pax Boarding Changed to: 22
[11:40:11] - Pax Boarding Total Changed to: 22
[11:40:13] - Pax Boarding Changed to: 23
[11:40:13] - Pax Boarding Total Changed to: 23
[11:40:14] - Pax Boarding Changed to: 24
[11:40:14] - Pax Boarding Total Changed to: 24
[11:40:15] - Pax Boarding Changed to: 25
[11:40:15] - Pax Boarding Total Changed to: 25
[11:40:15] - Pax Boarding Changed to: 26
[11:40:15] - Pax Boarding Total Changed to: 26
[11:40:19] - Pax Boarding Changed to: 27
[11:40:19] - Pax Boarding Total Changed to: 27
[11:40:19] - Pax Boarding Changed to: 28
[11:40:19] - Pax Boarding Total Changed to: 28
[11:40:19] - Pax Boarding Changed to: 29
[11:40:19] - Pax Boarding Total Changed to: 29
[11:40:20] - Pax Boarding Changed to: 30
[11:40:20] - Pax Boarding Total Changed to: 30
[11:40:21] - Pax Boarding Changed to: 31
[11:40:21] - Pax Boarding Total Changed to: 31
[11:40:21] - Pax Boarding Changed to: 32
[11:40:21] - Pax Boarding Total Changed to: 32
[11:40:23] - Pax Boarding Changed to: 34
[11:40:23] - Pax Boarding Total Changed to: 34
[11:40:23] - Pax Boarding Changed to: 36
[11:40:23] - Pax Boarding Total Changed to: 36
[11:40:24] - Pax Boarding Changed to: 37
[11:40:24] - Pax Boarding Total Changed to: 37
[11:40:24] - Pax Boarding Changed to: 38
[11:40:24] - Pax Boarding Total Changed to: 38
[11:40:26] - Pax Boarding Changed to: 39
[11:40:26] - Pax Boarding Total Changed to: 39
[11:40:29] - Pax Boarding Changed to: 40
[11:40:29] - Pax Boarding Total Changed to: 40
[11:40:30] - Pax Boarding Changed to: 41
[11:40:30] - Pax Boarding Total Changed to: 41
[11:40:31] - Pax Boarding Changed to: 42
[11:40:31] - Pax Boarding Total Changed to: 42
[11:40:32] - Pax Boarding Changed to: 43
[11:40:32] - Pax Boarding Total Changed to: 43
[11:40:35] - Pax Boarding Changed to: 44
[11:40:35] - Pax Boarding Total Changed to: 44
[11:40:35] - Pax Boarding Changed to: 45
[11:40:35] - Pax Boarding Total Changed to: 45
[11:40:37] - Pax Boarding Changed to: 46
[11:40:37] - Pax Boarding Total Changed to: 46
[11:40:37] - Pax Boarding Changed to: 47
[11:40:37] - Pax Boarding Total Changed to: 47
[11:40:37] - Pax Boarding Changed to: 48
[11:40:37] - Pax Boarding Total Changed to: 48
[11:40:39] - Pax Boarding Changed to: 49
[11:40:39] - Pax Boarding Total Changed to: 49
[11:40:43] - Pax Boarding Changed to: 50
[11:40:43] - Pax Boarding Total Changed to: 50
[11:40:44] - Pax Boarding Changed to: 52
[11:40:44] - Pax Boarding Total Changed to: 52
[11:40:47] - Pax Boarding Changed to: 53
[11:40:47] - Pax Boarding Total Changed to: 53
[11:40:47] - Pax Boarding Changed to: 54
[11:40:47] - Pax Boarding Total Changed to: 54
[11:40:47] - Pax Boarding Changed to: 55
[11:40:47] - Pax Boarding Total Changed to: 55
[11:40:49] - Pax Boarding Changed to: 56
[11:40:49] - Pax Boarding Total Changed to: 56
[11:40:49] - Pax Boarding Changed to: 57
[11:40:49] - Pax Boarding Total Changed to: 57
[11:40:51] - Pax Boarding Changed to: 58
[11:40:51] - Pax Boarding Total Changed to: 58
[11:40:54] - Pax Boarding Changed to: 59
[11:40:54] - Pax Boarding Total Changed to: 59
[11:40:54] - Pax Boarding Changed to: 60
[11:40:54] - Pax Boarding Total Changed to: 60
[11:40:55] - Pax Boarding Changed to: 61
[11:40:55] - Pax Boarding Total Changed to: 61
[11:40:57] - Pax Boarding Changed to: 62
[11:40:57] - Pax Boarding Total Changed to: 62
[11:40:57] - Pax Boarding Changed to: 63
[11:40:57] - Pax Boarding Total Changed to: 63
[11:40:58] - Pax Boarding Changed to: 64
[11:40:58] - Pax Boarding Total Changed to: 64
[11:41:00] - Pax Boarding Changed to: 65
[11:41:00] - Pax Boarding Total Changed to: 65
[11:41:01] - Pax Boarding Changed to: 66
[11:41:01] - Pax Boarding Total Changed to: 66
[11:41:03] - Pax Boarding Changed to: 67
[11:41:03] - Pax Boarding Total Changed to: 67
[11:41:03] - Pax Boarding Changed to: 68
[11:41:03] - Pax Boarding Total Changed to: 68
[11:41:08] - Pax Boarding Changed to: 69
[11:41:08] - Pax Boarding Total Changed to: 69
[11:41:08] - Pax Boarding Changed to: 70
[11:41:08] - Pax Boarding Total Changed to: 70
[11:41:08] - Pax Boarding Changed to: 71
[11:41:08] - Pax Boarding Total Changed to: 71
[11:41:09] - Pax Boarding Changed to: 72
[11:41:09] - Pax Boarding Total Changed to: 72
[11:41:10] - Pax Boarding Changed to: 73
[11:41:10] - Pax Boarding Total Changed to: 73
[11:41:11] - Pax Boarding Changed to: 74
[11:41:11] - Pax Boarding Total Changed to: 74
[11:41:11] - Pax Boarding Changed to: 75
[11:41:11] - Pax Boarding Total Changed to: 75
[11:41:12] - Pax Boarding Changed to: 76
[11:41:12] - Pax Boarding Total Changed to: 76
[11:41:13] - Pax Boarding Changed to: 77
[11:41:13] - Pax Boarding Total Changed to: 77
[11:41:13] - Pax Boarding Changed to: 78
[11:41:13] - Pax Boarding Total Changed to: 78
[11:41:14] - Pax Boarding Changed to: 79
[11:41:14] - Pax Boarding Total Changed to: 79
[11:41:15] - Pax Boarding Changed to: 80
[11:41:15] - Pax Boarding Total Changed to: 80
[11:41:16] - Pax Boarding Changed to: 81
[11:41:16] - Pax Boarding Total Changed to: 81
[11:41:18] - Pax Boarding Changed to: 82
[11:41:18] - Pax Boarding Total Changed to: 82
[11:41:20] - Pax Boarding Changed to: 83
[11:41:20] - Pax Boarding Total Changed to: 83
[11:41:21] - Pax Boarding Changed to: 84
[11:41:21] - Pax Boarding Total Changed to: 84
[11:41:22] - Pax Boarding Changed to: 85
[11:41:22] - Pax Boarding Total Changed to: 85
[11:41:23] - Pax Boarding Changed to: 86
[11:41:23] - Pax Boarding Total Changed to: 86
[11:41:24] - Pax Boarding Changed to: 87
[11:41:24] - Pax Boarding Total Changed to: 87
[11:41:25] - Pax Boarding Changed to: 88
[11:41:25] - Pax Boarding Total Changed to: 88
[11:41:26] - Pax Boarding Changed to: 89
[11:41:26] - Pax Boarding Total Changed to: 89
[11:41:26] - Pax Boarding Changed to: 90
[11:41:26] - Pax Boarding Total Changed to: 90
[11:41:27] - Pax Boarding Changed to: 91
[11:41:27] - Pax Boarding Total Changed to: 91
[11:41:33] - Pax Boarding Changed to: 92
[11:41:33] - Pax Boarding Total Changed to: 92
[11:41:34] - Pax Boarding Changed to: 93
[11:41:34] - Pax Boarding Total Changed to: 93
[11:41:38] - Pax Boarding Changed to: 94
[11:41:38] - Pax Boarding Total Changed to: 94
[11:41:38] - Pax Boarding Changed to: 95
[11:41:38] - Pax Boarding Total Changed to: 95
[11:41:46] - Passenger Loading Complete
[11:41:46] - Boarding State Changed to: 6
-
In the meantime, I have made about 20 different attempts to identify the problem myself. It seems to work at some airports. But most of the time, it doesn't.
Last test at ZPPP airport on the ramp. Boarding with stairs and passenger bus. The bus arrives, but is empty. Even after the luggage is loaded, absolutely nothing happens. Boarding never starts and is not finished.
A pushback is also no longer possible, as the stairs cannot be removed from the aircraft, not even if the doors are closed. The only solution is a reset.
It cannot be right that the feature for MSFS makes GSX unusable for P3D users. An exception can be seen in the attached log file!
It's about time that someone from FSDT spoke up and offered a solution to this problem. The P3D users have also paid money for the product!
And whether you write here or on Discord doesn't seem to matter. The way they treat their own customers is unbelievable.
And the question about log files has been answered, since enough log files have now been uploaded by users.
-
Possibly the two problems (this Topic 32066: Delay in boarding pax and Topic 32309: FSLabs - Doors not open but boarding and boarding happening http://www.fsdreamteam.com/forum/index.php/topic,32309.0.html (http://www.fsdreamteam.com/forum/index.php/topic,32309.0.html)) are related. During my tests with FSX and GSX Level 2 I also encountered the problem when boarding was requested. Not every time, but every now and then. Although it is displayed in the menu, nothing happens and is never completed. Only a restart of GSX helps.
@dkreiskott,
I also think that it can't be, that updates, which are supposed to eliminate errors, keep generating new errors and thus break GSX for P3D/FSX. And as a paying customer you hear NOTHING from FSDT. Absolutely no response for weeks. This is absolutely no way to deal with customers. We should think about what we can do here.
-
The problem will be surely dealt with in the next update.
-
The problem will be surely dealt with in the next update.
Hallelujah! ;D I was close to restoring from a backup.
-
A quick note for Umberto,
it seems as if the problem does not occur at all airports. I checked what was happening at least 10 times with Justsim EDDL at Gate A15 and at the ramp.
Each time the passengers were boarded on time.
If I try the same thing in ZLXY from WFSS Sceneries the passengers never arrive, or only arrive (happened once) after about 30 minutes.
It doesn't matter whether at the gate or the ramp.
-
I've had a similar situation, especially with the FSL320 series plug-in, when deboarding is completed and then at ATSU or manually calling out boarding, there is no longer a crew or passenger boarding animation, however this issue does not occur at some airports, nor in previous versions, and on PMDG models the person boarding animation does not disappear
-
Sorry Umberto,
I no longer believe your promises that the next update will fix the errors for GSX for FSX/P3D. So far, every update has created new bugs that have made us FSX/P3D users hope for the next update because they broke the features we paid for.
I don't know what game you play with us long-time GSX Level 2 users. But I have the impression that you are no longer interested in offering your former paying customers error-free software, but rather in generating new customers for your product by continually promising new features. The main thing seems to be that customers pay. You don't seem to care whether customers who have previously paid for your software can still use error-free software today. This is also proven by your update strategy, which does not allow a return to the original, previously paid status if the customer discovers that the update is not error-free. It is not possible to restore the software to the state in which we customers once paid for it.
The argument that you are providing old GSX Level 2 customers with new services with the updates does not count here. On the contrary: you have been telling us "old" customers of GSX Level 2 for P3D/FSX for years that we can expect the water lavatory feature to be available. Now it's developed, but you're denying us if we don't switch to GSX Pro. This is clearly customer fraud.
It would be OK if you tell us old customers, that you stop supporting P3D/FSX. Time doesn't stand still. The live update probably also checks whether MSFS is installed. But then I expect that updates offered will not generate new errors for P3D/FSX that destroy our paid product, but rather existing errors will be eliminated.
I challenge you to provide GSX for FSX/P3d customers with a bug-free product. I didn't pay for anything else. Anything else I consider as fraud.
Make me an offer as to how we can settle the matter. Otherwise I will take further steps.
I suspect that you have gotten carried away with your own development and are no longer under control. You don't seem to care about your customers now.
-
This is also proven by your update strategy, which does not allow a return to the original, previously paid status if the customer discovers that the update is not error-free. It is not possible to restore the software to the state in which we customers once paid for it.
If you back up the Add-on Manager folder before you run the update, you can revert it if you run into any issues after updating, just simply move the files back over.
-
The problem will be surely dealt with in the next update.
Stable products will make customers happy and continue to support your company's other products, the consistent model has been broken has greatly affected our flight experience, and we hope that GSX will solve this sudden bug as soon as possible
-
This topic starts in August.
It's now November and nothing has really happened. The old problems continue to exist and new ones have emerged.
I continue to be of the opinion, especially now that MS2024 is approaching, that FSX/P3D for FSDT is just a stopgap that is maintained when nothing else is needed.
Peter
-
Update appears to be out now, so go ahead and try it if you wish. Just make sure to back up the Add-on Manager folder first in case you wish to revert for whatever reason.
-
I no longer believe your promises that the next update will fix the errors for GSX for FSX/P3D.
And of course, with today's update, we fixed the problem (as promised), even while having to do lots of other important fixes to support MSFS 2024, yet we managed to add the promised P3D fix.
-
Thanks for getting this fixed umberto!
-
First test today at my favorite test position @EDDM/Gate 301 (sim-wings pro Munich, SODE jetway) with P3Dv5, Project Airbus A320 with JeeHell, latest GSX version installed 3.2.7:
Looking good, I had no delay in boarding pax anymore.
Thanks!
-
Thank you, Umberto!!!
Working well.
Aussie
-
Today, after the update, a large-scale test was carried out at airports in western China, and the phenomenon of no passengers after applying for boarding again after a period of deboarding that was previously encountered was resolved. Thanks for the update on FSDT GSX
-
Thank you @virtuali. I’ll look forward to my pax boarding tomorrow. ;D
-
Works now, thanks. :)
-
Thanks Umberto and team.
Works well now, but only with Aerosoft A320/21 I get sometimes only 2 bag container for about 160 Pax.
Is not a big deal because is not always.
Thank you
Peter
-
I had a second bus for my 100 pax on Concorde. 👍 No delays. 👏
-
I decided to do an update as the latest fixes seem to have solved most of the issues. The boarding is working correctly for me, including the appropriate number of baggage containers. The only issue I have is that in the FSLabs A320 I get no animated people in the fuel truck, apart from that it works and refuels properly. I did not have this issue with the PMDG 747. The fuel truck was one of the smaller Texaco trucks with underground refuelling facilities, both SCEL and SAEZ.
postscript - I tried again the next day and the refuelling animations worked with the non Texaco branded small fuel truck.