Custom Scenery 64 Bits On Every

There are several versions of WED from which you can download.

Additional information on how to use WED, including the manual, can be found on the Scenery Development Documentation page.

System Requirements: WED should run on Windows 710, OSX 10.9 or Linux with GLIBC 2.23.

Custom Scenery 64 Bits On Every

WED 2.0 is now 64 bits on every platform.

Latest Stable Version WED 2.2 is an incremental update that features the ability to preview facades in 3D, faster loading, and up to 100 undo operations.

More info in our privacy policy.) Youll receive about one email a month, and you can unsubscribe at any time.

X-Plane 2020 Privacy Policy.

And of course, how should all of this be ordered in the scenerypack.ini file.

You need to check the right order in your scenerypack.ini file.

You need to check for example that add-on airports are at the top of this file and AlPilotX mesh packages at the far button, and oh yes, libraries somewhere in the middle already confused.

What Ive done is collected them and added my own writing skills to it.

Although some of the screenshots in this article are taken on an iMac thus with macOS installed it follows the same principle on a Windows PC and Im quite sure also on Linux.

Its very important to get the order correct, as having incorrectly ordered scenery can cause strange problems, such as trees on a runway, or a completely blocked scenery.

Since X-Plained.Com offers besides a couple of freeware airports, a lot of libraries, and many questions come along how to do this, I dont see my airport, I do get a lot of error messages at startup, and so on, its perhaps a good idea to make a backup of your original read clean Custom Scenery folder and store it a save place.

The macOS Finder screenshot below shows you an example of the default scenerypack.ini file or perhaps even better to say a clean install of a X-Plane 11.xx.

The default global scenery, alpilotxs HD Mesh v3 and Ortho4XP photo sceneries are all mesh sceneries.

If a mesh scenery is placed on top of another mesh scenery, it will completely block it out.

This is a key point here, if you have, for example, HD Mesh v3 and Ortho4XP photo sceneries, whichever one is higher priority will block the other.

Overlay sceneries are always placed on top of basemesh sceneries.

Examples of overlay sceneries are World2XPlane sceneries, Simheaven scenery containing landmarks, a scenery containing roads, and so on.

This is important, because without exclusions, one overlay scenerys objects could conflict with another.

The global scenery and HD Mesh, for example, include autogen, and if an overlay scenery provides its own houses (such as World2XPlane), then it will have to exclude the autogen from the base mesh below.

If you place an airport below an overlay scenery which has exclusions, the exclusion might block out the airport.

This way, the default scenery and autogen will show through in otherwise empty areas.

A scenery can be told just to block forests, or roads, or houses, etc.

World2XPlane sceneries include their own roads, and as such always include an exclusion to block all roads from the scenery below.

Without such an exclusion, the roads would be drawn twice and look a mess.

As long as you follow the simple rules (to follow), then you shouldnt have any issues with the sceneries.

Whilst some airport developers do correctly create exclusion zones, others dont, and airports without exclusion zones are the main cause of seeing trees or objects on an airport ground.

It should be the responsibility of the airport developer to create the exclusions, however not everyone does.

If you find such an airport, Id suggest contacting the author to get this fixed.

The above may be boring stuff, but it is essential to understand the rest of Tonys article.

So lets move on and see the more practical steps including the ordering of your scenery in X-Plane or if you prefer how is your scenery build up when X-Plane is up and running.

Download Custom Scenery