Easy workaround: create a waypoint using relative positions and make them part of your route, e.g. in the attached route we have a turning point created "EGCR 000/23" (i.e. 23NM due north of EGCR) to give us a route straight up the Manchester low-level route... no need to use the RNAV function then (which for that point would have come up with "MCT 319.3/15.9" which is not as easy-to-use in the air!).(route not attached as forum does not permit files of the type .flightplan)