Hi all,

I wanted to put this out there and ask your opinions and something I have been thinking about yesterday. I think the answer maybe a yes though but here goes.

For those of you who have MKStudios Keflavik, when you install that scenery, it deactivates the relevant ORBX files around that area so it does not conflict with the actual scenery. ( I get that )

I also noticed yesterday, when you install an ORBX ariport it also deactivates the necessary bgls in your ORBX region ( if you have one ). What I have noticed though and this is my question, is it good practice to go through all your bgls and name them to OFF if you have a 3rd party scenery. ?

Most sceneries do not have a problem with bleed throughs and duplication errors but I cannot help but think this may be GOOD practice to do this, even though it is a little tedious doing this following an ORBX refresh as it restores the files as they were so you are having to repeat the process.

I had a thought going through that is if you have duplicate bgls of an airport which is adeqautely covered by an exclusion file to stop bleed through, is the sim  STILL trying to draw that scenery in the background. Are there any scenery experts that can confirm if this is the case. ?

 

What are your thoughts and experiences ??

12 minutes ago, Steve_Ellis said:

I also noticed yesterday, when you install an ORBX ariport it also deactivates the necessary bgls in your ORBX region ( if you have one ). What I have noticed though and this is my question, is it good practice to go through all your bgls and name them to OFF if you have a 3rd party scenery. ?

 I cannot help but think this may be GOOD practice to do this, even though it is a little tedious doing this following an ORBX refresh as it restores the files as they were so you are having to repeat the process.

I had a thought going through that is if you have duplicate bgls of an airport which is adeqautely covered by an exclusion file to stop bleed through, is the sim  STILL trying to draw that scenery in the background. Are there any scenery experts that can confirm if this is the case. ?

It is often overlooked that all the Orbx regions add airports, so they are already "third party addons".

If another "third party addon"airport is added  in the same place, even if that "third party addon" is also by Orbx, then you have two "third party addons" and it is a good idea to disable at least one of them. Apparently if an airport is "correctly" modelled, it will include an exclusion for all other airports that are below it in the scenery library but logic would suggest that disabling the unwanted "third party addon" is a catch all and therefore good practice.

My understanding is that if an exclude is working, it does indeed prevent the other feature, rather than suppressing it in the background. I would personally not rename files manually unless there is a problem to be seen in the simulator.

If you intend to regularly update, reinstall or otherwise tinker with your installation, then the better solution than renaming files is to remove them altogether for their folders and store them somewhere safe. In the event that tinkering restores the unwanted files, they can be copied back into the folder from the store and when highlighted, as they are by this process, deleted all in one go.

Edited June 12, 20205 yr by Reader

Yes, it is good practice.

 

Whenever I install a 3rd party add-on airport in an Orbx region, I do looking for the corresponding .bgl files and rename them to OFF just as matter of practice. Its very hard to tell if a scenery developer is including those changes in their installation process or not.

The only other thing to watch out for, is if a scenery update from Orbx comes along, it can undo those changes, so they need to be reapplied.I dont believe the Orbx installers can register those changes you made manually unless its part of an Orbx  configuration file.

 

regards