|
|
Post by Herve Sors on Feb 9, 2015 12:19:25 GMT
In a few weeks, I will provide a full update of ILSs and instrument runways for the US continental states (Alaska may not be covered initially). I hope those who aim for a realistic flying environment will appreciate it. There will be some restrictions though
- Update will be for FSX only (all versions); it may work on P3D but I cannot guarantee it
- All ILSs updates as well as runway identifiers changes will be included but of course ILSs for non existing runways in FSX will not be covered; also, runway Id changes for airports without any ILSs will not be included
- A manual install will be needed (I do not intend to include it in my Navaid installer by now) but I will provide a comprehensive 'How To" text file, including backup of default BGL stock files
So stay tuned
Hervé
|
|
|
|
Post by Herve Sors on Feb 15, 2015 23:01:39 GMT
|
|
|
|
Post by jrbarrett on Feb 22, 2015 17:58:59 GMT
Herve,
Thank you for the excellent service you provide!
I have just installed the new U.S. ILS updates. This is for P3D 2.5. I fully understand that these files are not guaranteed to work in P3D.
I first backed up all default APX files to a safe location per your instructions. I then installed the replacement APX files into P3D.
I use FlightSim Commander (Version 9.6) as a planning tool, and the first thing I always do after making any scenery changes in the sim is to run the FSC Database Manager program, which scans all installed scenery to rebuild its database of airports, navaids etc.
The manager program locked up when scanning the new APX23210.BGL file, which is located in the \0202 folder. This happened twice. I restored the default version of just that one file, and the Database Manager completed its scan with no errors.
I do not know if there is actually a problem with the modified APX or not, but for some reason the FSC database program found "something" in that particular file which it unable to parse.
I have tried a couple of ILS approaches with the new APX files installed in P3D, and everything seems to be working well!
Thanks again for your outstanding tools and utilities. I shall be sending a donation to support your work.
Jim Barrett
|
|
|
|
Post by Herve Sors on Feb 23, 2015 0:10:24 GMT
Hi Jim
I presume APX23210 was the only one that raise a problem. You will confirm. I will check again this file with the BGL analytical tools I have and let you know here if I find something wrong. Thanks for the support.
-H
|
|
|
|
Post by jrbarrett on Feb 23, 2015 15:26:16 GMT
I am happy to report that the replacement APX file you sent works perfectly. The FSC Database Manager scanned it with no errors or program lock-ups.
Thanks Hervé
Jim Barrett
|
|
|
|
Post by Herve Sors on Feb 23, 2015 16:37:56 GMT
Fine..you may now wish to redownload the full North America package on my site. I corrected this one and a few others. I also add some files covering a bit more the Canada and the Mexico countries. It nows cover the overall area as described here www.aero.sors.fr/images/World_Regions.jpgAlso, other regions are now available if you're interested flying to those. I will probably upload Africa and Far East in a couple of days. Europe ILSs updates are already included in the regular World Navaids update (at least if you do not uncheck the ILS option in the install program) Best regards |
|
|
|
Post by Herve Sors on Mar 6, 2015 15:47:51 GMT
For information to all: after checking the new data, I observed that there is still some remaining mistakes especially regarding localizer beam widths (bounds are usually 3 to 6° and some were incorrectly calculated) as well as placement of some associated scenery ojects. I'm currently correcting that but it will take some time..there's about 4000 ILSs worldwide ;-) and process cannot be fully automated. Since then, the current regional ILS updates, with a very few exceptions, remain usable and much more realistic than the default FSX data
|
|
|
|
Post by Herve Sors on Mar 12, 2015 12:35:08 GMT
North America ILS data March 2015 with corrections will be uploaded today. I highly recommend those who already install first package (dated Feb 2015) update it as far as it corrects a lot of things. Now, it is fully fixed, future updates will be published on an as needed basis. Other regions updates will be available ASAP
Enjoy
Hervé
|
|
|
|
Post by Herve Sors on Mar 23, 2015 12:28:04 GMT
World wide runway and ILS data have now been updated..quite a lot of object misplacements and some ILS data have been corrected. For those who already use it, please update...(just replace files since you already have your original backup set)
I intend to provide updates on a 3-month basis considering probably most simmers do not check charts on every AIRAC cycle. However if, for professional training purpose, you need the most recent data, let me know and I will send you the latest files.
Packages will always contain the latest corrections..check file date stamp to know if it has been updated and replace as needed
Enjoy
PS: I changed this thread title accordingly..feel free to feedback
|
|
|
|
Post by Herve Sors on Apr 11, 2015 10:57:27 GMT
I've now completed all ILS, runway and associated object updates (FSX & P3D) for all world regions. I also corrected markers and added an automatic installation program. You'll find those on my dedicated web page. I also decided to update data as far as possible on every AIRAC cycle. It's not too much work (only a couple of days ). Feel free to mail me if you find any error and carefully read the included text file before installing (I kept a manual install option in case you prefer it)
Enjoy
Hervé
|
|
|
|
Post by Robert on Apr 19, 2015 10:18:18 GMT
Dear Herve,
I found some VORs in US California (SXC OCN MZB) which are still not updated. (At least the Magnetic Variation is not)
How come?
Regards
|
|
|
|
Post by Robert on Apr 19, 2015 11:01:26 GMT
Dear Herve once again,
I did some Research and found Navaid Data (Airnav.com) which Shows outdated Data for SXC OCN MZB
(SXC Variation: 15E (1975), OCN Variation: 15E (1965), MZB Variation: 15E (1965))
So my Questions are:
As AIRAC obviously does not contain Magnetic Variation Data (at least not for VORs) where do you get this Data from?
Could it be you are using outdated (VOR)-Data as shown on Airnav.com ?
Why does FSX use Magnetic Variation Data for Navaids (VORs) at all ? (as this Data after all results of the Navaid's location itself)
Would it be possible for you to update the wrong Navaids (Simulator)-Data by looking up their respective location and use that Variation Data instead?
And another one (regarding the Intersections Database (bgl)):
Is it possible to remove the Default Intersections Database within FSX to avaid having double entrys within FSX?
I very much appreciate your work !
Regards,
Robert
|
|
|
|
Post by Herve Sors on Apr 19, 2015 21:20:37 GMT
Dear Robert These data are not outdated; they are the currently calibrated values for those navaids (also called station declinations) and we have to use them if we want to match chart radials when proceeding to/from a station. It has nothing to do with the current magnetic variation at the navaid position. However, very often navaids declinations are recalibrated at regular intervals. In such cases, chart radials (airways, procedures, etc) have to be updated. More details on this concept in my FAQ list (see N°10) aerosors.freeforums.net/thread/5/faq-answers-related-navaid-updatesIt also answers the question of data source. Specifically for the US, I mainly use FAA official sources. The most accurate and detailled one can be found here webdatasheet.faa.gov/Just to have a look, select navaid, SXC then search and open the resulting PDF (note that for ILS, you'll have to enter the identifier without the leading "I"). I also check Jeppesen information (that provide navaid declinations in its radio aids airway manual text list) especially for countries that do not provide any AIP on line Regarding intersections, removing ALL outdated data will require we completely rewrite many BGLs (airport and enroute); practically it is too much work and will lead to a massive change of sim data.... Hope it will answer your questions. Thanks for the support Regards Hervé |
|
|
|
Post by Robert on Apr 20, 2015 7:34:34 GMT
Dear Herve,
thank you for the detailed explanations.
Quote:
"they are the currently calibrated values for those navaids (also called station declinations) and we have to use them if we want to match chart radials when proceeding to/from a station. It has nothing to do with the current magnetic variation at the navaid Position"
I think I completely understand now.
I just was confused by the fact that flying along a radial which is "calibrated" i.e. (SXC) to 15/E in an area where the Magnetic Variation actually is 12,2/E requires me to fly a Magnetic Course which is 2,8 Degress off.
In comparison when flying along an (updated) ILS course the Magnetic Course actually correlates to the ILS course.
(For my underatnding that is because the ILSs calibrations (and approach charts) are more frequently updated to always match the current Magnetic Variation.)
Would it be correct to say that a VOR-Radial is NOT necessarilly the same as the Magnetic Course then?
I was not aware of that until now...
Regards and thank you much !
Robert
|
|
|
|
Post by Herve Sors on Apr 20, 2015 12:40:19 GMT
Quote
"Would it be correct to say that a VOR-Radial is NOT necessarilly the same as the Magnetic Course then?
That's what I understood from the concept of VOR calibration even if I didn't go inside electronic design of such devices
When looking at Jeppesen notices and alerts and AIP updates, it appears that when a VOR calibration value is changed, airways (if any) are realigned accordingly; the same is true for arrival/departure procedure radials.
Often, calibration values are near actual magnetic variation data and are updated on a regular basis, so there's no significant difference on the pilot side
In a very few cases (including those you mentionned), calibration are off by a few degrees.
Let's take an example on what it implies
Published radial from SXC to GOATZ on C1177 high altitude airway is 213° magnetic (the value I have on my latest chart, you'll check)
Calculating true course from SXC (N 33° 22' 30.2 W118° 25' 11.7) to GOATZ (N 33° 11' 05.5 W118° 40' 14.9) on a WGS 84 model gives a result of 228.0° as initial true track and 227.9° as final true track (so let's take 228.0°). Considering the actual 2015 magnetic variation at this position is E12.2° (both IGRF-11 and WMM 2015), the effective magnetic course to proceed from SXC to GOATZ (that's what the pilot will have to follow if no wind to reach GOATZ) will be approximately 215.8°..2.8° off the published radial value. If we now take the SXC calibration value (15°E) values match..
I suspect that flying the correct magnetic course (215.8°) will just maintain the needle centered otherwise it will not. That's what the needle is for (taking into account the calibration). So certainly if you leave SXC to GOATZ on a 213° radial, needle will go off right and you will have to correct
Not sure FS modelizes that perfectly but that's why I entered the calibration data in my navaid updates. To be tested
Regards
Hervé
|
|
