FS2004 ADE9 Extended Compile Plugin

[scruffyduck]

Extended Compile is a plugin for Airport Design Editor FS9 version (ADE9). It does not work with the FSX version. The purpose of this plugin is to extend the options available for compiling FS9 airports. Users have requested that we provide a way to generate a Bgl file that is compatible with AFCAD. We have also identified a problem with the Microsoft FS9 compiler which will fail at certain airports with large numbers of, or complex aprons. This problem is caused by a limited amount of space (buffer) available to the compiler. AFCAD/AFX compilers do not show this limitation. This plugin may help to split the airport in such a way to overcome this problem.

You can get it directly from http://www.scruffyduck.org.uk/files/ade9_extended_compile.zip

 

[tgibson]

Hi,

Thanks, I'll try it out.

So I guess it's not possible for there to be a three file split?

1. AFCAD Compatible Airport
2. Library Object placement (i.e. compatible with Instant Scenery)
3. All the rest (appears to be MDL inclusions, Approaches and Taxi Signs).

That would be the most useful.

Thanks,

 

[scruffyduck]

Hi,

Thanks, I'll try it out.

So I guess it's not possible for there to be a three file split?

1. AFCAD Compatible Airport
2. Library Object placement (i.e. compatible with Instant Scenery)
3. All the rest (appears to be MDL inclusions, Approaches and Taxi Signs).

That would be the most useful.

Thanks,

Yes it would be Tom. Although does IS handle exclusions?

EDIT

Let me be clear you want

• AFCAD Compatible Airport File
• A file containing only object placement code (no exclusions?)
• The rest

I have some concerns about where the exclusions go - in this split it seems that perhaps they should be separated into their own file which gets called first.

 

[tgibson]

Hi,

A separate file for exclusions is OK if it really needs to be separate from the Approaches, etc. Then the 4 files would be:

1. AFCAD Compatible Airport
2. IS Compatible Library Object Placements
3. Exclusions
4. Everything else

Thanks,

 

[scruffyduck]

Hi,

A separate file for exclusions is OK if it really needs to be separate from the Approaches, etc. Then the 4 files would be:

1. AFCAD Compatible Airport
2. IS Compatible Library Object Placements
3. Exclusions
4. Everything else

Thanks,

My problem might be with #2 - perhaps you can email me a file or two created by IS?

 

[tgibson]

Sure. It's the same format (and they are compatible with) Rwy12 and EZ-Scenery placement files too. They are attached to this message.

Thanks,

 

[scruffyduck]

Thanks Tom

I will check them out

 

[tgibson]

Hi,

Tested the current version and it seems to work fine, thanks. Airport is editable by AFCAD, and the taxi signs and approaches are preserved after AFCAD edits. I assume it wouldn't hurt anything to rename the airport BGL to AF2_code.bgl so people recognize it as an AFCAD-compatible file?

I had a scare when my taxi signs didn't show up upon initial load of my old .ADE file, but after I saved the file as an ad2 file and loaded it, then they showed up in *all* the files, no matter the format! I also couldn't reproduce this when I restarted ADE.

Thanks,

 

[scruffyduck]

Hi,

Tested the current version and it seems to work fine, thanks. Airport is editable by AFCAD, and the taxi signs and approaches are preserved after AFCAD edits. I assume it wouldn't hurt anything to rename the airport BGL to AF2_code.bgl so people recognize it as an AFCAD-compatible file?

I had a scare when my taxi signs didn't show up upon initial load of my old .ADE file, but after I saved the file as an ad2 file and loaded it, then they showed up in *all* the files, no matter the format! I also couldn't reproduce this when I restarted ADE.

Thanks,

By all means rename it!

 

[jvile]

I don't use IS but checking everything else as per what Tom is also checking..