Too many passengers boarding

Version: 1.15.17.0

Frequency: Consistently

Severity: Blocker

Bug description: Not 100% sure but it seems there is a bug or the minimum for passenger boarding is 16. I have 8 passengers in my navigation passenger graph but 16 are coming out of the bus and 8 board and the other 8 are trapped.

Is there a way to fix this situation?

Hello,

I checked with the da62 sdk and it was working.
Can you test with the da62 navigation graph passengers to see the behavior ?

Can you use send us your project ?
See How to report a bug or crash

Regards,
Boris

1 Like

I compared the code and found that when you add the navigation_graph_passenger.cfg data for the passengers and the plane entrance, the PLANE_ENTRANCE needs a tag called PLANE_ENTRANCE.

The SDK confused me to put a tag called SIT for the passengers as seen below (left side). But I also have this tag added for the actual asset for each passenger (right side). And If I remove the one from the asset then nothing shows up. If I remove the one from the preset navigation_graph_passenger.cfg then it fixes the bug from 16 coming off the bus to 8. So my question is why is the SDK telling me to add the tag sit for both locations?

Seems to me the SDK Commercial_Passengers is not actually telling you to add the tag SIT for the passengers but is showing illustrations as if it would have this tag. Where as SpawnPilot does require specific tags and the PLANE_ENTRANCE is also another has a required tag. So conclusion is the tag SIT is only for the asset and not the navigation graph passengers. The copilot does have multiple options for tags based on mixed roles. Anyways I now have this convoluted system figured out. Was a learning curve.

How can I scale the payload station icons? It seemed to be too small when I had the SIT tag and now it’s too big when fixed. Also it’s a square and I think the DA62 they were circles. So any help would be appreciated.

I logged two bugs. One to update the documentation and make it more clear about plane_entrance and sit tags and the other one for the efb seat behavior.

I will let you know when I know more.

Regards,
Boris

2 Likes

I’m not sure if you are aware of this but you can make your plane “larger” in the efb and have seat with more space around it.
This could mitigate your issue.

Regards,
Boris

1 Like

I was aware but when I kept testing it was during the period when I had an issue and all my squares were super small. So nothing really changed but the scale of the background. I will test again now that I have the standard larger squares.

By the way why do I have squares when the DA62 has circles? Even my luggage icons are circles.

Here is all three sizes. What I found is the background did not change only the icons. So this is not correct. Far left is Large, then Medium and far right is Small.

I tested this with the DA62, and after updating the aircraft size in panel.xml the EFB zoom adjusted correctly. I’m not sure why it isn’t working on your side.

You can send us your project, I will take a look at it. See How to report a bug or crash.

Regarding the seat icons, they appear as circles when no navigation graph is associated there is no way to change the icon type.

Regards,
Boris

It’s so strange as it’s now working today when I tested it. So I suspect it had something to do with some of the other aspect of the project that was not complete. Because the tablet info itself has not changed but yet it works perfect now.

Thanks @Boris

1 Like

Hello,

Tagging this as fixed as there is no plan to update this part of the documentation and the placement issue you had was caused by another file as you said (We could not repro the original issue).

Feel free to open a new bug report about this if needed.

Regards,
Boris

1 Like

This topic has been automatically closed after 60 days of inactivity since it was marked as fixed.

If there is important new information about this same report, you can use the “Request reopen” button below to ask the moderation team to review it again.
For other issues or broader discussion, please open a new topic in the appropriate category.