Author Topic: Fast boarding with fslabs airbus and latest GSX Update  (Read 3739 times)

hkhoanguyen

  • Jr. Member
  • **
  • Posts: 71
Fast boarding with fslabs airbus and latest GSX Update
« on: July 01, 2019, 08:23:02 pm »
Hi,

I have just tried FSLabs A320 with the new update from GSX, here is the problem that I have :

First scenario :

+ Fslabs A320 is first loaded empty, with the OFP contains 168 pax.
+ Do the initialisation, request fuel via GSX, right after that click Boarding and Request Boarding
=> The 2 cargo cars appear but each of them just has one compartment of cargo
=> The pax boarding proceeds but only less than one minute

Second scenario :
+ Fslabs A320 is first loaded empty, with the OFP contains 168 pax.
+ Do the initialisation, request fuel with option : INSTANT, right after that click Boarding and Request Boarding
=> The 2 cargo cars appear and they have all 3 compartments of cargo
=> The pax boarding proceeds but again only less than one minute


After posting in fslabs forum asking for help, their developers detected that there is 168 pax in coualt.log is set, so they redirected me here to ask if this is a GSX Bug (?!)

Here is my question in fslabs forum (along with additional photos) : https://forums.flightsimlabs.com/index.php?/topic/22151-fast-boarding-part-2/

Here is Couatl log file, where fslabs detected that there is 168 pax is set :

Code: [Select]
Requested assistance services at Gate A 24
createCamera() PassengerStairsRear Behind
createCamera() PassengerStairsRear Front
createCamera() PassengerStairsRear Right
createCamera() PassengerStairsRear Left
createCamera() PassengerStairsRear Driver 1st Person
createCamera() PassengerStairsRear Driver Close-up
Fuel price =  1.872
createCamera() BaggageLoaderFront Behind
createCamera() BaggageLoaderFront Driver 1st Person
createCamera() BaggageLoaderFront Loading Area
createCamera() BaggageLoaderRear Behind
createCamera() BaggageLoaderRear Driver 1st Person
createCamera() BaggageLoaderRear Loading Area
createCamera() PushBack Driver 1st Person
createCamera() PushBack Behind
createCamera() PushBack Front
createCamera() PushBack Pushback
Total payload:760 lbs.
Estimated number of passengers =  4
createCamera() FuelTruck Behind
createCamera() FuelTruck Driver 1st Person
createCamera() FuelTruck Front
createCamera() FuelTruck Fuel Counter
View changed to Outside
View changed to Outside
View changed to Outside
View changed to On-Board
View changed to On-Board
View changed to On-Board
View changed to Outside
View changed to Outside
View changed to Outside
View changed to On-Board
View changed to On-Board
View changed to On-Board
Number of passengers provided by airplane addon =  168

Crew number set by Add-on =  4.0
Pilots number set by Add-on =  2.0

Thanks and hope to have your reply soon;
« Last Edit: July 01, 2019, 08:28:25 pm by hkhoanguyen »

hkhoanguyen

  • Jr. Member
  • **
  • Posts: 71
Re: Fast boarding with fslabs airbus and latest GSX Update
« Reply #1 on: July 01, 2019, 08:44:58 pm »
Seems like in the first option with Fuel via GSX option, I don't see this section of reset in the file log : (I just have these lines with FUEL INSTANT option)  :-\

Code: [Select]
reset FSDT_GSX_DEICING_STATE to 0
reset FSDT_GSX_DEICING_TYPE to 0
reset FSDT_GSX_DEICING_CONCENTRATION to 0
reset FSDT_GSX_NUMPASSENGERS to 0
reset FSDT_GSX_BATTERY_VOLTAGE to 0
reset FSDT_GSX_MAX_BATTERY_VOLTAGE to 0
reset FSDT_GSX_FUEL_PRICE to 0
reset FSDT_GSX_FUELHOSE_CONNECTED to 0
reset FSDT_GSX_DISABLE_DOORS_MSG to 0
reset FSDT_GSX_DISABLE_DETECT_REFUELING to 0
reset FSDT_GSX_BOARDING_CARGO_PERCENT to 0
reset FSDT_GSX_DEBOARDING_CARGO_PERCENT to 0
reset FSDT_GSX_NUMPILOTS to 0
reset FSDT_GSX_PILOTS_NOT_BOARDING to 0
reset FSDT_GSX_PILOTS_ON_BOARD to 0
reset FSDT_GSX_NUMCREW to 0
reset FSDT_GSX_CREW_NOT_BOARDING to 0
reset FSDT_GSX_CREW_ON_BOARD to 0

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51400
    • VIRTUALI Sagl
