Incorrect sequencing of VA leg

[SeaHawkGaming]

Aircraft Version

Development

Build info

{
    "built": "2024-04-24T17:04:51+00:00",
    "ref": "refs/heads/master",
    "sha": "c989ce225b7a6c201346dfc73609ea45eb203ff0",
    "actor": "frankkopp",
    "event_name": "manual",
    "pretty_release_name": "master:c989ce22",
    "version": "a32nx-v0.12.0-dev.c989ce2"
}

Describe the bug

BOSNA 4W departure out of LQSA has a VA leg to 2100ft, followed by a CI leg. After correctly sequencing from the DF leg to DER30 to the VA leg to (2100) it didn't sequence to the CI leg to (INTC), nor to the CF leg to TIMID when crossing 2100. In my testing there was no difference whether DER30 was crossed above or below 2100ft. Navdata version used is Navigraph 2404.

Expected behavior

When crossing DER30 or 2100, whichever is later, sequence the CI leg to intercept the specified course to TIMID

Steps to reproduce

1. Load into LQSA
2. Select BOSNA 4W departure out of Rwy 29
3. Observe missed sequencing at end of runway

References (optional)

Database Excerpt (FSLabs ROM file of same data source):

Initial display situation after rotation

Additional info (optional)

No response

Discord Username (optional)

cookiechiara

[tracernz]

Did it eventually sequence when you got to the end of the leg displayed on the ND? Altitude-terminated legs are a bit of a weak point for us at the moment as we don’t have a tight enough coupling between LNAV and VNAV to properly predict their end.

[SeaHawkGaming]

When I initially did the flight it didn't, it just pushed the pseudo waypoint ahead of itself, but when I did isolated testing it did sequence properly once it got past the 2100 pseudo waypoint, just at like 7000ft