Quick Terminal Buildings

[archtx]

I used this code to locate the Guatamala (La Aurora) FS9 default terminal building to another airport. Listed below are some others from Central and South America. This is an easy way to add a terminal or FBO to an airport that doesn't have one.

<?xml version="1.0"?>
<FSData
version="9.0"
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
xsi:noNamespaceSchemaLocation="bglcomp.xsd" >
<SceneryObject
lat="N21 35.09"
lon="W083 08.91"
alt="0.0000M"
altitudeIsAgl="TRUE"
pitch="0.00"
bank="0.00"
heading="105.00"
imageComplexity="VERY_SPARSE">
<LibraryObject
name="8476fbfaa4424affb6de75c7f921c7dc"
scale="1.00"/>
</SceneryObject>
</FSData>
*****************************************************************************
OB9SAME0_45
Guatamala City Guatamala (MGGT)
Main Terminal (large)
name="8476fbfaa4424affb6de75c7f921c7dc"
lat="N14 35.23643"
lon="W090 31.87248"

OB9SAME0_46
Tegucigalpa Honduras (MHTG)
Simple 3 story (Medium)
name="46726ffcc5a644be9024829d43705e6c"
lat="N14 3.75501"
lon="W087 13.18264"

MODEL OB9SAME0_03
Ilopango El Salvador (MSSS)
2 story medium size w/ offset
name="d9af4a0a598d42c4a9a6be832c1c300c"
lat="N13 41.78490"
lon="W089 6.98128"

OB9SAME0_47
El Salvador Intl. (MSLP)
medium large multi story
name="ce465afe77fb4927b38cba0106ed4f53"
lat="N13 26.67102"
lon="W089 3.38348"

OB9SAME0_28
Managua Nicaragua (MNMG)
small ell shape 2 story
name="2610eba1eb5c475e87ba2a11b1314795"
lat="N12 8.73222"
lon="W086 10.40892"

MODEL OB9SAME0_01
Managua Nicaragua (MNMG)
Long 2 story rectangle w/ addition in front
name="5a940106c10b4185b142d1665a23ff71"
lat="N12 8.72147"
lon="W086 10.81130"

OB9SAME0_43
Managua Nicaragua (MNMG)
same as 28
name="0d2bb3f50bbc465ab1d52be5268e8f26"
lat="N12 8.70961"
lon="W086 10.72110"


OB9SAME0_40
Caracas Venezuela (SVVA)
long rectangular 2 story
name="e42a48e54567485cb4b5251cc97f0b6f"
lat="N10 9.32860"
lon="W067 55.64007"

OB9SAME0_39
Caracas Venezuela (SVVA)
same as 40
name="ab1488d1378b4b1c8c99d16a48efb6dc"
lat="N10 9.32860"
lon="W067 55.64007"

OB9SAME0_17
Toucumen Panama
3 story teep
name="b04f216d7a6b44edbdc04945be17145e"
lat="N09 5.22613"
lon="W079 22.46550"

OB9SAME0_30
Toucumen Panama (MPTO)
large with jetways
name="1db1d8a2de944589832fc9cab54eda7e"
lat="N09 4.13700"
lon="W079 23.11212"

OB9SAME0_19 (MPTO)
Toucumen Panama
large multi story with wings
name="2ca92973778449ef9f5faf2795627516"
lat="N09 4.02358"
lon="W079 23.18481"

OB9SAME0_08
Macapa Brazil (SBMQ)
interesting zigzag 2 story medium

name="11601e35da39480f88155791babd16d1"
lat="N00 3.04060"
lon="W051 4.10242"

**********************EQUATOR***************************

**********************
OB9SAME0_18
Quito Ecuador (SEQU)
nice medium large multi story
name="d1a43e6d76cb40acaf61ac1ff49d13b4"
lat="S00 8.74978"
lon="W078 29.39853"

OB9SAME0_37
Sao Luis (SBSL)
small 2 story FBO
name="9afab4c5b0944eaab36c98ccb4bc13f7"
lat="S02 34.99397"
lon="W044 14.09692"

OB9SAME0_25
Petrolina Brazil (SBPL)
medium with ells, nice
name="4fb8e58d74a74a018730e4c72eea6e09"
lat="S09 21.88748"
lon="W040 34.16852"

OB9SAME0_10
Salvador Brazil (SBSV)
medium 2 story
name="8dea9d3c5d3844f58746e4e37b764ed0"
lat="S12 54.77288"
lon="W038 20.05761"

MODEL OB9SAME0_02
Cuiaba Brazil (SBCY)
Interesting offset smaller terminal
name="c71ced083ea144bda7d44a6e5e6a7758"
lat="S15 39.28963"
lon="W056 7.11058"

