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)

i do agree , it would be beneficial to allow the selection of a vor rather than automated selection to avoid , as you say excessive knob twiddling. i accept the closest vor is preferable but sometimes the distances can almost be the same and therefore remaining on the same vor would make life easier.

if one could override the individual leg info as , for example the route altitude per leg it would deffinately be more user friendly. either way the r nav feature saves a huge amount of planning time and is a great feature.

Hello there, I'm afraid it isn't possible to edit that column. I belive SkyDemon chooses the closest VOR/DME in order to generate the RNAV "position" of the waypoint.

Hi



Apologies if this has been asked before or is obvious. Is it possible to edit the RNAV column in the PLOG? For example, on a flight from the south to Coventry recently we tracked Daventry for much of the trip and wanted DME info for the waypoints based on DTY. However the plan uses different VOR's for different legs of that part of the trip - CPT, BNN and HON. Whilst useful for cross cuts it was a lot of knob twiddling in the cockpit. For the last leg, inbound to Coventry from DTY the RNAV uses HON but the Coventry ILS intercept is from DTY.



Just getting to grips with the software - truely excellent both as a planning tool and in the cockpit.



Thanks