bsal 38 Posted December 18, 2019 Share Posted December 18, 2019 This has been bothering me for some time now so I've decided to make a post about it maybe it can be rectified. Not sure if the problem is caused by the navdatapro coding (also happens with navigraph) or the aerosoft airbus how it reads Radius to fix RF legs in the database. Bare with me for a second. There are more but we'll use this one for an example, KBZN Bozeman RNAV12-Z via JOXIT, The arc between TETBY and JURAL is drawn as a straight line on the 32bit aerosoft airbus (probably the same on the 64bit) if someone could check for me that would be great. Please login to display this image. Straight line drawn by the airbus Please login to display this image. The RF legs seem to be coded correctly in the database, you can see RF between both TETBY and JURAL, the issue seems to be caused by the APPTR section ending with an 'RF' leg then beginning the FINAL with the same name waypoint JURAL as a different leg type 'IF'. Please login to display this image. Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted December 18, 2019 Aerosoft Share Posted December 18, 2019 The 64 bits busses got updated code for that and we are no longer working on the old code. sorry. Link to comment Share on other sites More sharing options...
bsal 38 Posted December 18, 2019 Author Share Posted December 18, 2019 That's a shame, thanks for the reply Mathijs. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.