Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jan 26, 2020 23:57:20 GMT
I updated the P3D World Navaids and when I flew into KSEA I found myself unable to use the 16C ILS, essentially I ended up with the 34C ILS instead. Running the "uninstall" for the north american ILS update fixed the issue.
I will try and test the next update in case this is a one-time glitch. I'm very grateful for the uninstall option!
PS, while I use the DD Seattle X scenery, the AFD for this uses the stock P3D ILS.
Thanks very much,
Tim Metzinger
|
|
|
|
Post by Herve Sors on Jan 29, 2020 7:56:05 GMT
Hello Tim, It is certainly not a one-time glitch Considering I renumbered KSEA runways in the default scenery file (16L/16C instead of 16L/16R) while 16R is missing but you also have an addon scenery (with a highest priority) for KSEA, there is probably some kind of ILS interferences between both. It would be interesting you check available ILS navaids using my BGL facility scanner before and after installing the update I propose www.aero.sors.fr/bgltools.htmlLet me know |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jan 29, 2020 20:03:23 GMT
I put all three files in a single folder (the older and new 'default' airport BGLs) and the BGL from DD Scenery. Then I ran your tool on the folder. Here are the results:
Current FS version= P3D v4
Current FS path= C:\Program Files\Lockheed Martin\Prepar3D v4\
Facility type= ILS
Search type= Associated airport
Searched facility= KSEA
Scan location= Custom folder
Current custom folder=C:\Users\timme\Desktop\KSEA BGL\
Number of BGL files to analyze= 3
C:\Users\timme\Desktop\KSEA BGL\APX15150-new.bgl [Analyzed OK] 04/12/19
C:\Users\timme\Desktop\KSEA BGL\APX15150-orig.bgl [Analyzed OK] 24/05/17
C:\Users\timme\Desktop\KSEA BGL\Seattle-Tacoma Intl KSEA.BGL [Analyzed OK] 27/04/18
Number of records= 14
IBEJ KSEA 110.75 47.466589 -122.317849 QMID(9,61,60) SEATTLE-TACOMA INTL KSEA.BGL 27/04/18
ICJL KSEA 110.75 47.437796 -122.318094 QMID(9,61,60) SEATTLE-TACOMA INTL KSEA.BGL 27/04/18
ISEA KSEA 110.30 47.464916 -122.307715 QMID(9,61,60) APX15150-ORIG.BGL 24/05/17
ISEA KSEA 110.30 47.464917 -122.307763 QMID(9,61,60) SEATTLE-TACOMA INTL KSEA.BGL 27/04/18
ISEA KSEA 110.30 47.464933 -122.307715 QMID(9,61,60) APX15150-NEW.BGL 04/12/19
ISNQ KSEA 110.30 47.428220 -122.308037 QMID(9,61,60) APX15150-NEW.BGL 04/12/19
ISNQ KSEA 110.30 47.429233 -122.308028 QMID(9,61,60) APX15150-ORIG.BGL 24/05/17
ISNQ KSEA 110.30 47.429233 -122.308072 QMID(9,61,60) SEATTLE-TACOMA INTL KSEA.BGL 27/04/18
ISZI KSEA 111.70 47.435007 -122.311262 QMID(9,61,60) APX15150-NEW.BGL 04/12/19
ISZI KSEA 111.70 47.435602 -122.311256 QMID(9,61,60) APX15150-ORIG.BGL 24/05/17
ISZI KSEA 111.70 47.435602 -122.311256 QMID(9,61,60) SEATTLE-TACOMA INTL KSEA.BGL 27/04/18
ITUC KSEA 111.70 47.464919 -122.310999 QMID(9,61,60) APX15150-ORIG.BGL 24/05/17
ITUC KSEA 111.70 47.464919 -122.310999 QMID(9,61,60) SEATTLE-TACOMA INTL KSEA.BGL 27/04/18
ITUC KSEA 111.70 47.464933 -122.310998 QMID(9,61,60) APX15150-NEW.BGL 04/12/19
END OF FILE
Th e "missing" ILS is ISZI 111.70. I can't say it"s missing, just that I can't pick it up when centered on the runway. One more note. If I turn the APX15150.bgl file off (rename it to APX 15150.off), then I still get the ILSs apparently from the SEATTLE-TACOMA INTL KSEA.bgl file, although when I open the DD bgl file in ADE it shows as a stock ILS.
Best wishes,
Tim.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jan 29, 2020 21:54:50 GMT
Even more data: I've installed your update. (APX15150.bgl dated December 2019)
With your update installed and the DD Seattle X scenery disabled, When I place an airplane on 16C and tune in 111.70 I get a good signal, with proper left/right variation and the GS works. If I move to 34C the localizer switches orientation and works properly. I just lose all the scenery/gates and the western runway (16R/34L) without the DD Scenery.
With your update disabled (renamed to .off) and the DD Seattle X scenery enabled, when I place an airplane on 16C and tune in 111.70, I get a good signal, with proper left/right variation and the GS works. If I move to 34C the localizer switches orientation and works properly. I just lose all the other data from the APX15150.bgl file for other airports.
With your update enabled AND the DD Seattle X scenery enabled, when I place an airplane on 16C and tune in 111.70, I get a signal that behaves like the localizer for 34C (ITUC). It moves "in reverse". When I move to 34C, It's correct.
So it seems to me that when both bgl files are active, some sort of conflict disables ISZI and leaves ITUC functional. Either one is correct by itself. And the previous version of APX15150.bgl doesn't seem to conflict with the DD Seattle X Scenery in the same way.
Hope the additional information is useful.
Best wishes
|
|
|
|
Post by Herve Sors on Jan 29, 2020 22:01:01 GMT
Hello Tim
The way you analyzed files is a bit confusing since I do not know which files are active or not while you perform your flight. So as to sort it out, I would prefer you make an analysis using the "Active sceneries" option in the 2 different settings
1) Without any installed update (that is you have to uninstall it if not already done)
2) After installing it
Also there should be only ONE APX15150.bgl file (without any -NEW or -ORIG) since as far as the .bgl extension remains, it is active. My update just rename the original APX15150.bgl file as APX15150.bgl.p3dini so as it is not anymore active and replace it with a new one. When unisnstalling the original file is restored and the new one is deleted. Take care not to rename files by yourself otherwise it could mess up the simulator
Looking forwards
Hervé
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jan 30, 2020 15:40:26 GMT
I'm running the tester again. A couple discrepancies - with P3D v4 I don't get the option of selecting "Active Sceneries", it's grayed out, probably because all my installed scenery is active?
The backup files from installing the ILS update for a region are ending in ilsbckup, not p3dini.
The running of the check with log scan takes a very long time, but there's no way (with Windows 10) to run without the log and then copy and paste from the results.
Here's "Before" the upgrade:
Current FS version= P3D v4
Current FS path= C:\Program Files\Lockheed Martin\Prepar3D v4\
Facility type= ILS
Search type= Associated airport
Searched facility= KSEA
Scan location= Full sim folder
Number of records= 10
IBEJ KSEA 110.75 47.466589 -122.317849 QMID(9,61,60) SEATTLE-TACOMA INTL KSEA.BGL 27/04/18
ICJL KSEA 110.75 47.437796 -122.318094 QMID(9,61,60) SEATTLE-TACOMA INTL KSEA.BGL 27/04/18
ISEA KSEA 110.30 47.464916 -122.307715 QMID(9,61,60) APX15150.BGL 24/05/17
ISEA KSEA 110.30 47.464917 -122.307763 QMID(9,61,60) SEATTLE-TACOMA INTL KSEA.BGL 27/04/18
ISNQ KSEA 110.30 47.429233 -122.308028 QMID(9,61,60) APX15150.BGL 24/05/17
ISNQ KSEA 110.30 47.429233 -122.308072 QMID(9,61,60) SEATTLE-TACOMA INTL KSEA.BGL 27/04/18
ISZI KSEA 111.70 47.435602 -122.311256 QMID(9,61,60) APX15150.BGL 24/05/17
ISZI KSEA 111.70 47.435602 -122.311256 QMID(9,61,60) SEATTLE-TACOMA INTL KSEA.BGL 27/04/18
ITUC KSEA 111.70 47.464919 -122.310999 QMID(9,61,60) APX15150.BGL 24/05/17
ITUC KSEA 111.70 47.464919 -122.310999 QMID(9,61,60) SEATTLE-TACOMA INTL KSEA.BGL 27/04/18
END OF FILE
Here's AFTER the upgrade:
Current FS version= P3D v4
Current FS path= C:\Program Files\Lockheed Martin\Prepar3D v4\
Facility type= ILS
Search type= Associated airport
Searched facility= KSEA
Scan location= Full sim folder
Number of records= 10
IBEJ KSEA 110.75 47.466589 -122.317849 QMID(9,61,60) SEATTLE-TACOMA INTL KSEA.BGL 27/04/18
ICJL KSEA 110.75 47.437796 -122.318094 QMID(9,61,60) SEATTLE-TACOMA INTL KSEA.BGL 27/04/18
ISEA KSEA 110.30 47.464917 -122.307763 QMID(9,61,60) SEATTLE-TACOMA INTL KSEA.BGL 27/04/18
ISEA KSEA 110.30 47.464933 -122.307715 QMID(9,61,60) APX15150.BGL 04/12/19
ISNQ KSEA 110.30 47.428220 -122.308037 QMID(9,61,60) APX15150.BGL 04/12/19
ISNQ KSEA 110.30 47.429233 -122.308072 QMID(9,61,60) SEATTLE-TACOMA INTL KSEA.BGL 27/04/18
ISZI KSEA 111.70 47.435007 -122.311262 QMID(9,61,60) APX15150.BGL 04/12/19
ISZI KSEA 111.70 47.435602 -122.311256 QMID(9,61,60) SEATTLE-TACOMA INTL KSEA.BGL 27/04/18
ITUC KSEA 111.70 47.464919 -122.310999 QMID(9,61,60) SEATTLE-TACOMA INTL KSEA.BGL 27/04/18
ITUC KSEA 111.70 47.464933 -122.310998 QMID(9,61,60) APX15150.BGL 04/12/19
END OF FILE
|
|
|
|
Post by Herve Sors on Jan 30, 2020 22:32:30 GMT
Ok thanks will analyze that tomorrow (a bit busy) tonight and let you know
[Later on]
Hello Tim,
The problem is clearly due to an interference of modified KSEA data (runway renumbering and ILS corrections) in the stock BGL files I provide and the Seattle scenery you also have
I suspect it is due to an ineffective "Exclude" of stock data by the Seattle scenery due to the fact I renumbered the KSEA runways
There's no simple solution. The only I can see by now is to cancel all changes I made to KSEA data in the stock APX15150.BGL file. Just removing this single file and restoring the original file (the one with a .ilsbckup extension should do the trick although you will lose the updates made to other airports in this file (KBFI, KDLS, KEAT, KGRF, KHIO, KMMV, KOLM, KPDX, KPWT, KSPB, KTCM, KTIW, KUAO, KVUO and KYKM mainly). May be it is not so much a problem on your side depending on the flights you usually like to perform. Another possibility is that I provide you a modified file in which only KSEA changes are removed. It is possible but, of course, it will have to be redone in case the file is updated later on (although it should not be so frequent). Let me know. For further communication, please feel free to use my hotmail email (link is on my site)
Regards
Hervé
|
|
|
|
Post by Richard Keen on Feb 20, 2020 23:03:11 GMT
|
|
|
|
Post by Richard Keen on Feb 20, 2020 23:19:15 GMT
Hi tmetzinger 1:) download Airport inspector from this page www.aero.sors.fr/navaids.html2:) open it and click on select data then Analyze singe file (make sure your Flight sim is ticked below it) 3:) open the stock BGL file for KSEA which is APX15150.BGL and it is in scenery /0101 /scenery Back the file up 3:) under Nav editor ILS editor ..for the airport ICAO put KSEA and just delete the ILSs for the effected runways you will sadly have to do this every Airac but at least you will have correct data for all the airports around SEA and you will have working ILSs again at KSEA |
|
|
|
Post by niksan29 on Feb 21, 2020 17:44:40 GMT
you will sadly have to do this every Airac just want to add: no need to do it every time, will be perfect only when the date of the file from the update pack(from Herve) changes  |
|
