lmp Posted October 1, 2017 Posted October 1, 2017 Since update 3 waypoints are now copied from the ME into the device. Unfortunately there are some problems. 1. Waypoints can't be looked up in the database. They're not treated as user waypoints or anything else - so they have no WPT page, no NRST page etc. 2. Sometimes the flight plan isn't copied correctly. I've noticed this so far when starting on a FARP, starting on an airfield seems to be more reliable. One time the flight plan was empty, another time it didn't have the FARP in it, yet another time there was just the digit "2" where the FARP should be.
lmp Posted October 2, 2017 Author Posted October 2, 2017 Also, I tried to create a waypoint from the WPT user page by inputing a radial and distance from a FARP as a reference point and it placed the waypoint somewhere beyond Caucasus.
Olddog Posted October 2, 2017 Posted October 2, 2017 I have found that for FARP names and if using WP names, there can be no spaces in the the name. If there are spaces, the FLP will not show them.
ody81 Posted October 3, 2017 Posted October 3, 2017 Since update 3 waypoints are now copied from the ME into the device. Unfortunately there are some problems. 1. Waypoints can't be looked up in the database. They're not treated as user waypoints or anything else - so they have no WPT page, no NRST page etc. 2. Sometimes the flight plan isn't copied correctly. I've noticed this so far when starting on a FARP, starting on an airfield seems to be more reliable. One time the flight plan was empty, another time it didn't have the FARP in it, yet another time there was just the digit "2" where the FARP should be. I'll check this out tonight. If you can upload the .miz file you are using for the FARP takeoff, that'd be great. Cheers
Olddog Posted October 4, 2017 Posted October 4, 2017 Imp, For Item 2. Try changing "New Static Object" of the FARP (Static Object )name, to something without a space(s) in the name.
Recommended Posts