Changes to payload in manifest

[psharp84]

Hi

When I create a pax flight, the manifest almost always mentions changes to the payload such as

- LOST ITEMS REDUCED PAYLOAD BY 351LB.

In this case, the change to the payload is almost 50% (planned: 756lb in 4 seater Duke B60).

My question is how I can disable these unplanned changes to the payload?

Thanks

Peter

[peter]

Hello Peter,

I have never seen that message myself, but I would suspect that this is an airline issue. Can you provide us with the ADMIN_..._.log file of the manifest? You may find it in the FSCAptain\Data\Logs\ folder. If you send it via email (see blue link below) I won't be able to access it until next week. Alternatively, you could move the file to a Google Drive and provide us with the link via a private message in this forum.

Cheers,
Peter

[Travis]

Nov 20, 2021 5:39:21 GMT -5 psharp84 said:

Hi

When I create a pax flight, the manifest almost always mentions changes to the payload such as

- LOST ITEMS REDUCED PAYLOAD BY 351LB.

In this case, the change to the payload is almost 50% (planned: 756lb in 4 seater Duke B60).

My question is how I can disable these unplanned changes to the payload?

Hi Peter,

Short answer - you can't change that now.

Years ago I had an idea to (optionally & randomly) have payload change between the time of the Dispatch Release and Load Complete.  It would include both additions and subtractions from the Dispatch Payload, and would represent a possible last-minute change that a Captain might have to account for.

I added the display elements to both the FCDU and the WriteRelease() method.  I planned for an airline-specific option... but I made some flights first to test something else.

That's when I noticed that on occasion, if I were flying a medium or smaller a/c with a Load Map I would get the "LOST ITEMS" or "EXTERNAL TRANSPORT ISSUES REDUCED PAYLOAD BY" without any effort on my part.

It turns out that the method that is supposed to load "an amount of payload" could fail to find a matching load station.  That itself would trigger the new messages.

So I left well-enough alone at the time... but I guess now is as good of a time to look at this for a fix... or at least an improvement.

Targeted for the next build.

Best,

[psharp84]

Hi Travis

Thanks for your reply. - To me it looks cleary not like an issue of assigning payload to stations. The AC does have, according to aircraft.cfg and load map the capacity to load what is specified.

I would suggest to simply add the option to disable any random changes and variability to the dispatch payload.

Looking forward to the fix.

Thanks
Peter

[Travis]

Work is underway to correct issues in the payload size and allocation methods.

One bug is that if an aircraft's load map is set to allow "just baggage," the Administrator might not see that setting and originally allocate more cargo weight than "just baggage"... only to later be restricted in a different method by not being able to load anything other than baggage.

There are a few other minor issues in play as well.

Best,