Jetway/Excluding Library Objects - FSX

[NovemberIndiaCharlieOscar]

I have added two jetways at a local airport in FSX. No problem, they work/animate just fine.

My problem is the exclude file! As soon as I use excludeLibraryObjects = "TRUE" in my Exclusion Rectangle, then all the library objects, the default MS objects as well as the library objects I have added through my AFCAD file gets axed! This includes the jetways I have added afterwards!

I want to use the excludeLibraryObjects = "TRUE" in order to get rid of the default MS library objects, but not the objects that I have add afterwards!

This only affects library objects such as jetways that I add through my AFCAD file with the LibraryObject command. All other library objects that I add through normal coding is still there. Normally I would just go and add the objects again, but you cannot do this for jetways without loosing the animation...

I have tried to copy the exclude file into various other directories in FSX in the hope that placing the file at various scenery levels would somehow work, but no joy unfortunately.

I am now hoping that somoen out there can give me a bit of help short of adding the jetways as static objects.

Regards,

 

[scruffyduck]

The exclude either needs to be in the XML above the new entries you are making (if it is in the same physical file - which is preferable). Alternatively if the exclude is in a separate Bgl file then it can go in the same folder as the one containing your new objects provided that it is read first by FS. FS seems to read in alphabetical order so make sure your Exclude Bgl is names alphabetically before the others in the folder.

 

[jvile]

Adding to what scruffyduck says there is a problem and it has been reported to MS.

A default FSX Jetway will not showup if its reference point (center of the pivot point) nest inside any type XML exclude.

You need to make additional excludes around the Jetway Reference point so they are not nesting inside your exclude.

This only occurs with Jetway mdl's and not other type model mdl's.

Maybe SP1 fixed this problem.

 

[José]

Unbelievable!

Hi, Jim

A default FSX Jetway will not showup if its reference point (center of the pivot point) nest inside any type XML exclude.

Is it really possible to happen, even following the rules Jon pointed out?

Regards,

José

 

[jvile]

The exclude either needs to be in the XML above the new entries you are making (if it is in the same physical file - which is preferable).

Jose

That rule is the prefered which I have used since FS9 came out. If you go back and download some of my earlist scenery and approach codes for KMIA, KDEN, etc. dated 06/2004 you will see that I have always placed my excludes into my scenery/approach XML. This does several things.

One it reads the excludes first when nesting above the Airport header, allows FS to sort the excludes and prioritize without a naming scheme, keeps everything in one file and allows many excludes rather then one exclude per bgl or multiple excludes per bgl.

Some of my XML AFCAD/approach records have as many as 50 excludes. It is much better to pick and choose what to exclude right down to a single tree (FS9) then have one big exclude that leaves the entire scenery bare.

When FSX was released I noticed I could not place FSX Jetways at KATL if the pivot point which is the reference was nesting in a exclude. I had the same problem with my KJAX and most recently with KSAV.

I reported this to MS and they concured it was a problem that is not suppose to happen which in some ways also relates to the Taxiway sign issue of excludes.

To further my studies of excludes, they are not airport or region specific. You can actually make a master exclude bgl and add excludes from around the world and FS9/FSX honors that.

But, then there are opposites to these rules such as runways. A runway must nest inside the airport header but can be placed halfway around the world and the airport does not care. This is the technique I use when introdcing the crosswind runway activation in FS9/FSX back in 2004.

My FSX KJAX uses both runway 13/31 and 07/25 at the same time but I placed the 7.9 degree fake runways in the pacific Ocean north of Australia. KJAX still sees these extra runway as there's but ATC cannot find them.

You can use many different elusions in FS9/FSX but FSX animated Jetways cannot nest inside a user exclude regardless of where the exclude nest. Keep in mind we are only talking about the Jetway and nothing else. All other type scenery model mdl's (GUID's) will show properly when nested inside a exclude both nested in the XML file and when using a dedicated exclude bgl (use the naming rule properly).

hope this helps

 

[José]

Very good explanation

Hi, Jim

Thanks for the long, clear and interesting explanation.

It sounds as if FSX behaves somehow erratically, giving responses not expected and not logically well explained even by whom should understand.

Jose
That rule is the prefered which I have used since FS9 came out. If you go My FSX KJAX uses both runway 13/31 and 07/25 at the same time but I placed the 7.9 degree fake runways in the pacific Ocean north of Australia. KJAX still sees these extra runway as there's but ATC cannot find them.
hope this helps

