Jump to content
Sign in to follow this  
knich

95: Excludes Error?

Recommended Posts

It says that parking position H23 in your LFPG.xml airport file has got more than two neighbouring parking positions that overlap with H23.

Which is weird, that cannot be...can it?

You should fix  it by editing the LFPG.xml file (probably in PPG_MSFS/airports folder). See the <afcad> section.

 

 

Edited by kiek

Share this post


Link to post
Share on other sites
4 hours ago, kiek said:

It says that parking position H23 in your LFPG.xml airport file has got more than two neighbouring parking positions that overlap with H23.

Which is weird, that cannot be...can it?

You should fix  it by editing the LFPG.xml file (probably in PPG_MSFS/airports folder). See the <afcad> section.

 

 

Hi..Here are the Hs..what am I editing?  There are multiple exclude H23s

<parkpos id="H1" latitude="49.016132" longitude="2.578671" heading="355.7" radius="21.0" cargo="false" ramp="true" />
    <parkpos id="H10" latitude="49.015327" longitude="2.573593" heading="355.3" radius="32.0" cargo="false" ramp="true" />
    <parkpos id="H11" latitude="49.013882" longitude="2.574772" heading="175.2" radius="36.0" cargo="false" ramp="true" />
    <parkpos id="H12" latitude="49.013813" longitude="2.573779" heading="175.5" radius="36.0" cargo="false" ramp="true" />
    <parkpos id="H2" latitude="49.016079" longitude="2.577679" heading="355.8" radius="17.0" cargo="false" ramp="true" />
    <parkpos id="H20" latitude="49.016006" longitude="2.578802" heading="355.5" radius="26.0" cargo="false" ramp="true" />
    <parkpos id="H21" latitude="49.015972" longitude="2.578175" heading="355.1" radius="32.0" cargo="false" ramp="true" />
    <parkpos id="H22" latitude="49.015942" longitude="2.577584" heading="355.4" radius="26.0" cargo="false" ramp="true" />
    <parkpos id="H23" latitude="49.015991" longitude="2.578542" heading="355.6" radius="26.0" cargo="false" ramp="true" />
    <parkpos id="H3" latitude="49.016026" longitude="2.576702" heading="355.6" radius="18.0" cargo="false" ramp="true" />
    <parkpos id="H30" latitude="49.015903" longitude="2.576820" heading="355.4" radius="33.0" cargo="false" ramp="true" />
    <parkpos id="H34" latitude="49.015869" longitude="2.576203" heading="355.4" radius="35.0" cargo="false" ramp="true" />
    <parkpos id="H4" latitude="49.015972" longitude="2.575699" heading="355.4" radius="21.0" cargo="false" ramp="true" />
    <parkpos id="H40" latitude="49.015839" longitude="2.575616" heading="355.5" radius="19.0" cargo="false" ramp="true" />
    <parkpos id="H5" latitude="49.013721" longitude="2.578977" heading="174.9" radius="23.0" cargo="false" ramp="true" />
    <parkpos id="H50" latitude="49.013817" longitude="2.579060" heading="174.9" radius="23.0" cargo="false" ramp="true" />
    <parkpos id="H55" latitude="49.013794" longitude="2.578552" heading="174.4" radius="23.0" cargo="false" ramp="true" />
    <parkpos id="H6" latitude="49.013672" longitude="2.577995" heading="174.4" radius="23.0" cargo="false" ramp="true" />
    <parkpos id="H60" latitude="49.013763" longitude="2.577880" heading="174.1" radius="36.0" cargo="false" ramp="true" />
    <parkpos id="H65" latitude="49.013790" longitude="2.578480" heading="173.6" radius="23.0" cargo="false" ramp="true" />
    <parkpos id="H7" latitude="49.013622" longitude="2.576997" heading="174.8" radius="23.0" cargo="false" ramp="true" />
    <parkpos id="H70" latitude="49.013725" longitude="2.577102" heading="173.9" radius="23.0" cargo="false" ramp="true" />
    <parkpos id="H8" latitude="49.013569" longitude="2.576010" heading="174.8" radius="23.0" cargo="false" ramp="true" />
    <parkpos id="H80" latitude="49.013672" longitude="2.575900" heading="174.8" radius="23.0" cargo="false" ramp="true" />
    <parkpos id="H87" latitude="49.013699" longitude="2.576495" heading="174.3" radius="23.0" cargo="false" ramp="true" />
    <parkpos id="H9" latitude="49.015396" longitude="2.574582" heading="355.4" radius="32.0" cargo="false" ramp="true" />

<parkpos id="H1" airls="" excludes="H20,H23" />
    <parkpos id="H10" airls="" />
    <parkpos id="H11" airls="" />
    <parkpos id="H12" airls="" />
    <parkpos id="H2" airls="" excludes="H22" />
    <parkpos id="H20" airls="" excludes="H1,H23" />
    <parkpos id="H21" airls="" excludes="H23" />
    <parkpos id="H22" airls="" excludes="H2" />
    <parkpos id="H23" airls="" excludes="H1,H20,H21" />
    <parkpos id="H3" airls="" excludes="H30" />
    <parkpos id="H30" airls="" excludes="H3" />
    <parkpos id="H34" airls="" />
    <parkpos id="H4" airls="" excludes="H40" />
    <parkpos id="H40" airls="" excludes="H4" />
    <parkpos id="H5" airls="" excludes="H50" />
    <parkpos id="H50" airls="" excludes="H5" />
    <parkpos id="H55" airls="" excludes="H65" />
    <parkpos id="H6" airls="" excludes="H60" />
    <parkpos id="H60" airls="" excludes="H6" />
    <parkpos id="H65" airls="" excludes="H55" />
    <parkpos id="H7" airls="" excludes="H70" />
    <parkpos id="H70" airls="" excludes="H7" />
    <parkpos id="H8" airls="" excludes="H80" />
    <parkpos id="H80" airls="" excludes="H8" />
    <parkpos id="H87" airls="" />
    <parkpos id="H9" airls="" />

