Jon Clarke

The pics you have showed just now are not of TEGB South. They are of the default scenery. This gets more intriguing. Open your Custom Scenery folder and open the TEGB South folders and tell me what you see and the size of each folder please. TEGB South is not showing. Have you touched the folders in anyway or moved them from one location to another? Also please run the Verify Files for TEGB South using Orbx Central

Is the file you refer to a standalone file/mod sitting on it's own in the scenery_packs? The old Mod was called KTMK Tillamook (Modified default) Retain everything within the TE addon files. Place the new Mod above Global airports.

First time i have ever seen this so bear with me. Is the TEGB South addon installed in the XP11 directory or so it installed in a library you made? Initially please run the Verify Files option in Orbx Central for TEGB South in case there are files missing. I would also like to see a cockpit view pic if it is showing TEGB South looking OK. Can you change the assignment you have for the view behind? What does a pic in Spot View look like? I have also rearranged your scenery_packs. It will not resolve your issue but is now optimised for when we do resolve this. scenery_packs.ini

Welcome Please post a pic of the issue. Also attach, not a photocopy, your scenery_packs.ini. Do you get any on screen error message. I will attend to your reply early a.m. UK time Tuesday as i am logging off now

I assure you that performances were tested otherwise they would not have been released and the forum would be full of reports of them being unflyable. The issue you are having will be related to not only the density of detail in the surrounding area f the airport but also on your settings. One XP seeing does not act a a £fits al scenarios£ one unfortunately. There are reports of fps loss at some terminals by some people. Searching the forum will show you some posts like this for EGNM in which you see that I show pics of 30+fps: Here is a post about EGNT: EGLC is surrounded by the most detailed and intense autogen and POIs outside of KLAX and does have a performance hit. You will have fps hits and that de[ends on what your XP settings are, what plugins you may be running, what payware resource demanding plane you are flying, what screen resolution you use etc. I just want to reemphasise that performance was tested by the beta testers and each tester has a different rig set up and runs different settings. The results are of course variable.

I see no "huge V" at EGPT:

Please attach your scenery_packs.ini and indicate the location of where your pics are taken at. I want to check if I see the same, especially at the location of pic 1. Please also advise me about the "multiple users" having the same issues. TEGB addons have been out for several years now and I do not recall reports on the forums here of such anomalies and customers wanting refunds.

Thanks for the tip. it will help those who experience the issues you had. I tried it and did gain a few fps.

I think it is a result of changes by the SAM developer as to how SAM is installed. Check in your Resources/piugins folder for SAM and then check if you have a folder called "libs" in there. if you click on that folder it should then show a folder called SAM Library. If it is in there then test by removing the SAM Library folder that was placed in your Custom Scenery folder. SAM was only offered by Orbx because it is used to run the jetways at a couple of Orbx airports like EGNM and only the SAM Library is required for that aspect. I have SAM installed in the plugins folder in Resources and have no entry for SAM in my scenery_packs. Installing it into Resources was the newer installation method by the SAM developer versus into the Custom Scenery folder which was the previous way.

Both

That topic did not say to have Oregon above Washington from what I can see. I referred to a topic that had issues with TE Washington and Oregon. That topic was actually the Tilammook Creamery. The sequencing of TE Washington and Oregon by Orbx Central is fine. The situation we are talking about here is a unique one in that there is a shared vicinity object between Washington and Oregon, so that is why there is an issue. This to my knowledge is not experienced elsewhere in the TE addons. The TE addons will be placed under Global Airports by Orbx Central in the sequence of the date installed. Because of the unique nature of the Tillamook issue, it requires the Mod and to manually move TE Washington above TE Oregon in the scenery_packs. That is the solution.

That message is not mentioning an error with TE Washington specifically. It would state TE Washington if the errors were in that addon. That is why i think you need to remove all the backup copies of TE Washington airport addons from Orbx that you have and run the Verify files options for all. Verify Files will initially read from any backup copy you have. If you don't have a backup then it will use the Orbx server copy to check files etc so even if you have run the Verify Files option, if the addon is corrupted it will be repeating the problem.

I can only offer the resolution you already have. What was the issue with Portland that required Oregon to be placed above TE Washington.

What is the on screen message fro TE Washington. post a pic. Darrington shows an error in your Log that is why I mentioned it Rename your Custom Scenery folder to Custom Scenery.BAK. Maker a new Custom Scenery folder. Drag and drop TE Washington files into the new folder PLUS Global Airports. Run XP and exit. Open the scenery_packs and make sure that TE Washington Airports is above Global Airports. The scenery parts of TE Washington below Global Airports and in the sequence like you have at the moment, of Custom/Overlay/Orthos. Run a flight in TE Washington and post a pic of any On Screen error message you get. If you do get one then remove any Backup copy of TE Washington you may have, and then run the Verify Files option. Report back. It may require a reinstall of TE Washington if the issue persists after having done ALL of the above tests.

Ok thanks. Have you run the Verify Files for Darrington 1S2? If you have a Backup copy of Darrington then remove it and then run the Verify files. This is in case the backup copy is corrupted. Verify Files will initially read from any backup copy you have. If you don't have a backup then it will use the Orbx server copy to check files etc. The best option of all is to use Orbx Central to uninstall Darrington, reboot PC and then reinstall. Report back with the XP log file attached if you still get an On Screen error message

The resolution was offered at the end of that topics posts. There is a mod zip file offered. You need to download, unzip and place in your Custom scenery folder making sure it takes a high position in the scenery_packs If you have both TE Washington and TE Oregon installed also make sure that the 3 TE Washington Custom. Overlay and Orthos files are above the TE Oregon files. Orbx_A_US_Oregon_TE_Tillamook.zip

Thanks. Please also attach your XP11 Log file

We need to ask the dev about this. He is extremely busy at present so I don't know when he will be able to answer @Tony Wroblewski

Are these On Screen messages or just from the Log file? If they are just from the Log then ignore them as most wil be remnants of previous OrbcLibs references. If they are On Screen error messages then we need to look further and will need your Orbx Central log file attached.

From top down: 3rd party airports Laminar Global Airports Laminar London Landmarks only if you have Orbx TEGB South Orbx True Earth addons if you have them Laminar Landmarks 3rd party sceneries and scenery enhancers like SFD Global/ X-Europe etc Libraries like openscenery, Mister-X etc ortho overlay if relevant ortho photo scenery 3rd party mesh If you ever have an issue you can always post with an attached copy of your .ini and I will check it out for you.

@Ed Correia Please comment Ed on the customers suggestion.

Welcome. I just answered another post about Nimbus KMIA and TE Florida here: The Nimbus KMIA should not be affected by Orbx Key West but as to it's compatibility please check the Nimbus forums where they were issues in the past but i don't know if they were resolved by Nimbus

Correct, and also lowering settings in the downloader/conversion section of Orbx Central can help. The TE addons are also extremely large and require extensive extract and conversion processes so often will take a long time to complete. SD versions do not require conversion processes and are quicker. I was seeking additional assistance from those in the Orbx Central team to clarify or advise further if there is anything other than the norm that could be done, and also explain why sometimes there is a need to Close and restart.

Here is a post that makes reference to the Nimbus airport but in a different scenario to yours. He does not mention non compatibility just a duplication which is resolved by removing KMIA from the TE Florida/airports file. Maybe you should also check with Nimbus

@Nick Cooper Pease assist or pass to the Central support team. Thanks.