Author Topic: errors in afcad causing crashing of p3d on exit **ADE BUG**  (Read 2892 times)

p3dx3

  • Hero Member
  • *****
  • Posts: 592
errors in afcad causing crashing of p3d on exit **ADE BUG**
« on: December 12, 2019, 05:51:58 am »
After landing at Ohare v2 my p3d would hang on exit and crash in the event viewer and create a prepar3d.cfg.txt file
In the afcad file I found these errors and I think they are the cause
Can you update the afcad and fix these errors? Thanks

« Last Edit: December 12, 2019, 01:16:18 pm by virtuali »

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50659
    • VIRTUALI Sagl
Re: errors in afcad causing crashing of p3d on exit
« Reply #1 on: December 12, 2019, 01:16:08 pm »
There are no duplicate runways anywhere in our AFCAD. What you are looking there, is likely an ADE bug, which is mistakenly identifying a double runway that doesn't exists, which was supposed to be added by ADE itself to attach the old ILS not in use anymore.

Proof of this are:

- The source .XML file doesn't contain any duplicate runways.

- Decompiling the released .BGL with ADE own BglToXml utility result in an XML file with not duplicate runways, there are only TWO fake "water" runways there, with different designators.

- Opening THAT XML ( the one decompiled by Bgl2Xml ), in ADE, shows THREE fake "water" runways, when the XML clearly has only two. Two of them have duplicated designators, which is considered a bug by ADE but, the issue is, there are only TWO water runways in both the .BGL and the .XML decompiled from that, not THREE. The extra one must have been added by ADE when opening the file, it's just not there in the scenery.

So, it's clearly an ADE bug ( we'll report it to the author ), so your crash wasn't caused by our AFCAD, for sure.

p3dx3

  • Hero Member
  • *****
  • Posts: 592
Re: errors in afcad causing crashing of p3d on exit
« Reply #2 on: December 12, 2019, 08:23:22 pm »
There are no duplicate runways anywhere in our AFCAD. What you are looking there, is likely an ADE bug, which is mistakenly identifying a double runway that doesn't exists, which was supposed to be added by ADE itself to attach the old ILS not in use anymore.

Proof of this are:

- The source .XML file doesn't contain any duplicate runways.

- Decompiling the released .BGL with ADE own BglToXml utility result in an XML file with not duplicate runways, there are only TWO fake "water" runways there, with different designators.

- Opening THAT XML ( the one decompiled by Bgl2Xml ), in ADE, shows THREE fake "water" runways, when the XML clearly has only two. Two of them have duplicated designators, which is considered a bug by ADE but, the issue is, there are only TWO water runways in both the .BGL and the .XML decompiled from that, not THREE. The extra one must have been added by ADE when opening the file, it's just not there in the scenery.

So, it's clearly an ADE bug ( we'll report it to the author ), so your crash wasn't caused by our AFCAD, for sure.

Not an ADE bug

You have 2 runways with identical names and 2 runways with runway length at or below minimum of 3.3feet

First and last runways in the list are identically named NORTHEASTW/SOUTHWESTW

First and second in list are 3.3 feet and should be increased to 3.4 feet

Then making these changes ADE compiles without errors

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50659
    • VIRTUALI Sagl
Re: errors in afcad causing crashing of p3d on exit
« Reply #3 on: December 13, 2019, 07:40:50 pm »
Not an ADE bug

Yes, it's an ADE bug, have you actually *read* how to check this ?

Quote
You have 2 runways with identical names and 2 runways with runway length at or below minimum of 3.3feet

No we don't, that's what ADE is saying, that doesn't mean they are there in the scenery. That's precisely what the ADE bug is: it's TELLING you there are two identically named runways, but there aren't any in the scenery!


Quote
First and last runways in the list are identically named NORTHEASTW/SOUTHWESTW

Again, in ADE. Not in the scenery. I'll try to explain it again:

- The source .XML file doesn't contain any duplicate runways.

- Decompiling the released .BGL with ADE own BglToXml utility results in an XML file with no duplicate runways.


Just try it yourself: download BglToXml here:

https://www.scruffyduck.org/bgl2xml/4584282773

Decompile the AFCAD, and LOOK AT THE XML. Do you see any runways with the same number and designator ? No, because they are NOT in the .BGL. Now, take the XML you JUST decompiled, and open it with ADE: duplicate runways will appear.

How else you could possibly explain this, other than an ADE bug that Bgl2Xml doesn't have ?