I modified two airports in a certain region (adjusting altitude to mesh and moving the runway to the right position. To test my work, I created an aircraft traffic between them. As the example above, in one airport, the runway is there, but ATC do not recognize the traffic.

Thanks,

José

BTW, I posted one problem I have creating mesh files. Could you take a look at that (FSX Mesh).

 

[NovemberIndiaCharlieOscar]

Thank you very much to all the replies.

I have tried all the suggestions except for building multiple exclude files. Nothing of what I have tried so far, worked. That includes changeing the filename to 1.BGL so that it is read as the very first file and including the Exclusion Rectangle as part of my AFCAD file... As soon as I make excludeLibraryObjects = "TRUE", then there goes my jetways!

Hopefully MS will fix this bug with SP1. Until then, I will just have to live with the 50ft tower next to the runway!

Regards,

 

[DougMatthews]

Thank you very much to all the replies.

I have tried all the suggestions except for building multiple exclude files. Nothing of what I have tried so far, worked. That includes changeing the filename to 1.BGL so that it is read as the very first file and including the Exclusion Rectangle as part of my AFCAD file... As soon as I make excludeLibraryObjects = "TRUE", then there goes my jetways!

Hopefully MS will fix this bug with SP1. Until then, I will just have to live with the 50ft tower next to the runway!

Regards,

Control towers are a special. Try using the DeleteAirport mechanism with deleteAllControlTowers = "TRUE".

-Doug

 

[glottis]

Hi
I was wondering if you could try this delete statement:

deleteAllJetways="TRUE"

may be worth a try

Ray

 

[Mace]

Thank you very much to all the replies.

I have tried all the suggestions except for building multiple exclude files. Nothing of what I have tried so far, worked. That includes changeing the filename to 1.BGL so that it is read as the very first file and including the Exclusion Rectangle as part of my AFCAD file... As soon as I make excludeLibraryObjects = "TRUE", then there goes my jetways!

Hopefully MS will fix this bug with SP1. Until then, I will just have to live with the 50ft tower next to the runway!

Regards,

I think you can get it working, if you put your ExclusionRectangle at the very top of your xml file.

Then go on to define the various other elements such as Jetways.

The only caveat is, that if your jetway lat/long is inside the exclude...it might not show as was said. But from what you have said, I cannot verify that this is the situation you have encountered. *Is* your jetway lat/long inside the ExclusionRectangle bounds?

If so then wait for SDK SP1a. -- cleaning up exclude behavior was mentioned as something that attn was paid to.

If not, then it _should_ work provided that your ExclusionRectangle was at the very top of your xml, above all other scenery elements.

 

[DougMatthews]

If so then wait for SDK SP1a. -- cleaning up exclude behavior was mentioned as something that attn was paid to.

If not, then it _should_ work provided that your ExclusionRectangle was at the very top of your xml, above all other scenery elements.

All of the FSX SP1 exclusion work was in-game. I did a good part of it. I am not sure if this specific issue was addressed.

-Doug

 

[NovemberIndiaCharlieOscar]

Adding to what scruffyduck says there is a problem and it has been reported to MS.

A default FSX Jetway will not showup if its reference point (center of the pivot point) nest inside any type XML exclude.

You need to make additional excludes around the Jetway Reference point so they are not nesting inside your exclude.

This only occurs with Jetway mdl's and not other type model mdl's.

Maybe SP1 fixed this problem.

I was so hoping that SP1 will fix it, but alas... Anyone know when SP2 will come out?

 

[jvile]

SP1 did get the taxiway sign exclusion working so you no longer have to reference the first sign.

Thats a start but as you say the jetways in an exclusion box probably was not fixed.

Many of my reports sent to fsinsider which needed fixes appear to have been overlook.

 

[sparker256]

I was working on the same problem at KERI. I was trying to exclude the terminal building as it is in the wrong place and there are no jetways but in reality there are three jetways. Got the jetways to display but when I excluded the terminal I lost one jetway and the tower.

My answer is small excludes. Find out where FSX is putting the object to exclude and make the exclude about 1 or 2 meters around the center point. The exclude file I named 0_exclude_KERI.BGL and put it in my "Microsoft Games\Microsoft Flight Simulator X\Addon Scenery\Keri\Scenery" directory with the airport bgl.

I sure hope this makes some sense to someone other than me

 

[scruffyduck]

I was working on the same problem at KERI. I was trying to exclude the terminal building as it is in the wrong place and there are no jetways but in reality there are three jetways. Got the jetways to display but when I excluded the terminal I lost one jetway and the tower.

My answer is small excludes. Find out where FSX is putting the object to exclude and make the exclude about 1 or 2 meters around the center point. The exclude file I named 0_exclude_KERI.BGL and put it in my "Microsoft Games\Microsoft Flight Simulator X\Addon Scenery\Keri\Scenery" directory with the airport bgl.

I sure hope this makes some sense to someone other than me

Yes you just need to exclude the reference point of the object - generally in the middle but not always so you may need to experiment

 

[Mace]

My answer is small excludes. Find out where FSX is putting the object to exclude and make the exclude about 1 or 2 meters around the center point. The exclude file I named 0_exclude_KERI.BGL and put it in my "Microsoft Games\Microsoft Flight Simulator X\Addon Scenery\Keri\Scenery" directory with the airport bgl.

You know, for cleanliness you can put those types of excludes in the same .bgl file as your airport scenery.

It would be one less .bgl file to keep track of, and one less .bgl file that FSX needs to parse at run-time.

 

[scruffyduck]

Making sure that they are the first things in the Xml File and before the Airport Record

 

[José]

Working with FSX Planner

Hi, people

Making sure that they are the first things in the Xml File and before the Airport Record

Presently, FSX Planner save XML code in a different order, and the exclusion section could be moved and stop working.

So, one must be careful using Planner when editing airport code that has exclusion inside.

Russell knows that problem and is trying to fix.

Regards,

José