OB9SAME0_06
Corumba Brazil (SBCR)
Smaller multi-level
name="9d68aa26b37b4ceeac14bea08e53b67d"
lat="S19 0.76963"
lon="W057 39.86405"

OB9SAME0_21
Belo Horizante Brazil (SBCF)
2 story boomerang
lat="S19 37.92238"
lon="W043 57.84388"
name="0278a07a0ee7441aad6195c19dc53027"

OB9SAME0_35
Uberaba Brazil (SBUR)
small FBO type
name="b0562fbe12b14293b575eb4274da3226"
lat="S19 45.96498"
lon="W047 57.71072"

OB9SAME0_29
Rio de Janiero (SBGL)
Same as 20
name="f32b80a22e2e44d78332d6d89057b996"
lat="S22 48.91422"
lon="W043 14.78121"

OB9SAME0_20
Rio de Janiero Brazil (SBGL)
large 3 story odd shape very nice

name="29d152731d6247bf8ae8657b7cc7873f"
lat="S22 48.65275"
lon="W043 15.17147"

OB9SAME0_42
Rio de Janiero (SBRJ)
Large 2 story with wings
name="2ed90bf5cb984f78a2874ed80dbc25a3"
lat="S22 54.68126"
lon="W043 10.03378"

OB9SAME0_38
Viracopos Brazil (SBKP)
Large Terminal
name="f38064d01c5e4fe6af14307442221a17"
lat="S23 0.54335"
lon="W047 8.50938"

OB9SAME0_44
Viracopos Brazil (SBKP)
same
name="e8ed57f76e764d42973b8381b02d0abe"
lat="S23 0.61571"
lon="W047 8.51303"

OB9SAME0_12
Sao Paulo Brazil
large 2 story-multiple wings

name="d37e2d4cbe62460e85181d9233e1ed1c"
lat="S23 25.58186"
lon="W046 28.92330"

OB9SAME0_16
Sao Paulo Brazil (SBSP)
large 2 story boomerang
name="6714b06bbc004f8abd6a7c5066a6d608"
lat="S23 37.48511"
lon="W046 39.68481"

OB9SAME0_34
Bacacheri Brazil (SBBI)
name="13581db36e1c4f378b2935f4c092f5ae"
lat="S25 23.98719"
lon="W049 14.10615"

OB9SAME0_15
Curitiba Brazil (SBBI)
small 2 story Tee
name="d0551a6af0c94c1db88ea4b5d78bbf9b"
lat="S25 24.10670"
lon="W049 13.82353"

OB9SAME0_32
Curitiba Brazil (SBBI)
medium 2 story
name="623e88af24a548dfad22788fc711165c"
lat="S25 24.18159"
lon="W049 13.82291"

OB9SAME0_31
Navengantes Brazil (SBNF)
medium 2 story
name="216effa2a79046e091ab8288aee05472"
lat="S26 52.90515"
lon="W048 39.02900"

OB9SAME0_07
Porto Alegre Brazil (SBPA)
medium size
name="002fc7314a394fe2abef195f773eece3"
lat="S29 59.45129"
lon="W051 10.92266"

OB9SAME0_41
Porto Alegre Brazil (SBPA)
medium tee
name="3d67a8e5a54241bb844a0c4709f50ee6"
lat="S29 59.50696"
lon="W051 10.46684"

OB9SAME0_23
Porto Alegre Brazil (SBPA)
small multi story ell
name="d06ddd7c07be47b5bed216ca27187604"
lat="S29 59.85286"
lon="W051 11.07927"

MODEL OB9SAME0_00
Porto Alegre Brazil (SBPA)
Simple 2 story rectangle
name="d38ca800144b4c0e9d92f0ce4f984798"
lat="S29 59.99832"
lon="W051 11.06098"

OB9SAME0_24
Santiago Chile (SCEL)
larger 3 story
name="955b597da1c241ad9ce84d997e21ae67"
lat="S33 23.77698"
lon="W070 47.80447"

OB9SAME0_36
Santiago Chile (SCEL)
larger multi level
name="71e105bffb434f44b0e8ecc1d2d60265"
lat="S33 23.41925"
lon="W070 47.50752"

OB9SAME0_11
Santiago Chile (SCEL)
name="280ba24220cd43b1835e0c9a4a052a71"
lat="S33 24.17543"
lon="W070 47.56674"


MODEL OB9SAME0_05
Buenos Aires Argentina (SABE)
multi level rectangle
lat="S34 27.25240"
lon="W058 34.94924"
name="ccf73614eed74478b2f7ee21bc341076"

MODEL OB9SAME0_33
Buenos Aires (SAEZ)
Larger odd shaped nice texture
lat="S34 48.85910"
lon="W058 32.53295"
name="3cd56eb22785456b94883900f96338cd"

OB9SAME0_26
Buenos Aires Argentina (SUMU)
Interesting angular 2 story
lat="S34 50.45523"
lon="W056 1.58268"
name="4581439afda9498c925740f3b893b6c9"



