Jump to content
Sign in to follow this  
GERairborne272

EDDB Aerosoft

Recommended Posts

16 hours ago, GERairborne272 said:

I will send you the new file. Maybe you can check the afcad section again.

I have let PSXT generated the excludes, it is based on the radiusses. If  the distance < 1.05 * radius,  it concludes a clash.

Spoiler

<parkpos id="B1" airls="" excludes="B1A" />
<parkpos id="B10" airls="" excludes="B9A" />
<parkpos id="B11" airls="" excludes="B11A" />
<parkpos id="B11A" airls="" excludes="B11,B12" />
<parkpos id="B12" airls="" excludes="B11A" />
<parkpos id="B13" airls="" excludes="B13A" />
<parkpos id="B13A" airls="" excludes="B13,B14" />
<parkpos id="B14" airls="" excludes="B13A" />
<parkpos id="B15" airls="" excludes="B15A,B15B" />
<parkpos id="B15A" airls="" excludes="B15,B15B,B16" />
<parkpos id="B15B" airls="" excludes="B15,B15A,B16" />
<parkpos id="B16" airls="" excludes="B15A,B15B" />
<parkpos id="B1A" airls="" excludes="B1,B2" />
<parkpos id="B2" airls="" excludes="B1A" />
<parkpos id="B3" airls="" excludes="B3A" />
<parkpos id="B3A" airls="" excludes="B3,B4" />
<parkpos id="B4" airls="" excludes="B3A" />
<parkpos id="B5" airls="" excludes="B5A" />
<parkpos id="B5A" airls="" excludes="B5,B6" />
<parkpos id="B6" airls="" excludes="B5A" />
<parkpos id="B7" airls="" excludes="B7B" />
<parkpos id="B7A" airls="" excludes="B7B" />
<parkpos id="B7B" airls="" excludes="B7,B7A" />
<parkpos id="B9" airls="" excludes="B9A" />
<parkpos id="B9A" airls="" excludes="B10,B9" />
<parkpos id="C10" airls="" excludes="C11A" />
<parkpos id="C11" airls="" excludes="C11A" />
<parkpos id="C11A" airls="" excludes="C10,C11" />
<parkpos id="C13" airls="" excludes="C14" />
<parkpos id="C14" airls="" excludes="C13" />
<parkpos id="C5" airls="" excludes="C5A" />
<parkpos id="C5A" airls="" excludes="C5" />
<parkpos id="C6" airls="" excludes="C7A" />
<parkpos id="C7" airls="" excludes="C7A" />
<parkpos id="C7A" airls="" excludes="C6,C7" />
<parkpos id="C8" airls="" excludes="C9A" />
<parkpos id="C9" airls="" excludes="C9A" />
<parkpos id="C9A" airls="" excludes="C8,C9" />
<parkpos id="D10" airls="" excludes="D11A" />
<parkpos id="D11" airls="" excludes="D11A" />
<parkpos id="D11A" airls="" excludes="D10,D11" />
<parkpos id="D14" airls="" excludes="D15A" />
<parkpos id="D15" airls="" excludes="D15A" />
<parkpos id="D15A" airls="" excludes="D14,D15" />
<parkpos id="D16" airls="" excludes="D17A" />
<parkpos id="D17" airls="" excludes="D17A" />
<parkpos id="D17A" airls="" excludes="D16,D17" />
<parkpos id="D18" airls="" excludes="D19A" />
<parkpos id="D19" airls="" excludes="D19A" />
<parkpos id="D19A" airls="" excludes="D18,D19" />
<parkpos id="D2" airls="" excludes="D3,D3A" />
<parkpos id="D20" airls="" excludes="D21,D21A" />
<parkpos id="D21" airls="" excludes="D20,D21A" />
<parkpos id="D21A" airls="" excludes="D20,D21" />
<parkpos id="D3" airls="" excludes="D2,D3A" />
<parkpos id="D3A" airls="" excludes="D2,D3" />
<parkpos id="D4" airls="" excludes="D5A" />
<parkpos id="D5" airls="" excludes="D5A" />
<parkpos id="D5A" airls="" excludes="D4,D5" />
<parkpos id="D6" airls="" excludes="D7A" />
<parkpos id="D7" airls="" excludes="D7A" />
<parkpos id="D7A" airls="" excludes="D6,D7" />
<parkpos id="D8" airls="" excludes="D9A" />
<parkpos id="D9" airls="" excludes="D9A" />
<parkpos id="D9A" airls="" excludes="D8,D9" />

It is a bit differtent from yours. There are indeed also gates with 3 excludes... will see if I can update PSXT to be prepared for that.

I have updated your file, you can download it from my site.

 

 

Edited by kiek

Share this post


Link to post
Share on other sites
51 minutes ago, GERairborne272 said:

Thank you

Thanks to you I found a nasty bug that has been there for a long time already. Exclude info for parking positions that have no afcad airlines was forgotton. That's why you saw still aircraft parked on top of each other.

Now fixed in v31.17.8  (supports 3 excludes too)

Give it a try.

Edited by kiek

Share this post


Link to post
Share on other sites

Now it´s working perfectly. I just edited the afcad again. Because in yours there were few missing. This is the final version. I will send it to you now.

Share this post


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

Now it´s working perfectly. I just edited the afcad again. Because in yours there were few missing. This is the final version. I will send it to you now.

Well there is no need to. I've decided not to store exclude info in airport files anymore. At the moment the airport file is read I let PSXT calculated the excludes dynamically. This has the advantage that if a radius chnages (due to auto correct) possible excludes will be found, while with exclude info in the airport file generated from scratch it is static and will never change.

What did I miss? According to the radiusses there are no more excludes...

I can only have mist new parking positions, but with my new approach the excludes will be found automatically if you add them to the airport file.

Share this post


Link to post
Share on other sites

Maybe my English isn´t that good what I thought it would be or I have an error in thinking at the moment.. Is it right, that with the new version there is no manual input of afcad needed anymore for exclusions?

I tested it with no afcad and I have overlapping aircrafts. Should I empty the parkpositions in my updated file and learn from scratch those parkpositions?

Share this post


Link to post
Share on other sites
22 minutes ago, GERairborne272 said:

 Is it right, that with the new version there is no manual input of afcad needed anymore for exclusions?

I tested it with no afcad and I have overlapping aircrafts. Should I empty the parkpositions in my updated file and learn from scratch those parkpositions?

No, in 31.17.8 the excludes attribute is still generated when an airport file is created from a .bgl file. Your EDDB.xml I have updates with the afcad as if it was generated from scratch. So you can just use it, no need to change something. You better not edit an airport file yourself.

In 31.17.9 (to be released in 5 minutes)  the excludes attributes will no longer be generated, because PSXT will calculate the excludes each time it reads the airport file. 

Edited by kiek
  • Like 1

Share this post


Link to post
Share on other sites

Hallo Marco,

Thanks for your generous donation, I'll  take an extra "Pilz" tonight 😉

Nico

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
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...