I recently picked up the Leonardo MD8x pack and noticed simbrief giving me odd routing, I primarily fly the 73x and A3xx with simbrief. Examples:
KSMF → KLAX
73x: FTHIL3 FRA REBRG IRNMN2
MD8x: LIN J189 AVE FIM SADDE8
KSAN → KLAS
73x: PADRZ2 CHKNN SEBBY YELAH MISEN RNDRZ2
MD8x: BRDR7 JLI TRM TNP LARKK1
I understand the Leonardo MD8x to be RNAV capable for departures and arrivals, just not RNAV GPS approaches.
Then you need to add RNSV RNAV capability to a custom simBrief profile would be my guess. Although why it would have RNAV off by default is a bit weird, given how almost every MD80-something addon out there does have at least enroute RNAV capability.
Regards,
Tim
I’m not familiar with the RNSV acronym. Typo? I don’t see a way to add RNAV capability to a custom airframe off the MD8x. I assume it would be done in this area?
The ICAO equipment seems to include an inertial reference system (I), satellite navigation (G) and PBN “RNAV 5 all sensors” capability (B1), so it makes no sense that simBrief would give you a non-RNAV route by default given the pictured profile above.
The plot thickens.
Regards,
Tim
Same behavior here, BTW, regardless of how the airframe is configured. Something is needlessly hardcoded somewhere in the base profile would be my guess.
Regards,
Tim
Tim - Thanks. I tried a custom profile based off the default and noticed the same results (no RNAV dep/arv). I appreciate you chiming in and the insightfulness on the ICAO equipment translation.
The FTHIL3 departure is an RNAV 1 SID. The issue with the MD8x airframes was that the default PBN codes did not include D# or O#, therefore the aircraft could not use any RNAV 1 SIDs.
I’ve updated the default MD8x airframes with the proper PBN codes, should be fixed now.
Cheers,
Quick test looks good with the same routing in my example. Appreciate it!
That would explain it. Cheers!
Regards,
Tim
