Jude 190 Posted December 20, 2012 Share Posted December 20, 2012 If you take a look at the screenshots, you can see that there should be a straight line between these two waypoints. I created a flight between EIDW-EGLL RWY27R arrival. The aircraft flew the arc rather than a straight line to the next waypoint IRR4 Link to comment Share on other sites More sharing options...
Jaap K. 43 Posted December 20, 2012 Share Posted December 20, 2012 This bug seems to have been introduced when solving another nav issue, just before release. I've seen it a couple of times already. Will be looked into. It's not pretty, but if you arm approach before reaching IRR75 the bus will pick up the localiser, and not do the loop. Link to comment Share on other sites More sharing options...
Jude 190 Posted December 20, 2012 Author Share Posted December 20, 2012 Thanks Jaap, It's for the benefit of other users that I'm posting this. Link to comment Share on other sites More sharing options...
CritterDC9 8 Posted December 21, 2012 Share Posted December 21, 2012 Yea I still have that issue after the hotfix but in my case it was on approach to CVG back in the States. Link to comment Share on other sites More sharing options...
JRBarrett 675 Posted December 23, 2012 Share Posted December 23, 2012 Had the same thing happen on the ILS 30 approach at Long Beach KLGB. Fortunately, I did capture the localizer prior to getting to the looped segment, so the aircraft did not actually try to follow the curved path Link to comment Share on other sites More sharing options...
Jude 190 Posted December 24, 2012 Author Share Posted December 24, 2012 On the other hand, EGGP-EIDW works perfectly. Link to comment Share on other sites More sharing options...
golyaht 11 Posted December 25, 2012 Share Posted December 25, 2012 Also see this issue on ILS 36R into KMCO. Sounds like a logic issue, rather than some kind of problem with AIRAC data. All in all, not a big deal. As was stated earlier, arm the LOC just prior to intercepting this line and good to go. Link to comment Share on other sites More sharing options...
Jude 190 Posted January 15, 2013 Author Share Posted January 15, 2013 Fixed with 1.03, mark as solved if you wish Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.