Jump to content
Sign in to follow this  
GERairborne272

EDDB Aerosoft

Recommended Posts

First of all I would like to thank you for the great work.

I have a problem with EDDB Aerosoft.

With Aerosoft, many gate and ramp numbers are incorrect. For example, Ramp A3A at Aerosoft is referred to as A301 and so on. And it is precisely these that are not filled by PSXT. It's a pity, because these are exactly the positions where the big planes are. I have read the FAQ's and the documentation for PSXT. In the MSFS EDDB stock version at least most of the ramps and gates are correctly labeled. Aerosoft is 10 times better at displaying the scenery. How can I get PSXT to also fill the ramps and gates from the stock version when using Aerosoft? I just deactivated Aerosoft and let the stock version learn. After that I would like to use the Aerosoft Airport again. Does PSXT then also load the learned file of the stock version?

Share this post


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

I just deactivated Aerosoft and let the stock version learn. After that I would like to use the Aerosoft Airport again. Does PSXT then also load the learned file of the stock version?

It will do that only if there is no EDDB.xml in the thirdparty_airports folder. So you should delete that file there, it will be regenerated at the next push of the Airports button. Are you sure the gates in the stock version are about the same as in the Aerosoft version?

 

1 hour ago, GERairborne272 said:

How can I get PSXT to also fill the ramps and gates from the stock version when using Aerosoft? 

By manually changing the Aerosoft EDDB.xml file, copy the missing or to be changed parts from the stock version. 

 

Share this post


Link to post
Share on other sites

This is Aerosoft Ramps 😧

    <parkpos id="D1" latitude="52.366848" longitude="13.499244" heading="248.8" radius="40.0" cargo="false" ramp="true" />
    <parkpos id="D1101" latitude="52.363018" longitude="13.501670" heading="248.8" radius="40.0" cargo="false" ramp="true" />
    <parkpos id="D12" latitude="52.362221" longitude="13.502182" heading="248.8" radius="25.0" cargo="false" ramp="true" />
    <parkpos id="D13" latitude="52.361797" longitude="13.502497" heading="248.8" radius="25.0" cargo="false" ramp="true" />
    <parkpos id="D1501" latitude="52.361187" longitude="13.502855" heading="248.8" radius="40.0" cargo="false" ramp="true" />
    <parkpos id="D1701" latitude="52.360462" longitude="13.503321" heading="248.8" radius="40.0" cargo="false" ramp="true" />
    <parkpos id="D1901" latitude="52.359764" longitude="13.503791" heading="248.8" radius="40.0" cargo="false" ramp="true" />
    <parkpos id="D2101" latitude="52.358944" longitude="13.504292" heading="248.8" radius="40.0" cargo="false" ramp="true" />
    <parkpos id="D22" latitude="52.358273" longitude="13.504725" heading="248.8" radius="40.0" cargo="false" ramp="true" />
    <parkpos id="D301" latitude="52.366192" longitude="13.499721" heading="248.8" radius="40.0" cargo="false" ramp="true" />
    <parkpos id="D501" latitude="52.365231" longitude="13.500314" heading="248.8" radius="40.0" cargo="false" ramp="true" />
    <parkpos id="D701" latitude="52.364491" longitude="13.500756" heading="248.8" radius="40.0" cargo="false" ramp="true" />
    <parkpos id="D901" latitude="52.363754" longitude="13.501228" heading="248.8" radius="40.0" cargo="false" ramp="true" />
  

This is stock Ramps 😧

<parkpos id="D1" latitude="52.366894" longitude="13.499469" heading="250.3" radius="14.0" cargo="false" ramp="true" />
    <parkpos id="D10" latitude="52.363270" longitude="13.501557" heading="248.4" radius="7.0" cargo="false" ramp="true" />
    <parkpos id="D11" latitude="52.362976" longitude="13.501493" heading="249.2" radius="7.0" cargo="false" ramp="true" />
    <parkpos id="D12" latitude="52.362221" longitude="13.502145" heading="248.1" radius="7.0" cargo="false" ramp="true" />
    <parkpos id="D13" latitude="52.361889" longitude="13.502154" heading="246.7" radius="7.0" cargo="false" ramp="true" />
    <parkpos id="D14" latitude="52.361427" longitude="13.502721" heading="248.6" radius="7.0" cargo="false" ramp="true" />
    <parkpos id="D15" latitude="52.361141" longitude="13.502675" heading="246.7" radius="7.0" cargo="false" ramp="true" />
    <parkpos id="D16" latitude="52.360767" longitude="13.503256" heading="250.2" radius="7.0" cargo="false" ramp="true" />
    <parkpos id="D17" latitude="52.360447" longitude="13.503256" heading="248.9" radius="7.0" cargo="false" ramp="true" />
    <parkpos id="D18" latitude="52.359951" longitude="13.503604" heading="248.6" radius="7.0" cargo="false" ramp="true" />
    <parkpos id="D19" latitude="52.359615" longitude="13.503790" heading="249.3" radius="7.0" cargo="false" ramp="true" />
    <parkpos id="D2" latitude="52.366348" longitude="13.499475" heading="250.0" radius="7.0" cargo="false" ramp="true" />
    <parkpos id="D20" latitude="52.359119" longitude="13.504116" heading="249.6" radius="7.0" cargo="false" ramp="true" />
    <parkpos id="D21" latitude="52.358891" longitude="13.504036" heading="248.3" radius="7.0" cargo="false" ramp="true" />
    <parkpos id="D22" latitude="52.358215" longitude="13.504498" heading="249.1" radius="7.0" cargo="false" ramp="true" />
    <parkpos id="D3" latitude="52.366165" longitude="13.499598" heading="250.1" radius="8.0" cargo="false" ramp="true" />
    <parkpos id="D4" latitude="52.365429" longitude="13.499980" heading="249.9" radius="7.0" cargo="false" ramp="true" />
    <parkpos id="D5" latitude="52.365078" longitude="13.500363" heading="250.0" radius="7.0" cargo="false" ramp="true" />
    <parkpos id="D6" latitude="52.364723" longitude="13.500525" heading="250.4" radius="7.0" cargo="false" ramp="true" />
    <parkpos id="D7" latitude="52.364357" longitude="13.500830" heading="249.0" radius="7.0" cargo="false" ramp="true" />
    <parkpos id="D8" latitude="52.363987" longitude="13.501060" heading="249.8" radius="7.0" cargo="false" ramp="true" />
    <parkpos id="D9" latitude="52.363621" longitude="13.501276" heading="250.8" radius="7.0" cargo="false" ramp="true" />

