Jump to content

Sign in to follow this  
Hippo

Navdata question

Recommended Posts

P3D 4.5 latest revision, VoxATC 7.43.

I was not getting a SID as expected when using a flight plan from Simbrief, using recent Navigraph data in Simbrief and in VoxATC.  Then I installed Herve Sors's updates, and I did get the SID as expected.  This was for a flight in Europe.

I had experienced this before (years ago) and resolved it in the same way, but I thought VoxATC now only depended on the flight plan data and not the internal P3D database.

Share this post


Link to post
Share on other sites

I apologize, what are Herve's updates?  Is that the equivalent of FSAeroData?

It's an interesting question which flight plan has authority.  I would say that the flight planner in P3D is most critical for ATC, so even with updated navdata, if you're using a flight plan in P3D, the data falls back to its database (updated by Herve or FSAD).  However, if I'm using RXP GPS or some other that does not rely on default sim data, what does VoxATC require?

Edited by Gridley
More detail

I7-7700k@4.7ghz | 32gb RAM | EVGA GTX1080 8gb | Mostly P3Dv5 (also IL2:BoX, DCS, XP11)

Share this post


Link to post
Share on other sites

It may be that the Navdata SID that you were expecting is associated with a runway with a designation which does not exist in the P3D scenery. This can be caused by new runways being added or (more likely) runway numbers changing due to magnetic variation.  If the 'Herve' update fixed the P3D scenery, that would explain the SID now being assigned.

  • Upvote 1

Share this post


Link to post
Share on other sites
16 hours ago, tegoid said:

It may be that the Navdata SID that you were expecting is associated with a runway with a designation which does not exist in the P3D scenery. This can be caused by new runways being added or (more likely) runway numbers changing due to magnetic variation.  If the 'Herve' update fixed the P3D scenery, that would explain the SID now being assigned.

Thanks for that.  In this case, the airport (LEMG) heading is corrected (from 32 to 31), and the navigation point that the SID is based on (NESDA) is added by Herve's update.  I assumed the problem I was having was due to the latter, and had no idea that it could be because of the runway.  I guess the lesson is update the data in the sim if possible.

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  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    34%
    $8,560.00 of $25,000.00 Donate Now
×
×
  • Create New...