[Waiting] FSCaptain Simulate loading the last PAX forever

[draci]

I'm trying to setup FSCaptain for P3Dv5 after having used it successfully for years in FSX. I let FSCaptain Simulate the Load of the PAX

which is very slow, although I have set the loading time to as little as 6 ticks per pax in the Administrator. Especially for the last few pax the loading gets stuck (the last 2 or 3 pax never board or need an incredibly long time, at least longer than I'm willing to wait) and hence I have to interrupt the loading process and reconcile the load to be able to proceed with the flight. I use GSX in the PMDG 747, but GSX completes its boarding normally which the FCDU doesn't recognize. I never had this problem in FSX, so I guess its a wrong combination of settings?

Any help appreciated,

Best regards, draci

[Travis]

Hi Draci,

It's not something that's different between FSX and P3D.  The code is the same for all simulators, so it's likely a setting that's playing havoc with things... or it could just as easily be changes to our code since you last used FSX.

Give me a little time to look into this.  I haven't used "Simulate Load" for some time, and it is something I could do even with my current PC problems.

It would greatly help me if you could email at least two FCDU logs from such flights.  Also please include an FSCaptain log from at least one of those flights.  With your logs I can duplicate your settings for my testing, and look for "gotcha" things.

What you're doing as a workaround is exactly what we've intended.  Interrupt the load and reconcile it with the correct value(s).

And about GSX... what we do is to ensure we do not exceed their PAX count.  We don't try to match their count... although when it comes to "Simulate Load," that might not be a bad idea for a future build.

Best,

[draci]

Thank you for helping me, I will provide the logs as fast as I can (being at work from time to time unfortunately...)

[Travis]

Le Sigh... I remember having a job.    Take your time however you need to, we will be here.

Best,

[draci]

Thanks Travis, I appreciate. A short update: I did a quick and dirty experiment and noticed that the problem is with GSX interaction. The Fs Captain Load Simulation stops as soon as GSX finishes boarding, but since FSCaptain PAX count lags behind, the last few pax never board and I have to interrupt and reconcile the load. Never had to do this in FSX. So I guess that there is a problem with the "Honor_other_ground_services" options. There is one in the Administrator (tick on or off) and one in the options.cfg (values 0,1,2), but they seem to do different things. Perhaps you remember to which vaules I have to set these to prevent the problem, should I simply set both of them to off?

[Travis]

Hi Draci,

That may be the lead that I need.

It's possible that if GSX says "We're done" the FSCaptain PAX load may not complete as it should.  If so, that's easily fixable in code.

But also, have you tried changing your FSCaptain PAX timings, so FSCaptain PAX load faster??

Here's my settings, fwiw:



--------

The Checkbox in the Administrator should set HONOR_OTHER_GROUND_SERVICES to "2" so that we never load or unload faster than GSX.

I will start setting up my PC in the next day or two - until that's stable I can't run GSX to test.  And I really want to run GSX to test their "WALK IN" gates.

Best,

[draci]

I could solve the problem by disabling "Honor_Ground_Services". But there is yet another problem that is new in the latest version. After takeoff the FCDU does not accept block time changes, at least not if the desired new block time is less than the current one. I need this feature since I want the block time to reflect the scheduled arrival time, but since I start FSCaptain when I start taxiiing at the gate, I have to correct for taxi time after takeoff. Unforunately the latest version doesn't let me do this.

[Travis]

Disabling that option would work, but I want to fix the actual problem when I'm able so you can re-enable the option.

Something about "not being able to revise the block time" itches somewhere in my noggin, but I can't locate any notes on this.

I'm likely a week away from having my new PC "normalized" for my use with P3D and FSCaptain, so I've put this on the top of my "look at this" list.

I hate to continue asking for patience, but that's all I can do for now.

Currently under Win 11 Pro, my Admin cannot run, and my FCDU gauge can't connect to the Admin DLL.  My coding tools aren't installed, so I'm not of much use for a few more days.

Best,

Best,

[Travis]

Mar 3, 2022 19:31:30 GMT -5 draci said:

After takeoff the FCDU does not accept block time changes, at least not if the desired new block time is less than the current one. I need this feature since I want the block time to reflect the scheduled arrival time, but since I start FSCaptain when I start taxiiing at the gate, I have to correct for taxi time after takeoff. Unforunately the latest version doesn't let me do this.

Would it be safe to say the problem that you're facing is that the FCDU would allow you to change your block time... but the "minimum block time" it will accept is not enough for you??

There is some logic to keep a Captain from entering too low of a revision.  Off the top of my head, the minimum block time should be the calculation of a straight-line flight using aircraft config parameters, with the addition of your taxi-in time.

If that doesn't sound as if it would help you, I could try adding an option to bypass the standard minimum revision time check after going OUT.  Just know that the logic for calculating the standard maximum revision time looks at your current block time and won't allow for gross increases.

If, however, you're asking about something different, please re-explain it to us.

Best,

[Travis]

Captains,

A single Alpha Testing report from a different P3D5 Captain showed the PAX boarding count reported by GSX did not complete, so the FCDU was stuck waiting for the last passenger to arrive.  In other words, GSX Boarding finished, but they didn't report to us that all passengers had boarded.

We're monitoring this - it doesn't occur for me in P3D4 - and we have a first attempt at a workaround in 1.8.3 Service Pack Beta 1.  Once GSX reports that it has finished Boarding, your FCDU PAX count should now complete.  We're awaiting test reports on how (or if) this works.

Best,

[Travis]

Hi Draci,

Was the original GSX loading issue corrected in Service Pack builds, or does it continue?

There were two related attempts to fix this and a very similar problem.  Both fixes are in the Beta and RC builds.

Best,