|
|
Post by dirknl on Feb 12, 2018 10:56:26 GMT
Hi Hervé,
The fact that another product (AivlaSoft EFB) presents wrong info is not 'your cup of tea'. I know. But maybe you can give me an expert opinion on this. So far AivlaSoft's creator did not yet come up with a solution. This is what happens:
My P3Dv4 is regularly updates by Navigraph and your World Navaids package (recently 1802).
When I use the ILS inspector for the stock airport ENTO it reads the APX50100.bgl file to find for ENTO:
ILS/DME 36 SFJ 110.95
and ILS/DME 18 TRP 108.30
Checking the AIRAC data gives exactly the same.
But...
Then I fire up AivlaSoft EFB, it comes up at ENTO with the ILS BC info for an ILS approach on RWY18:
Loc SFJ 110.95 App.crs. 358 (Rwy 178) and for an ILS approach on RWY36:
There are only a VORDME Rwy 36 and a RNAV Rwy36 and no ILS.
Could it be that there is some sort of index that points to the wrong data?
I had the same situation in P3Dv3 and that disappeared when I bought Aerosoft's ENTO for FSX, installed via the Migration tool. Then the problem was solved by the add-on of course. But this add-on gives serious malfunctions in my Q400 when installed in P3Dv4. So I'm back on P3Dv4's default ENTO.
It would be nice if you could shine some light on this.
Thanks in advance,
Dirk
|
|
|
|
Post by dirknl on Feb 13, 2018 19:39:11 GMT
On request by the creator of AivlaSoft I checked if his program uses the correct file and it does: APX50100.bgl.
Could it be that the ILS Inspector ignores what's in that file and uses the AIRAC data instead when I check via the Nav Data tab?
Dirk
|
|
|
|
Post by Herve Sors on Feb 13, 2018 23:15:21 GMT
Hi Dirk
>>Could it be that the ILS Inspector ignores what's in that file<<
No it won't. The Inspector (now renamed Airport Inspector & Editor but it did not change its analysis routines) reads what is contained in the file..no less no more
Regarding the latest provided APX50100.bgl (dated 12-Oct-2017) as contained in the World Navaids package, ILS data for ENTO are those you described in your first post. You can also easily check for that within the sim. You may also open the APX50100.bgl file with some other editors (such as ADE or FSX-Planner) and you will see the ILS information is identical.
So, if AivlaSoft did not provide the same information, it means it doesn't read the modified file as expected (Organization of BGL files is highly standardized and the Airport Inspector & Editor or any previous ILS Inspector version just read the raw information from them).
Now, from your post it seems that your problem is not the ILS definitions but the associated approaches. This is of course another subject. From what you describe, I cannot provide you a definitive answer.
Let me know
Hervé
|
|
|
|
Post by dirknl on Feb 14, 2018 9:29:29 GMT
Hi Hervé,
This is what Urs (AivlaSoft EFB) came up with:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Hi Dirk,
I did some investigation and that's the outcome:
The file you provided herein (APX50100.bgl) does not have the correct assignments for the following fields
- 0x0C 'ICAO identifier for primary ILS'
- 0x10 'ICAO identifier for secondary ILS'
where primary means runway 18 and secondary means runway 36.
Currently the values are "SFJ" for primary (18), and 'blank' for secondary (36).
The correct values should be "TRP" for primary and "SFJ" for secondary.
Maybe this information should you post on Hervé Sors' forum.
Furthermore it is interesting that the 'Airport Design Editor' (ADE) lists 4 ILS, two for each of the runways (see screenshot). I guess this is another indication that this BGL-file is not properly defined.
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Unfortunately the screenshot did not come with the copy/paste from the AivlaSoft forum. But I think the written info is sufficient for you.
I am a bit hesitating to download and learn to use ADE, but since it seems that 'something' in the bgl is not correct according to Urs, I think I'll wait for your 1803 update presuming that the problem is corrected by then.
Greetings
Dirk
|
|
|
|
Post by Herve Sors on Feb 14, 2018 18:46:35 GMT
Thanks Dirk. After looking at the XML file that was used for generating the APX50100.bgl, there was indeed a problem with the primary/secondary assignment. However know it has absolutely no effect in the sim the reason why I didn't detect it before your post (and thanks for that). Clearly Aivlasoft doesn't like it and, anyway, it has to be corrected.
I will send you an updated file (by email) you will be able to test (just replacing the old one), before it is included in next update, and you'll let me know
>>Furthermore it is interesting that the 'Airport Design Editor' (ADE) lists 4 ILS, two for each of the runways (see screenshot). I guess this is another indication that this BGL-file is not properly defined.<<
No, the problem is that if you use ADE without selecting a specific bgl file via the "Open Airport from BGL" menu (and not Open Airport or Open Stock Airport) , ADE will display stock navaids in addition to those inside the new file (so here there will be 4 ILSs). It is a well known problem with ADE!! You may check there's only 2 ILSs in the file by opening it with ADE using the option "Open Airport from BGL" or using another Editor that only reads raw data (such as the old FSX-Planner or my Airport Inspector and Editor software).
Regards
Hervé
PS: I sent you an email so as to send you directly the corrected APX50100.bgl (but there's 2 possible files depending on your World Navaids Install options)
|
|
