Tom Stian Posted June 18, 2016 Report Posted June 18, 2016 (edited) Hello Its me.. again... Had a strange issue when I tried to add a waypoint on the legs page. As you can see on the video, When adding NDB "CH" as the first waypoint, it will be placed as the last waypoint. the VOR "CBY" was working as expected. Placing CH after CBY was also working as expected. Edited June 18, 2016 by Tom Stian Quote
Litjan Posted June 19, 2016 Report Posted June 19, 2016 Yep, this has been the bane of Tom´s LEGs page editing efforts - when you add a waypoint to the route that already exists, you will usually "shortcut" to it - but sometimes you don´t want that, especially if that waypoint is like the last point of your route. Many Routes pass the same waypoint twice, once as the IAF, and then as the last waypoint with a hold... We will have to revisit these cases - and I see a solution when we start implementing "derived waypoints" where we need to add a numbering tag to waypoints to keep them apart... Let´s see. Jan Quote
Tom Stian Posted June 19, 2016 Author Report Posted June 19, 2016 3 minutes ago, Litjan said: Yep, this has been the bane of Tom´s LEGs page editing efforts - when you add a waypoint to the route that already exists, you will usually "shortcut" to it - but sometimes you don´t want that, especially if that waypoint is like the last point of your route. Many Routes pass the same waypoint twice, once as the IAF, and then as the last waypoint with a hold... We will have to revisit these cases - and I see a solution when we start implementing "derived waypoints" where we need to add a numbering tag to waypoints to keep them apart... Let´s see. Jan Good morning. My route was: LFLB - LEPA ROMAM UY23 KURIR UY16 MTL UZ16 AVN UT161 DIVKO UN852 PIVUS UZ237 SISMO UN855 KENAS So the "CH" was not at part of my route, I was trying to add that for my self made depature route when I did a takeoff rwy 18 at LFLB ^^ Quote
Litjan Posted June 19, 2016 Report Posted June 19, 2016 Ah, I see - so basically CH was added to the END of your routing, instead of the first point... I will have to see if I can reproduce that, looks indeed suspicious . Thanks for the report, Tom! Jan Quote
tkyler Posted October 1, 2016 Report Posted October 1, 2016 All fixed up. Had a > 2 when it should have been >=2. Hope that doesn't break something else Was able to put "CH" at the beginning of the route successfully though after confirming the bug before the fix. -tkyler 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.