MODEL OB9SAME0_09
Mar Del Plata Argentina (SAZM)
larger angled with attached tower
lat="S37 56.04623"
lon="W057 34.82967"
name="71f27f38a62f45d49580168ce6349729"

OB9SAME0_13
Neuquen Argentina (SAZN)
interesting multi-level with wings

name="9e0ddc57614c4d48b7710be2e4aace25"
lat="S38 57.15137"
lon="W068 8.42753"

OB9SAME0_14
Neuquen Argentina (SAZN)
mirror image of No. 13
name="6fac945c68394e058c6763014785f3a0"
lat="S38 57.09984"
lon="W068 8.42750"

OB9SAME0_27
Neuquen Argentina (SAZN)
name="b9c1c09d308c47c6a04c62840c1452b6"
lat="S38 57.11710"
lon="W068 8.40095"

MODEL OB9SAME0_04
Comodoro Rivadavia Argentina (SAVC)
2 story medium large
name="013ab50bec5546eda8f8cd9534656f83"
lat="S45 47.45774"
lon="W067 28.38966"

OB9SAME0_22
Rio Gallegos Argentina (SAWG)
medium multi story
name="82dc4f7c81cc48e087a5e52e24936657"
lat="S51 36.68578"
lon="W069 18.44560"

 

[arno]

Could you just call the GUID at the other airport or did you extract the MDL objects first?

I thought the terminal objects would be area restricted. Or are you using them in the same part of the world?

 

[archtx]

location

Interesting observation Arno.

The new airport location is in a different part on the world than the terminal models. The default location of objects and models for the new airport should have been in the "north america central" scenery folder. My actual scenery files are in the Addon scenery folder.
The terminals were extracted from the "south america" folder. Nonetheless, I was able to call them only by guid number. So, it appears that as long as both scenery areas are active, the GUID is all you need. Check out the XML file I posted in the previous message. This location is in Cuba. All of the scenery objects and generic buildings in Cuba are in the north america central folder.

 

[arno]

But it could also mean that Cuba is close enough to the South America area you extracted it from.

Testing with locking of scenery objects has shown that in general when the placement and library code is in the same BGL, you can only access them around the area of the origional placement. How big this area exactly is I don't know either at the moment.

So it could very well be that the GUID that works for Cuba will not do so when you use it in Indonisia or so. But I was only asking to see if you have noticed any of such problems yet and it seems the answer is no .

 

[archtx]

Yes...that could be the case. However, they could still be used for airports in South America that do not have a terminal. Different ones could be extracted from Asia to use in Asia. I have found quite a few models that do not want to move to another location.

 

[arno]

Yes, using them in the same continent as their origional use should certainly work. If was just wondering if you had problems with the locking, to verify the theory of how it works .

 

[archtx]

Arno:
I did more investigation, per your request. They are indeed somewhat geographic in nature. When I tried to place the Guatamala terminal in Brisbane Australia. it did not appear. This is interesting. As I mentioned earlier, my airport where I successfully added the terminal before, is not in the same folder as the South American terminals, but because, perhaps as you suggest, the airport was within close enough proximity to South America that it worked. I tried adding a model reference to the XML file, and it still did not appear in Brisbane. I next created a library (using your XML Library Creator, thank you!) and placed the models in that. At that point, the Guatamala terminal did indeed show up at the Brisbane airport. Thus the conclusion is that the constraints on geographic placement are not in the model file, but somewhere else in Flight Simulator. This now brings up a new point. Is this true thruout the Flight Simulator scenery models? The old question about relocating the golden gate bridge to cross the Panama Canal. Or perhaps the models that are in the Landmark files are constrained, and others aren't. I will continue testing.

 

[arno]

I don't have all the answers yet. But at the moment I think it works like this.

The scenery folder or so does not restrict the usage. It is just that when the placement code and the library code are in the same BGL file, then the objects defined in the BGL can only be used in a certain geographic area around this BGL file. The exact size of this area is not yet known.

I think this is also way some of the MS objects can not be placed everywhere in the world. Only the objects that are contained in true library BGL files (so no placement in the same BGL) can be used worldwide.

 

[jvile]

arno

I have not found anything yet that I can't place where I want it but I am still looking.

This is the code I use to place the Empire State Building as far from New York City as possible as a test. It work in placing it in Spain and now here.

The city is Kuala Lumpur which is also in the southern hempishere half way around the world from NYC. The ESB is sitting between the twin office towers and the tall needle building downtown.

<?xml version="1.0" encoding="ISO-8859-1"?>
<FSData version="9.0" xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
xsi:noNamespaceSchemaLocation="bglcomp.xsd" >

