I have been struggling with this issue for a little while now but have normally been able to find a solution but I am really at a loss at the moment. From time to time when installing new add on scenery some airports default buildings remain overlapped with the addon on buildings.
Sometimes I have been able to resolve by ensuring the addon AFCAD is in its own scenery folder or raised priority in the library but I have just installed Flightbeam's KSFO and tried everything but the buildings still remain overlapped.
Flightbeam Ksfo Download Free
Download 🔥 https://urloso.com/2yGbO2 🔥
The only possible conflict I could have had was a Jetways and Terminals for ACOF for a lot of airports but I have removed that entire scenery from the library and FS completely to ensure their is no conflicts with that, but it appears to make no difference and the default terminals are still their.
So just to recap their is no conflicting scenery for KSFO, no other AFCAD's (just the default stock). There seems to be alot of topics on similar issues but most suggesting their is conflicting scenery which to my knowledge I don't have. Wondering if the Jetways scenery area left a file behind somewhere that's causing this as its a few airports, but no idea where to look or how I would find?
I have had this happen at many add on sceneries. To solve it I had to delete the default scenery. If you want to save the default scenery you can back it up to another folder outside of FS. That way if you need to put it back into FS you have it saved.
All addon sceneries must have higher priorities in your FS9 scenery.cfg library, in other words, they must be physically situated above any default scenery entries, which all need to remain near the bottom of scenery.cfg listing. If this is the case, then your related addon Adcad files may also remain within each of your addon scenery folders.
As a last resort you could search for, download and install a program called "ExcBuilderV2" or higher. When set up correctly you have the possibility of creating (partial) deletion rectangles for any default scenery objects which cause the types of problems you evidently have. Also for AG trees, etc, which can unexpectedly appear on e.g. addon runways.
This is a commercial product, if that is a problem it should surely have been fixed. Nobody should have to faff around fixing it. I would contact their support for advice - there may be an update available.
Yes agreed however as I mentioned it's not the first time this is happening when I have added new add on airports ( various airports, various scenery producers). I am in the process of pouring through the flightbeam forums and will send an email but because it's not the first time this has happened it suggests to me that it's maybe a "rouge" or stray file in my setup somewhere.
In all my very many simming years I've never heard of Afcad data or an Afcad file, somehow being able to influence the appearance of both default (airport) buildings and addon (airport) buildings, so that a visible mix of both becomes visible. Very strange indeed because under all normal conditions, any addon airport having a higher priority than the default version in it's APnnnnnn.bgl file, should supress that default one completely, including it's afcad data.
I don't think it is quite that simple. Any add-on will need an "exclude" created to remove default buildings, taxi signs and other miscellanea. Earlier sceneries would supply this as a separate file but the technology used to create more modern A&FD files can include that in those files.
So if the latter applied and the A&FD file has been modified without the exclude data being saved, there is every risk of this situation occurring. Nick has not suggested he has made any modifications, but it is possible some hasty changes were made by the developer before issue, creating this situation. Another possibility is that a separate exclude file may have been accidentally omitted from the download, or missed during the install process.
"So just to recap their is no conflicting scenery for KSFO, no other AFCAD's (just the default stock). There seems to be alot of topics on similar issues but most suggesting their is conflicting scenery which to my knowledge I don't have. Wondering if the Jetways scenery area left a file behind somewhere that's causing this as its a few airports, but no idea where to look or how I would find?"
Scanafd is one tool that could quickly tell if there might be conflicting scenery, but it's not fool proof as you could have a scenery without an afcad or an afcad without a scenery. but if you ran it and found you did have a duplicate afcad it could jog your memory to a scenery you had installed and forgot about.
I suppose you could be correct but only in a very isolated case where a scenery developer has not completely tested his creation before posting it. Moreover, Nick writes that his problem has occurred with a number of his addon airports, which makes it highly likely that there is something structurally wrong in his FS9 setup or with his own installation procedures. Hence my "last resort" suggestion for using a separate program for deleting default scenery objects.
I didn't mention in my original post as could not be 100% but I was sure I installed the scenery one time and went to the airport and found everything ok which would almost backup the lines being suggested.
I'm thinking that I might have replaced the AFD supplied with the scenery to another third party one (possibly), which according to John's post above may have some bearing on the exclude parts of the scenery and install.
IME this issue can be caused by not removing all of the associated files. Most scenery will only have files that are added to your selected location (i.e. for most users the default Addon Scenery folder) BUT some scenery packages will have you add an additional file (normally something named _ALT.bgl) into the default Scenery/World/Scenery folder. If this file is left behind when de-installing the main scenery files it can cause issues with the original default airport or other 'new' scenery files for the same location.
Another possible reason for the issue is that you have installed a 3rd party dedicated AI product (such as Traffic 360) - these products tend to get installed into their own folder structure within the siim and will often contain their own scenery.bgl files. Most of these files will be basic and, if viewed in an editor such as AFCAD or Airport Design Editor (ADE), only contain very basic 'taxi line only' routes but some can also contain objects including buildings and full taxiways etc..
Placing such products as low down the scenery list as possible, but above the sim default areas, will normally mean that other addons override them but occasionally the included .bgl file causes issues - this is normally manifested as AI aircraft taxying along routes where there is no taxiway in the current scenery being used but does occasionally cause other issues.
A little update from me and it seems I was right and I had subbed the provided AFD file with a third party downloaded one. I guess the main reason for doing this is to have a more update and realistic parking setup at the airport as the provided one tends to be a little outdated.
You can never succesfully use Afcad data which was developed for another version of the same airport. The visible terminals, their placements, their related gate/parking positions, etc.etc. are simply not exactly the same and therefore not compatable. It will result in AI aircraft parking in strange positions not related to the visible buildings, their gates, etc. etc, some AI aircraft even (partially) parking inside the buildings themselves.
As pointed out by Hans (post #19) various issues can occur, especially if the creator has fully updated the scenery to take into account known issues regarding its actually location in the sim world versus the real world, updated building locations, etc
You could try editing the file to add the required excludes. There are a number of tools available to edit/create scenery and, whilst the learning curve can be steep to create a full airport, the addition of excludes is relatively easy.
The main dependency on the editing the airport is based around the original tool used to create it - the more common tools used is either a version of AFCAD (FS2004 only) or Airport Design Editor (ADE - FS2004 and FSX). Normally, an creator will include details of the tool(s) used in a readme but not always. Additionally, if the original creator has not changed the default naming convention you should be able to ID the tool used from the name of the main airport .bgl (i.e. the one that usually contains the main runway/taxiway layout) - it will be similar to these examples:
When editing such files it is generally best to use the same tool that was used to create it. This is especially important with those created using AFCAD as, if you open it in ADE, it MAY lose some of the formatted features - but there are exceptions/occasions when you can safely use ADE, see further on.
Generally there are two types of excludes used - one that is a targeted area specific exclude used to remove default items in a specific or small area. The other is based on a larger area that is normally used to cover the whole airport area. The first only affects the targeted area whilst the other, as it implies, will affect the whole airport - this may cause other issues if the creator has purposely used other default objects in a correct location.
WRT to possible losing features - I am now solely an FSX user but actually use a lot of FS2004 scenery in it (mainly MAIW AI and associated scenery) and the main issue often found is that FSX default objects appear where they shouldn't. I use ADE to import/edit the airport scenery, including those created using AFCAD. I have set the tool to use an option enabled that compiles the various 'components' used to build the airport into separate .bgl files. I then add an exclude that covers the whole airport, re-compile the airport and then only copy the exclude .bgl file into the same location as the scenery. This normally resolves the issue and leaves any original AFCAD formatting in place. However, occasionally I have to use targeted excludes. 152ee80cbc