Re: Fast boarding with fslabs airbus and latest GSX Update
« Reply #2 on: July 01, 2019, 10:54:46 pm »
Your log shows the problem, which is FS Labs setting the number of passengers too late, after GSX has already started boarding.

These lines:

Total payload:760 lbs.
Estimated number of passengers =  4

Came just after the creation of all custom cameras so, at that time, GSX already calculated the number of passengers, which affected the number of carts too. At that time, the custom variable required by GSX was still not set by FS Labs, so GSX tried to estimate their number for the weight and, since the weight was very, the passenger number was set to 4.

Then, these lines finally come:

Number of passengers provided by airplane addon =  168

Crew number set by Add-on =  4.0
Pilots number set by Add-on =  2.0

Meaning FS Labs has just set the variables but, at this time, GSX already decided how many loaders and how many passengers to load and, it won't obviously change the number of loaders or the number of passengers after boarding already started.

They should set the variables earlier, before the Boarding option is even chosen.



hkhoanguyen

  • Jr. Member
  • **
  • Posts: 71
Re: Fast boarding with fslabs airbus and latest GSX Update
« Reply #3 on: July 02, 2019, 06:29:04 am »
Thanks for your reply,

I will send your answer to fslabs,


Machtwo

  • Beta tester
  • Newbie
  • *****
  • Posts: 11
Re: Fast boarding with fslabs airbus and latest GSX Update
« Reply #4 on: July 02, 2019, 02:02:00 pm »
As we've discussed, the L vars are all being set long before boarding is requested. In the example above, it is not the boarding service that is requested, but the refuel service.

Also in the above example, the L vars are being populated 3 minutes before the user requested boarding through GSX. Once boarding is requested through GSX, the value of the L Vars are printed to Couatl.log.

I'm sure there is still an issue somewhere in GSX; we are still observing the 'small bus' occasionally showing when GSX has registered 180 passengers (and loads 180 pax correctly).

Perhaps, if you are able to send me some libraries privately that contain more logging, I can forward these onto this customer in an effort to debug this process further.
« Last Edit: July 02, 2019, 02:05:35 pm by virtuali »
Andrew Wilson

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51400
    • VIRTUALI Sagl
Re: Fast boarding with fslabs airbus and latest GSX Update
« Reply #5 on: July 02, 2019, 02:15:06 pm »
As we've discussed, the L vars are all being set long before boarding is requested. In the example above, it is not the boarding service that is requested, but the refuel service.

That's the 2nd case. I was referring to the first case, in which the user said you called Boarding and his log indicates that, in the first case, when he had the problem with loaders with only 1 car, he selected Boarding.

Quote
Also in the above example, the L vars are being populated 3 minutes before the user requested boarding through GSX. Once boarding is requested through GSX, the value of the L Vars are printed to Couatl.log.

 GSX prints the value in the log only when it needs to calculate the passenger number and, since the log doesn't show the "Number of passengers provided by airplane addon" only AFTER the vehicles were created, but shows these two lines:

Total payload:760 lbs.
Estimated number of passengers =  4

It means that, when it printed that message, the number of passenger variable was still set to 0, so GSX reverted to the estimate based on airplane weight

Are you absolutely sure you are checking the L: variable ID *before* setting it ? Variable ID's sometime changes, depending which program (or gauge) set them first and, the only safe way to be sure that a variable that has been set from a program can be read from another one, is to always check its ID before using it.

In any case, we'll continue in private.