In Aerosoft there are those numbers like :

"D1101" . It should be "D11A"

"D1501".  It should be "D15A"......

Same for the rest. 01 stands for A

But those gates aren´t in the stock EDDB.

In Aerosoft are missing D2 to D11 and D14 to D21

 

Share this post


Link to post
Share on other sites

You should manually change the Aerosoft EDDB.xml airport file such that it suits your needs.

(The stock airport radiusses seem totally wrong to me.)

You should take the lat/lon positions as starting point, and then label according to a map of the real airport..

I'm sorry, but PSXT cannot help you in this.

Share this post


Link to post
Share on other sites

I have seen the radius issue too and fixed it.

I've now manually added the missing gates and ramps for aerosoft and MSFS with the correct coordinates. Can I upload them here somewhere so that others can use them too?

Share this post


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

I have seen the radius issue too and fixed it.

I've now manually added the missing gates and ramps for aerosoft and MSFS with the correct coordinates. Can I upload them here somewhere so that others can use them too?

Good idea, I'll p.m. you my email address. I'll put it on my site, okay?

Share this post


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

Ok. Will send it to you now.

Thanks, it is on my site now.

  • Like 1

Share this post


Link to post
Share on other sites

Now everything is working. The gates are recognized by PSXT.

But now I have a problem with overlapping aircrafts.

For exemple the gates B9, B9A and B10. PSXT places a Scoot 788 in 9A (thats´correct because of the wingspan) at B9A between the static aircrafts before departure time. At departure time the static aircrafts disappear.

Has it something to do with still using the old updated airport file? Should I delete it and start learn again with empty file? 

 

Share this post


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

But now I have a problem with overlapping aircrafts.

For exemple the gates B9, B9A and B10. PSXT places a Scoot 788 in 9A (thats´correct because of the wingspan) at B9A between the static aircrafts before departure time. At departure time the static aircrafts disappear.

Then exclude info might be missing, probably because you mixed two files.

If gates overlap you must add excludes info in the afcad section. Since it is still empty in EDDB.xml, you should add:

<afcad>
    <parkpos id="B9" airls="" excludes="B9A,B10" />
    <parkpos id="B9A" airls="" excludes="B9,B10" />
    <parkpos id="B10" airls="" excludes="B9,B9A" />
</afcad>

 

Edited by kiek

Share this post


Link to post
Share on other sites

There aren´t two different files.

But this with afcad is the anwser I needed. I will do it now for all those gates an email you the updated EDDB file.

Thank you

Share this post


Link to post
Share on other sites

Sorry...but I have two more questions.

I already started editing the afcad. I went in an issue. I just can ecxclude 2 parkpositions per parkposition in one line. If I enter a third PSXT crashes.

So i entered an extra line for the third exclusion:

<parkpos id="B7" airls="" excludes="B7A,B7B" />
    <parkpos id="B7A" airls="" excludes="B7,B7B" />
    <parkpos id="B7A" airls="" excludes="B8" />
    <parkpos id="B8" airls="" excludes="B7A,B7B" />
    <parkpos id="B7B" airls="" excludes="B7,B7A" />
    <parkpos id="B7B" airls="" excludes="B8" />

Second I wan´t to reserve few gates for specific aircraft types.

Can I do it with afcad like this? Is it just type or types?:

<parkpos id="B15B" types="A388,B748" airls="" excludes="B15,B15A" />

Share this post


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

I already started editing the afcad. I went in an issue. I just can ecxclude 2 parkpositions per parkposition in one line. If I enter a third PSXT crashes.

Normally you only have two neighbours (!) at an airport, so two exclude gates should be sufiicient. Will have a look in my code why it crashes, it probably does not expect a third one.

1 hour ago, GERairborne272 said:

So i entered an extra line for the third exclusion:

That will not work, it will overrule the previous line.

1 hour ago, GERairborne272 said:

Second I wan´t to reserve few gates for specific aircraft types.

Can I do it with afcad like this?

No, you cannot do that in the afcad. You cannot do that at all.

EDIT: you can of course define the type in a parking position for a static aircraft, but that does not prevent that live aircraft that fit park at the gate.

 

EDIT: I have fixed the bug, PSXT will no more crash when you define more then 2 excludes, re-uploaded v31.17.7

Edited by kiek
  • Like 1

Share this post


Link to post
Share on other sites

I tried it with 3 excludes with the new version. PSXT still crashes. So I left it with 2.

I finished all the afcad entries now. But still having overlapping aircrafts at the excluded gates. I don´t understand why. I don´t have duplicated EDDB files in my installation. Just one in thirdparty and one in updated folder.

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

 

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...