AES issue at Berlin Brandenburg (EDDB)

[SVM79 0]

Hi all,

 

I'm having some troubles with AES at EDDB. It works fine at other airports I've enabled it, but at the new Berlin it has issues. I've also asked the good people at Aerosoft, but so far they couldn't find an answer. Because I've been waiting for some time now, I hope that over here someone might have any clues.. Or does anyone has it working just fine?

 

More details and pictures can be found following the link provided, but to sum it up a bit:

- jetways ar too high at BER part of the EDDB scenery

- jetways are correct at SXF part of the EDDB scenery (and at any other airport)

- no runway rumbling sounds

- no runway winter textures

 

I've (re)run everything as an Administrator, no luck. I've tried different settings in the Airport Manager (e.g. textures, BER active/inactive), makes no difference.

BTW: adjusting parameters in AESconfig, lowering the door position, obviously helps at EDDB-BER, but puts the jetway far too low everywhere else. So that's not really an option.

 

The post at the Aerosoft forum can be found here

I'm very curious to your thoughts about the matter, thanks in advance!

 

Gr.,

 

Sebastiaan

[CoolP 283]

Can you rule out that another file for EDDB is active in your scenery setup? You could use a freeware airport scanner to check, just in case. It seems like some 'alt' file is active somewhere, maybe confusing AES and defining a wrong airport altitude, being slightly off.

 

Wouldn't be the only thing being off at that (rw) airport.

[SVM79 0]

I'm not very familiar with this, so I don't know exactly how to read it..

I've used the program and see nothing listed there. Only when I uncheck both 'Do not show pre-load files' and 'show only airports found in multiple files' I get one line:

Layer: 0001, Active: yes, Filename: ...\scenery\world\scenery\AF2_EDDB_ALT_BERopen.bgl

 

Is this something wrong? Because it's apparently not found in multiple files.

 

When I look in the folder ...\aerosoft\Mega Airport Berlin Brandenburg\Scenery I find AF2_EDDB_BEROpen.bgl and AF2_EDDB2_BEROpen.bgl.

 

Does this give you an answer?

 

I hope it doesn't have it's rw-counterparts luck indeed! ;-)

[CoolP 283]

Good work on the scan. Now I don't have the airport so I can not check with my installation. But, from the syntax used, it seems like all files belong to the same set, namely the one the Aerosoft installer created. Their file dates should be close together too.

 

Still, the only way I could imagine the AES error you've described to come alive would be that some file defines a wrong altitude. Since you've scanned for the EDDB ICAO code only, maybe there's another "airport" or definition for that location active, not being bound to that EDDB tag.

 

If you run the airport with all files (except the default FSX ones) disabled, does AES still mix things up? Also, when you open the default map while being at EDDB, does it show other, very close, airports which could form up a problem?

 

If you run things like Orbx Vector, you could also check if some correction file is in use. It may not show up under the EDDB ICAO, which adds to the confusion. The thing being that EDDB, so far, is fictional.

[SVM79 0]

Thanks for your explanation and thoughts so far already!

When I open the default map while at EDDB, it shows Tempelhof (EDDI) and Tegel (EDDT) rather close. EDDI is closed by Aerosoft, because it shared a frequency or something with the new EDDB (and in real life is also closed). But I dont know if this could form up a problem? They intended it like this I think.

 

How do I run the airport with all files except the default FSX ones disabled? I sure want to try :-)

 

I don't have Orbx Vector (yet) so nothing messing around there probably.

 

To make things more confusing: today I tried bagage loaders and stairs from AES (normally I use GSX there). AES bagage loaders and stairs do align proper and the same as at other airports. Also, when I spawn at a parkingspot without jetway at EDDB, AES rolls in the stairs to the front left door which also aligns proper.

I'll also point this out at the Aerosoft forum. Maybe it is something with the jetways. But then the runway issues are also stil there..

 

It's not an easy airport for sure ;-)

[CoolP 283]

 

 

How do I run the airport with all files except the default FSX ones disabled? I sure want to try :-)

Just disable all other scenery in the scenery library. You can use the FSX menu (many clicks) or free tools like scenery config editor.

[SVM79 0]

I ran the airport with only EDDB and AES Basepack enabled (and default scenery). Makes no difference..

 

I used the multi click method btw (my index finger is now in recovery indeed :smile:). Something tells me I'll like this scenery config tool you mentioned, but it only shows me the default scenery. In preferences I set it to the fsx root folder (where is scenery.cfg). Should I use 'Generate from directory' as I can find in the manual? And do I need to re-do this after installing new scenery? Sounds logical, but just checking :smile:

[CoolP 283]

In preferences I set it to the fsx root folder (where is scenery.cfg).

The active scenery.cfg is at C:\ProgramData\Microsoft\FSX. Tricky FSX installation, I know.

 

When you install new scenery, you can add it manually and you should always keep a backup of the current cfg file. I think the editor even automates the backup.

 

The reason behind this is that some tools delete the group entries you might have set up and also re-order the whole scenery because they think they are important.

 

When you go manual, you just need to know the folder where the new scenery resides (FSX\Addon Scenery\AndSoOn) as opposed to trusting some installer to do it right.

[SVM79 0]

Aah, it's working (the scenery tool that is) and very useful, thanks! It's initial 'Default flight simulator scenery file not found' tricked me into changing things.. 

 

No luck yet on the EDDB scenery however, but at least I'm learning things :smile:

 

To come back to your first reply: now we ruled this out, anything else it might be?

[SVM79 0]

Gentle bump..

In the meantime version 2.37 was released. Installing it also doens't solve anything. Any ideas?

 

Gr.,

 

Sebastiaan