I have a "Pro" subscription and am using v4.4.2. I have two questions about Vertical Profile view (see attached screenshot):
1. I can't figure out what the brown line is that crosses the vertical profile (starting at 4500ft on the left). It's not ground, it's not an airspace, and it doesn't seem to have anything to do with my route. What is it?
2. I find it is too easy to accidentally change the route altitude by touching the magenta line in the vertical profile. Worse, any change to the altitude is accepted with no confirmation and no way to undo. This seems wrong. Can I prevent such changes, e.g. by locking the vertical profile?
Thanks,
-- Terrence
Hi Terrence,
That transparent brown area represents the highest terrain using a 5NM path width along each side of your route. The less-transparent brown area represents the highest terrain using a 0.1NM path width along each side of the route. So you know when you're current flight altitude is in the transparent brown area you should be careful deviating from your track because of higher terrain around you.
I agree with you about the accidental change of the route altitude in the VPV. For the normal map we have the option to force tap&hold( menu->preferences ->Rubberband by Tap & Hold. I was convinced this setting also effects the VPV but I jut tried it and it doesn't make any difference, sorry. I think the best solution would be to make the VPV listen to that "rubberband by tap&hold" also?
Hi Rob,
Thanks for the quick reply. The brown line explanation makes sense.
I agree VPV should listen to "rubberband tap & hold", but it also MUST require to confirm any change. Right now, the behavior is disrupting and potentially dangerous because you can change the altitude without realizing it with a simple accidental swipe, and even if you realize something changed then there is no 'undo' so you're now left trying to figure out what you changed and then fix the route while flying.
Edit: Alternatively, allowing to make the VPV "read-only/not changeable" may also be an option. I feel that changing altitudes may be something that could be limited to the route editor, i.e. the VPV only shows the resulting route, but doesn't allow to change it.
In any case, to me this is a feature/bug that needs to be addressed before I would consider using Easy4VFR in a real cockpit. Do you want me to file a feature/bug fix request?
Thanks,
-- Terrence
Hi Rob,
Excellent, thanks!