Jump to content
Sign in to follow this  
bsal

RF Leg Bug

Recommended Posts

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.

1e241b3d45e480fab5db5dc79d37c459.png

 

Straight line drawn by the airbus

a7372f7b64b2fdffae507e4e1b131e35.png

 

 

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'.

cf7bd48751aee25bce4fc910edb4cb3b.png

Share this post


Link to post
Share on other sites

The 64 bits busses got updated code for that and we are no longer working on the old code. sorry.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×
×
  • Create New...