Share this post


Link to post
Share on other sites
53 minutes ago, knich said:

  <parkpos id="H23" airls="" excludes="H1,H20,H21" />

Change H1,H20,H21 into H20,H21

Share this post


Link to post
Share on other sites
2 minutes ago, kiek said:

Change H1,H20,H21 into H20,H21

Great..thanks.  

Just curious...what does the excludes mean?

Share this post


Link to post
Share on other sites

Spoke too soon..Just turned on learner..and this is what I get.  This is major airport and have never gotten these errors before.  Is the file perhaps corrupted?

Not sure how many more there are to correct.

Screenshot-1031.png

Here are the N excludes:

<parkpos id="N10" airls="" excludes="N9" />
    <parkpos id="N11" airls="" />
    <parkpos id="N2" airls="" excludes="N31" />
    <parkpos id="N3" airls="" excludes="N31,N33,N41" />
    <parkpos id="N31" airls="" excludes="N2,N3,N33" />
    <parkpos id="N33" airls="" excludes="N3,N31,N41" />
    <parkpos id="N4" airls="" excludes="N41,N43" />
    <parkpos id="N41" airls="" excludes="N3,N33,N4,N43" />
    <parkpos id="N43" airls="" excludes="N4,N41" />
    <parkpos id="N5" airls="" excludes="N53" />
    <parkpos id="N53" airls="" excludes="N5,N6" />
    <parkpos id="N6" airls="" excludes="N53" />
    <parkpos id="N71" airls="" />
    <parkpos id="N8" airls="" excludes="N9" />
    <parkpos id="N9" airls="" excludes="N10,N8" />

Edited by knich

Share this post


Link to post
Share on other sites

As I feel a little bit responsible for the exclusions 😄, I hope I can solve your questions.

The exclusions are generated from the AFCAD position infos, if there is an overlapping position, PSXT will only place a plane on either one but not on both positions. In real life there are often positions that can be used either by one big or two small aircraft. Some developers include only the big or only the two small stands but some do both. So that PSXT does not spawn up to 3 aircraft on top of each other, PPG generates the exclusions by the given position radius.
I dont have MSFS but on Taxi2Gates P3D V5 CDG scenery its clear to see why you get the error:

2021-6-1_17-9-53-49fdjos.jpg

H23 interferes with H21, H1 and H20 but PSXT only counts a maximum of 2 exclusions because if there are more, its likely that there is an AFCAD error. In your case, I assume you are using the stock MSFS scenery for CDG, there are just too many stand options.

The solution is to just check the AFCAD section of your PSXT / PPG airport file and see if there are any positions with more than 2 exclusions.

Hope I could help!

EDIT: Maybe Nico can downgrade it from an error to a warning?

Edited by DLH7LA

Share this post


Link to post
Share on other sites
4 minutes ago, DLH7LA said:

As I feel a little bit responsible for the exclusions 😄, I hope I can solve your questions.

The exclusions are generated from the AFCAD position infos, if there is an overlapping position, PSXT will only place a plane on either one but not on both positions. In real life there are often positions that can be used either by one big or two small aircraft. Some developers include only the big or only the two small stands but some do both. So that PSXT does not spawn up to 3 aircraft on top of each other, PPG generates the exclusions by the given position radius.
I dont have MSFS but on Taxi2Gates P3D V5 CDG scenery its clear to see why you get the error:

2021-6-1_17-9-53-49fdjos.jpg

H23 interferes with H21, H1 and H20 but PSXT only counts a maximum of 2 exclusions because if there are more, its likely that there is an AFCAD error. In your case, I assume you are using the stock MSFS scenery for CDG, there are just too many stand options.

The solution is to just check the AFCAD section of your PSXT / PPG airport file and see if there are any positions with more than 2 exclusions.

Hope I could help!

 

Great.  Thank you.  So I can just exclude any files with more than 2 exclusions?  It doesn't matter which ones I exclude as long as there are just 2 exclusions?

Share this post


Link to post
Share on other sites
Just now, knich said:

Great.  Thank you.  So I can just exclude any files with more than 2 exclusions?  It doesn't matter which ones I exclude as long as there are just 2 exclusions?

Yep, just delete any exclusions that are more than 2!

  • Like 1

Share this post


Link to post
Share on other sites
7 minutes ago, DLH7LA said:

Yep, just delete any exclusions that are more than 2!

That did it.  Thank you!

Share this post


Link to post
Share on other sites
1 hour ago, DLH7LA said:

 

EDIT: Maybe Nico can downgrade it from an error to a warning?

Even better, I will change PPG such that it does not generate more than 2 exclusions, and gives a warning.

  • Like 2

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...