Solving Errors (Debugging)         Back        



Fine Tuning             Problem Solving        Water All Around            Adding Extras          Community Links

X-Plane was designed as a flight simulator to closely mimmic the way real aircraft fly.  The compromise to this design was to make the scenery simple and functional so that the detail did not interfere with the basic function of the design.  WED is a design tool that was orignally meant to design Gateway airports from a functional and standard set of scenery objects and overlays to make the airports functional.  In its original default form, there are few issues with its function.

The addition of airports, detailed scenery, enhanced weather and different aircraft is a community driven thing.  You can add payware or freeware to enhance the sim as you go.

When scenery is designed as a custom add on, requiring extra library objects, or the addition of a custom function or othographic scenery file is made, the precise setup must be compatible with the design of X-Plane, or the function of the simulator may be compromised.  Typically, scenery may not show correctly, two different airport designs will show in the same space, trees may appear on runways or bits of scenery will flash and flicker - with lots of other permutaions of functional errors.

What if something does go wrong?

First question - Is your computer of a suitable specification to run the version of X-Plane you have?  If the CPU and GPU combination are not working well, or if you have too small a memory cache or have too many demanding add ons installed, that may be the issue.

If you are organised you should have 2 versions of X-Plane installed on your one computer - You are allowed a backup version on the same machine using the same activation code (not so easy if you are using the Steam version).  Only load an addon to one copy of XP.  If it works for a few weeks without problems it is safe to add it to your backup copy.

Often the first place to look is in the Log.txt file in the X-Plane folder.  That file is written for the last session and is a good diagnostic tool in the right hands.  If that file is not helpful, then you need to systematically debug the problem.  Here are a few simple methods.

1. If something does not work correctly, it is always worth running the X-Plane ?? installer.exe from the X-Plane folder to check if there is a problem with the core X-Plane software or updates.  Anything that is missing or corrupted is normally updated correctly.

2. Also worth a try is to close down XP and then reload again.  That can correct any issues that you may have with resident memory.

3. If you are getting missing library messages, then adding the missing libraries or updating ones that you already have installed my solve the problem.

4. If none of these options work, the next stage of problem solving is a bit more complicated.  If the problem you are experiencing is caused by a scenery add on or another added application, you will need to find and isolate the culprit. This will require you disabelling add ons in turn and seeing what effect that has.  OK is you only have a few add ons, but not so good if you are a long time user.

Disabling scenery files.

In the X-Plane folder is a folder called Custom Scenery.  That is where all add on scenery is installed.  At the end of the folder is a text file called scenery_packs.ini.  This instructs X-Plane what to load - reading from the bottom of the list, upwards.  This file can be edited in a text editor and saved.  If the file is deleted, X-Plane will recreate it at next load.

Each line of the file contains an item of add on scenery and a typical start of the file looks like this:

     I
    1000 Version
    SCENERY

    SCENERY_PACK Custom Scenery/00-a-ENFL-Floro-tdg/
    SCENERY_PACK Custom Scenery/Bielefeld/
    SCENERY_PACK Custom Scenery/Conningsby/
    SCENERY_PACK Custom Scenery/EGDY-Yeovilton/

The first 3 lines must remain the same, so that X-Plane can identify the file type.

To disable a scenery item (for instance Conningsby) the line needs to be altered as follows:

    I
    1000 Version
    SCENERY

    SCENERY_PACK Custom Scenery/00-a-ENFL-Floro-tdg/
    SCENERY_PACK Custom Scenery/Bielefeld/
    SCENERY_PACK_DISABLED Custom Scenery/Conningsby/
    SCENERY_PACK Custom Scenery/EGDY-Yeovilton/

By adding the markup _DISABLED, X-Plane will not load that file.  If that action solves the problem, then the culprit is found, otherwise more disabling is needed.  Best to start with the last add on and work backwards.

5. No joy - Then now is the time to use the X-Plane forum or a help group.  Explain the problem, add a screenshot and attach your log.txt file as appropriate.  That should provide enough evidence for an experienced user to make a good estimation of the problem.