Does anybody know whether V3 has updated navigational aids in their .bgls? Or are the data still based on the same databases from 2006 like FSX so that we need to use AIRAC updates as provided here http://www.aero.sors.fr/navaids3.html

 

Regards,
Chris

I'd like an answer to this too. 

 

Thanks

I'm not sure, but I would guess that if the data were updated, someone would have made a big deal of it.

Herve plans on updating the installers for the 1511 airac, 1512 at the latest (from his forums)

It is a bit disappointing that a $200 product still uses decade old navaid information.

 

I can understand the effort behind updating airport AFCADs, but at least update the damn NDB and VOR information.

It is a bit disappointing that a $200 product still uses decade old navaid information.

 

I can understand the effort behind updating airport AFCADs, but at least update the damn NDB and VOR information.

 +1

TMK they have made no changes to the database.

 

Vic

It is a bit disappointing that a $200 product still uses decade old navaid information.

 

I can understand the effort behind updating airport AFCADs, but at least update the damn NDB and VOR information.

The cost to license the data as well as the labor required is most likely the reason for not doing so.

It is a bit disappointing that a $200 product still uses decade old navaid information.

 

I can understand the effort behind updating airport AFCADs, but at least update the damn NDB and VOR information.

+99

 

But, if we need to use AIRAC updates as provided here http://www.aero.sors.fr/navaids3.html , what would be the net net?

 

What would be the upside and downside of modifying V3 with the above data?

 

Chas

FWIW... Not a navaid, but V3 still shows runways 27R and 27L at KOAK. They were changed to runways 28R and 28L a while ago due to magnetic drift.

OK, then let's wait until Herve provides the updates for P3D3...

 

By the way, I was asking a technical pilot whether the magnectic variation is adapted in the FMC software according to the "cycles". He states that this is not necessarily the case. In fact, the magnetic variation in the aircraft's software very often is at the stage of factory delivery. It may affect northern aeras more than others, and then in particular if you plan to do NDB approaches. AIRACs of course are monthly updated as we all know.

I am still using the magnetic var table from 2010 for the sim, although 2015 is available.

 then let's wait until Herve provides the updates for P3D3.

 

Installer has now been updated (v7.30) and made available. I needed some tests before but there's no drastic registry inscription changes between V2 and V3 (except of course string data).

 

  

I was asking a technical pilot whether the magnectic variation is adapted in the FMC software according to the "cycles". He states that this is not necessarily the case

 

He is true. It is important to distinguish between current magnetic variation at aircraft position (as provided for us by the magdec.bgl table) and navaid calibrated station declination that may affect GPS/FMC/VOR approach courses, radial interceptions as reported by instruments and/or visual displays. First one is what it is at a given date on earth, so it is important to have it updated as far as possible, second one depends on when navaid has been calibrated (could be well before actual date) and is included in the navaid records. Some more details on this concept in FAQ 10 on my forum with some explanatory links

http://aerosors.freeforums.net/thread/5/faq-answers-related-navaid-updates

 

V3 still shows runways 27R and 27L at KOAK. They were changed to runways 28R and 28L a while ago due to magnetic drift.

 

 There have been  at least 50+ runway id changes in the US on major airports and much more world wide, not talking about changed/added/deleted ILSs..For those not using dedicated sceneries correcting that (the preferred solution), you may give a try to regional ILS/Rwy updates I provide and that have been built so as to update everything on a regular basis (except of course general airport design), that is Rwy Ids (when they exist and their position didn't change), ILSs, PAPIs/VASIs. However, be aware some data may be "broken" mainly integrated GPS approaches and AI behavior. However, it could help improve realism especially for those who do use real current data and regret FS/P3D data are still 10 years old (but as n4gix said and explained, these stock data will probably never been updated)        

the cost of changing all the airport and runway data in a flight sim would be astronomical due to the time it would take. I doubt if anyone would want to pay for that.  

the cost of changing all the airport and runway data in a flight sim would be astronomical due to the time it would take

Literally, astronomical is IMO a bit pessimistic. Depends on what the aim and profit could be (because it is payware anyway)..there's around 150,000 airports world wide but probably only 10,000- with IFR capabilities (whatever the precision/non precision approach is), that is those we are mainly interested with. For big companies with 20+ designers, and let's say a 1 year dead line, it could be possible adequately priorizing data changes (I didn't make the work load calculation though..). Let's dream       

the cost of changing all the airport and runway data in a flight sim would be astronomical due to the time it would take. I doubt if anyone would want to pay for that.

It can be done - but it the case of FSX/FSX-SE/P3D, it would require a major change in the underlying design of the scenery. MS made the decision early on in the franchise to hard-code nav aids into the .bgl files that make up the underlying scenery - so modifications require de-compiling - modifying - recompiling .bgl files on a case-by-case basis.

 

X-plane uses a very different system - one which I hope may eventually be adapted for P3D (and for whatever new flight simulator Dovetail comes up with).

 

In XP, nav aids, VORs, NDBs, ILS etc. "sit on top of" the underlying scenery - rather than being "baked in". All of the world's nav aids are defined in a centralized group of 4 or 5 text files, which can be (and are) easily updatable. In fact, Navigraph issues monthly updates for all the XP-10 nav aids, just as they do for individual aircraft add-ons.

 

There are other advantages to using a central database in XP-10 for those who want to fly with maximum real-world accuracy. It is very easy to go into an XP menu and mark any individual VOR, NDB etc as being unavailable. I have done this for my local VOR (Elmira VOR, ULW) which is currently out of service until 2016 because the facility is being upgraded with new equipment. Having it unavailable affects the initial procedures for the two ILS approaches at KELM, and current R/W approach charts have been amended by NOTAMS to reflect this.