Departure is missing the SNS 264 radial intercept to SHOEY. The right turn to 329 HDG is fine but goes into SUSP at the MANSEQ waypoint.
Is this the convo you had with Matt on Discord?
I think this information might be helpful:
“Looks like a navdata issue to me. Seems like that’s coded as a VM and not a VI leg”
Also - Topic Author is reporting Stock Navdata (Navblue)
Yes, I was talking to Matt, but he also said to submit it.
Has this ever been acknowledged?
The discontinuity still exists.
Still not sequencing to the next waypoint. Another departure with two headings and an intercept is the LINDZ 9 at Aspen, KASE. The chart calls for two headings and then intercept the LOC outbound, but MSFS flies direct to LINDZ after reaching 9100. At least it doesn’t have the discontinuity. I’ve flown both of these departures in the Garmin Aviation Trainer application. Garmin designates different leg types, HDG and HDG to intercept, nothing like a MANSEQ. Out of Aspen, first leg is climb to 8240 (400 AGL), then a HDG leg 343 to 9100, then another HDG leg 273 with an intercept.
The MRY5 flies in the Garmin Trainer exactly like the published procedure. This is a GTN trainer, not a G1000 Nxi, so I checked the Nxi manual and it works the same way. I wonder if Garmin has to tweak the nav data they get.