X Plane 11 Google Earth Scenery

[Miss Ruhnke]

Please note that some third party airports may be missing the required exclusions. This is not an Orbx problem. If an airport designer does not use a proper exclude for the airport boundary then it is possible our scenery layers (and any other scenery layer) may interfere with the airport. If you experience interference from TE GB at a third party airport and the scenery layers are as per above, please contact the developer and request an exclusion to be correctly added. Update 18-Oct-18: We will add exclusions to all affected airports by incorporating fixes contributed by FlyAgi in the topic below, and also adding our own fixes for missing exclusions. In this way we can patch TE GB in a coordinated, official way via FTX Central. Thanks for your patience in the meantime.

Is the exclusion zone thing not something that you can fix? GBPRO worked fine for me in terms of this autogen issue. I'm also yet to find a single airport apart from the payware Heathrow that this works for.

Strangely I don't have SCENERY_PACK Custom Scenery/X-Plane Landmarks - London/ in my scenery_packs.ini after and before the installation. I understand this is Laminar's own, but how can I make it appear?

I converted the jpg files in dds files by adding the "convert" file in the texture folder. It took some hours but now everything works perfectly as you can see on the picture.....Marvelous work....I'd pay a lot for the same quality scenery of whole belgium.....

Cleaned up the order in my scenery_packs.ini file last night, then flew my Bae Hawk in VR from Llanbedr all the way South around the Welsh coast, up the Severn estuary across the bridge down through Somerset to the Dorset coast and along to land at Shoreham taking in all the sights. Awesome, got a real sweat on felt like finding a good bar to unwind after a good days sortie! Wonderful stuff! Thanks for all your efforts and a stunning product. Next phase the Central.....bring it on!!!

I'm not having any issues with TE GBS as such, but reading this and looking at my scenery.ini inspires a question or two. I can also see that all the ORBX products get installed as "ORBX_xxxx", which seems to be a technique also used by some other scenery vendors like Aerosoft, DD etc. This makes sense in that a vendor can then ensure that all their own products are in the correct order within their own section of the scenery.ini file. I can see that products like Ortho4XP label their folders/links to begin "z" to ensure placement at the end of the ini list, which is also a good thing. My understanding has been that the XP "Global Airports" should really be below all specifically installed airport entries.

I had previously been going through prefixing my folder names with headings like "AAA" for airports, "LIB" for libraries, OVL, ZZZ etc, so that everything was automatically in the correct order alphabetically, but that became too frustrating for a number of reasons. It meant separating out the different folders in the individual airport packages like ORBX's Meig's Field, for instance, plus in ORBX's case would mean that FTXC doesn't recognise that the product is installed. I also played around with X-Organizer to try and arrange things into groups in the same sort of fashion I use with P3D and the SCE, but frankly, I thought it caused more problems than it solved, so I have gone back in and returned all (well, most) folders to their original names, deleted my scenery.ini and let it rebuild itself alphabetically.

I then moved the "X-Plane Landmarks" folders above all the ORBX stuff, and "Global Airports" is already alphabetically ahead of all the ORBX entries. And that (finally!) is my question - do I need to split the ORBX entries within my scenery.ini so that all the ORBX airports are actually above Global Airports and only the TrueEarth entries are below it?

Your post ends with a mention that Ben will be looking at further development of the FTXC code regarding the scenery.ini environment. For me, this whole scenery.ini environment seems to be one of the weaker points of XP, as controlling large collections of scenery and its associated libraries, mesh entries etc can get messy, especially given that any complicated manual manipulation of the scenery.ini is replaced by a pure alphabetical entry any time there is a problem with the ini file and it gets rebuilt. Perhaps something within FTXC to separate out airports and regions via a naming convention like "Airports_ORBX_KCGX_A / B / C" and "Regions_ORBX_GB_South_TE_A / B / C" would help ensuring things got placed correctly in the bigger scheme of things. Just a suggestion, and only even worthwhile if the answer to my "Global Airports" question is that the ORBX entries should be split above and below it.

While I'm here, I'll also say that I had absolutely zero problems downloading, installing and running TE GBS, which is pretty damn impressive for such a massive piece of software, and I've said in other posts what a marvel I think this product is, so congrats all round, and I don't suppose you've ever considered taking over and running Microsoft, have you John? Now there's a company that could learn a thing or three from ORBX.

I have tried using the convert.cmd command but get an error message saying that texconv.exe was unable to start correctly, what do I do now as I have been trying to install this scenery since sunday morning.

Your method works by deleting the entire scenery-packs.ini and let X-Plane create a new one by alphabetical order. The JV method has to be done manually, you have to edit the scenery-packs.ini and move the entries to the right position yourself.

Renaming the Orbx folder names is not a good idea. This will break the automatic patching of updates and bug fixes by FTX Central, which will be looking for specific folder names. This will lead to more support issues in the future when updating fails.

It's not that hard. Regarding TE-GBS all you need is to care for the Global Airports entry and then place all TE-GBS entries below the Global Airports line, in the correct order, A, B and C. Of course you will need to do this manually in the scenery-packs.ini file.

I tried xorganizer but my problem is that as I said if I do in the order stated it just wont work at all. if global airports is above the orbx ones it just wont show up and that's what I don't understand. I have just installed a second copy of xplane 11 and will use that as a test platform.

What does not show up? TrueEarth or the global airports? If TrueEarth does not show up you will very likely have some other mesh sceneries placed on top of it - make sure that TrueEarth is above ALL mesh sceneries and below global airports.

I strongly recommend not to micromanage the scenery order. This is completely unnessessary and just causes additional work. Make sure that all mesh sceneries are placed at the bottom of the file (in the right order if you have different meshes for the same location of course) and below global airports. All custom airports have to be above global airports and libraries can be irgnored for most part - if this is all true, most of the stuff will be fine.

Hello JV, if i may, i'd like to make a suggestion in regards to AIRPORTS and only airports. The current naming standards that XP uses is ICAO - Airport common name. Those of us who make/improve/download gateway files are used to using this format, and many (not all) designers use it as well would it be possible (*yes i'm sure it will be a pain in the rear) to swap the naming of AIRPORTS ONLY to follow that format? While I fully understand asking us to not rename folders since it will cause issues it would be nice to have a single standard used when it came to airport scenery. As an example I've cut a bit of my ini out this is a Gateway scenery, an AS scenery, 2 Orbx and finally one from SFD (MrX6) Using this format would maintain the prexisting format, yet allow for your automatic updating. And again i'd like to mention this is for airports and airports only having Orbx in front of TE and other non airport scenery is fine because it groups them together and if a manual adjustment of the ini is needed makes for an easier time in locating them.

I've tried ompletely removing the Custom Scenery folder and reinstalling it from scratch using the X-plane 12 installer, then re-downloading the scenery and re-installing using Orbx central. Same result. Deactivating the Orbx scenery restores the terminal buildings.

Move the Ortho below Global Airports in the list and all should be well. You may wish to move X-Plane Landmarks London below the ortho if you find it messes up your scenery. If you delete this file, XP will re-install it at the next update.

I do wish XP wouldn't mess with the ordering of the ini file. There's plenty of times I have it ordered as I want, only to find that XP has rescanned (I guess mostly when detecting new scenery), and then changed the order to what *it* thinks, which breaks stuff (even if the new scenery has already been manually added to the file, in the correct ordering, therefore no file changes *should* need to be made.)

c80f0f1006