First STAR Waypoint has no limits set
aaaabcv opened this issue · 4 comments
aaaabcv commented
Aircraft Version
Development
Build info
{
"built": "2024-03-10T19:20:51+00:00",
"ref": "refs/heads/master",
"sha": "47dbbd872ed469c9b1f9f5e141a8d6cb666c888c",
"actor": "Maximilian-Reuter",
"event_name": "manual",
"pretty_release_name": "master:47dbbd87",
"version": "a32nx-v0.12.0-dev.47dbbd8"
}
Describe the bug
Limits in first WP of STAR are not used if there are some. I have reproduced this with LOWW and EDDM and compared it with Littlenavmap as well as inibuilds A310.
Expected behavior
The limits are set correctly on first waypoint of star
Steps to reproduce
- e.g. use followinf enroute route for EDDM to LOWW: ODSU2C SOVIL DCT SITNI DCT BAGSI DCT MATIG DCT AMADI Q113 NAPSA in MCDU via simbrief.
- Note that NAPSA has no limits but is in the route of course
- Add Arrival NAPS1B for RW26L (the approach is not relevant)
- NAPSA should have limits B10000, B250 but they are not set
References (optional)
No response
Additional info (optional)
It appears that the limits are in the data from MSFS but are not used and (no proof) it might be an issue that the WP is already there and the merge between first STAR and existing WP is resolved by dropping the first STAR WP and omitting the limits.
Discord Username (optional)
No response
Pruznak commented
Can confirm on BIMP5U STAR to EPWA and on ALBE2E STAR to LIPZ, may have happened on more STARs, I just don´t remember.
BlueberryKing commented
Fixed with #7692