I originally wrote this editor so that I could fly fast and low through valleys. Thus if you open a flight plan to make a quick edit of>a flight level, for example, you have to re-type the entire>file name to save it under the same name.1. The "save" dialogue does not default to the opened file>name. So using it is pointless for this purpose. I can change>the flight level to IFR levels with this utility but not the>IFR/VFR flag. After getting Radar Contact, for example, I frequently>change my previous VFR flight plans to IFR before loading them>in ActiveSky and Radar Contact for processing. This is one of the most common reasons I have to open>an existing flight plan outside FS or FSNavigator in an>editor. (i.e., you can't use>this utility to change a flight plan from VFR to IFR or vice>versa). I was surprised that seemingly the only parameter left off>for editing was the Type=VFR or IFR. In the meantime, I'm not holding my breath about the next version anymore. From what I've read here and elsewhere the focus for FSX is on arcade play and portability to XBOX, so i wasn't expecting much in the way of improvements to things that excite simmers, like weather, ATC, flight planning, aircraft dynamics, etc. As for FSX, I will be pleasantly surprised if they address the flight planner in the next version. Thus if you open a flight plan to make a quick edit of a flight level, for example, you have to re-type the entire file name to save it under the same name.All and all, a big thank you to the author. The "save" dialogue does not default to the opened file name.
I can change the flight level to IFR levels with this utility but not the IFR/VFR flag. After getting Radar Contact, for example, I frequently change my previous VFR flight plans to IFR before loading them in ActiveSky and Radar Contact for processing. This is one of the most common reasons I have to open an existing flight plan outside FS or FSNavigator in an editor. (i.e., you can't use this utility to change a flight plan from VFR to IFR or vice versa). I was surprised that seemingly the only parameter left off for editing was the Type=VFR or IFR. In the spirit of feedback, in case the author reads this, a couple of quick items for the next version: 1. I use FSnavigator for real flight planning but for teaking an existing flight plan (e.g., to make a quick change in the FL or starting position) this is promising.
0 kommentar(er)