<ModelData
name="3ebedf0d11d2f0721000849c2ae60c5a"
sourceFile="ldm_ny_empirestate.mdl"
fileOffset="0"/>

<SceneryObject lat="3.15446989614946" lon="101.706883840341" alt="0.00"
altitudeIsAgl="TRUE" pitch="0.00" bank="0.00" heading="270"
imageComplexity="NORMAL">
<LibraryObject name="3ebedf0d11d2f0721000849c2ae60c5a" scale="1.00" />
</SceneryObject>

</FSData>

When I compile this XML I make sure the Model Source File "ldm_ny_empirestate.mdl" is in the folder also.

I copy the compiled bgl to the Generic Scenery folder and also but the 2 ESB textures in the Generic texture folder.

Alternate install is make a scenery folder for the bgl and 2 textures and point to it inside the scenery.cfg.

Any GUID in FS9 that has textures I have been able to extract and place anywhere in the world.

I use this method of placing default scenery in the Active ILS airports I write which mimics a default APxxxxxxxxx.bgl file.

My lastest upload (today) is KBUF using just one bgl and write the data in this order

the exclusion for the extended 14/32 runway,
adding gate jetways using method above
many default FS9 GUIDS for ramp scenery
airport id
new taxiway signs
ILS approach data for the new runway 32 ILS
new waypoints for the IAF and the FAF for runway 32

I keep seeing post on forums that say this can't be done but yet I am doing it and using only one bgl for all the airport data.

What am I missing that can't be done. I have even take jetways from one default airport and put then into another terminal that doesn't have Jetways.

Could you give me an example of what type GUID can't be used somewhere else so I can try and move it/use it.

thanks

 

[rhumbaflappy]

The geographic locking concerns the placing of some of the default objects from the UNDECOMPILED default BGLs.

Some default BGLs have no placement code, which allows their placement throughout the world by simply referencing the GUID in a placement BGL.

Other BGLs have placement code along with the ModelData inclusion... that's what locks them out from other areas.

When I compile this XML I make sure the Model Source File "ldm_ny_empirestate.mdl" is in the folder also

You can ALWAYS place the object if you include the ModelData in the XML. This is what makes a new object.

You are using decompiled MDLs from the default BGLs. You are actually making copies of the originals, even though you are using the same GUID numbers.

In fact, your new library objects are now also geographically locked, as they have placement data within that same BGL. You don't notice it, because you are including the MDL ( again ) in the compiled BGL with each placement.

There's nothing wrong with this, but if you distribute BGLs that have both ModelData and placement code, they will be geographically locked for other users. Better to make them as ModelData Libraries, and a separate BGL for the placement. That allows the objects to be global.

The whole idea of a Library is to be able to reuse the MDL in multiple locations, without having to include it each placement instance.

Dick

 

[jvile]

Thanks Dick

I am starting to see the actual objective which differs based on what the end result is used for.

In my example I am placing a new locked object in my scenery for upload but it is not objects that can be shared amoung others because they are still locked.

Now the other objective is to find a way that the Lock Library objects can be uploaded simular to what is in arno's objlib.xml and shared amoung everyone.

 

[rhumbaflappy]

All the default objects in FS9 can be decompiled and the ModelData entered in XML code to produce unlocked versions... they just can't be placed within the same BGL. Just declare them, and they become global objects.

<?xml version="1.0" encoding="ISO-8859-1"?> 
<FSData version="9.0" xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' 
xsi:noNamespaceSchemaLocation="bglcomp.xsd" > 

<ModelData
name="3ebedf0d11d2f0721000849c2ae60c5a"
sourceFile="ldm_ny_empirestate.mdl"
fileOffset="0"/>

</FSData>

The above code creates a Library BGL that has only one object... it is global because there was no placement for the object. You can include hundreds of ModelData entries in the same BGL, and if none have placement, they will all be global.

This isn't anything new. It was all discovered and resolved within days of the BGLComp SDK release. I never made a giant unlocked Library of all the MDLs because I perceived a possible copyright problem with both Microsoft, and with the authors of the decompilers we use... we'd be copying other's work and using it in our own BGL. Seeing as MS made the MDL location-specific, their intent may have been to not allow the MDLs to be placed anywhere else. Sounds odd, but that's how I see it.

Anyone else is more than welcome to make and distribute such a BGL at their own risk... I just won't do it.

Dick

 

[arno]

Yes, I agree with Dick here. Editing default BGL files and releasing them again does not sound like a good idea.

Most of the locked objects are city specific anyway, so I wouldn't want to place them on the other side of the world in the first place.

 

[jvile]

Thanks Gentlmen

Your points on this are well taken and I also will adhere to the above cautions.

I have been writting XML for airports that install new runways that have an ILS for many months and just recently started to enhance my files with additional GUID's. Scenery is not my strong area so I will continue to abide by the consensus of how you guys perceive the locked GUID's.