Insane routing for KLAX ORCKA5 MISEN RNDRZ2 KLAS

[DrS0ftware]

Are you using Developer Mode or made changes in it?

Yes

Have you disabled/removed all your mods and addons?

Yes

Brief description of the issue:

The flight planning engine does not know how to handled overlapping SIDs and STARs. I copied a real flight, AAL1763, with the routing KLAX ORCKA5 MISEN RNDRZ2 KLAS. Taking off 24L and landing ILS 26L. The route that I would expect is KLAX (DLREY FABRA, KLIPR, KEGGS, COOPP) ORCKA NNAVY (MISEN TEDDE WATEV TOETS RNDRZ GRMMA BUETY ENNVY REDQN TWAFL) BERBN (BISHP GOGOG KODSE HUXAR, SHAND, RELIN) LAS. However, because ORCKA5 technically ends at BLAZN LAS, the flight planner will plan NNAVY BLAZN LAS, then in order to take up the arrival, will send you back west again to MISEN, but the arrival ends AT BERBN BLD, so then you get routed to BLD. The ILS approach starts at BLD, then LARRE, then HUXAR et al. In the MSFS navlog, it is not possible to delete out segments of an ILS approach. Thus, although BLD is depicted, you can’t delete BLD, nor PRINO, nor LARRE. Also, I have gone insane trying to fix all the waypoints in the Boeing 747-8 FMS… there seem to be bugs where if you want to insert a waypoint at the top of page 2, clicking the top softkey ends up putting the navaid at the top of page 1! YIKES!

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

Enter the following into a flight plan KLAX/24L ORCKA5 RNDRZ2 KLAS/ILS 26L

PC specs and/or peripheral set up if relevant:

Xbox Series X

Build Version # when you first started experiencing this issue:

1.29.30

---

For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

[CharlieFox00]

Are you able to select the MISEN transition on the ORCKA 5 departure? Filing that should look like ORCKA5.MISEN

[DrS0ftware]

It turns out that if you delete some of the overlapping waypoints on the way out, it will automatically end up routing to MISEN. Looking at the FMS, it also adds some wierd waypoints. EED and ZELMA, that aren’t on the arrival at all.

It doesn’t look like the 747-8 FMS can modify the departure – it just goes in as a bunch of waypoints. Maybe the A320 model can do that. Will have to try and get back to you.

Also, I tried to refly the route this morning. Copying it from the logbook discards the edits I made in the Navlog when I saved it, and also discards the cruising altitude. It looks like redoing a flight from the logbook just copies the boxes at the top and not the actual flight plan.

Also, on departure, the aircraft turns the wrong way – it is supposed to turn left not right, but it turns right instead.

And one more thing, the taxi guidance seems to suggest I line up the wrong way for takeoff – i.e. point off the beginning of the runway (east) instead of the end of the runway (west).

Is it just me or are there some serious bugs in the 747 model?