For example,
DNMM […] BUT ATS32 IRO ATS17 KIMKO […] HUEN passes SB validation even though it’s not actually valid.
BUT ATS32 IRO is valid (IRO NDB here)
IRO ATS17 KIMKO is valid (IRO VOR there)
BUT ATS32 IRO ATS17 KIMKO is invalid, because the two airways do not actually share the same IRO navaid
I guess it’s not necessarily an easy fix, but it’s pretty annoying, as the error then happens later in e.g. custom aircraft with a more robust route parser, whereas it would be much more useful to catch the error earlier, at the simBrief stage.
Regards,
Tim