Tips & tricks

Here I have collected some tips & tricks which may help you with X-Plane:


Placing scenery and other files on a different drive

Using links to place Scenerypacks at a different location than your X-Plane installation can be a good choice if:
– You don’t have enough space on your X-Plane (SSD)drive
– You want to share files between different X-Plane installations to reserve space or keep them in sync

It is a bit more nuanced than this, but to keep it simple there are 2 ways to achieve this:
– Softlinks / shortcuts
– Hardlinks / junctions

So which of the 2 should you choose? If what you want is only about the Custom Scenery folder I would stick to softlinks / shortcuts.
If it is also about other folders (like plugins, Global scenery, etc.) you have no choice but to use the hardlinks / junctions. X-Plane can not handle softlinks / shortcuts for these folders (only for the Custom Scenery folder)

How to make Softlinks / shortcuts

Softlinks or shortcuts make it possible to place a scenery folder (scenerypack) on a different location or drive. X-Plane sees this and takes care of it. Here is how to create one:

  1. Go to the scenery on the other location and right click:
    Shortcut 1
  2. Open the Custom Scenery folder of your X-Plane installation and right click:
    Shortcut 2
  3. After the paste the folder will show the shortcut (you can rename it if you want):
    Shortcut 3
  4. After startup X-Plane will display the scenery in the ini file as follows:
    Shortcut 4
  5. That is it! Just delete the shortcut if you want to get rid of it (the original files won’t be touched)


How to make Hardlinks or Junctions

Hardlinks or junctions make it possible to place any folder on a different location or drive but in such a way that applications like X-Plane do not notice that they are actually placed somewhere else. Windows handles everything on the background.
So a photoscenery can be placed on drive E: while X-Plane thinks it still is placed in the Custom Scenery folder.

You can create this type of link with the command line, buit unfortunately this can be a bit complex. However, there is an excellent shell extension which makes it simple. You can find it here:

The webpage is long and in depth, so here is a short description how I made it work for Windows 10 (and 8.1):

      1. Download and installDownload
      2. After installation: test to see if it works… First select the folder with the actual scenery (on the other drive). In the example I used the Global Scenery folder of X-Plane, which I share with a test copy of X-Plane to save space:
      3. Then go the folder where X-Plane expects your scenery (Custom Scenery in most cases, here the X-Plane folder), right click and select Drop as.. JunctionExample3
      4. Now the Junction should be visible (with a chain symbol in the Icon):Example1
      5. That is it! NB: Junctions can be deleted like shortcuts without deleting the original files

If the chain is not visible, follow these instructions:


As you can see it involves editing the registry of Windows. The risk is very small, but if you are not comfortable doing this: DON’T! Of course you could export keys to have a backup, but this implies already some knowledge.

NB: the link should work even if the chain is not visible, it is just a reminder for you as user that the folder is actually in a different location.


AGtrees_test.for error in the X-Plane log file

Even with a new and fresh install of X-Plane there is an error in the log (log.txt in the root of the X-Plane directory): the AGtrees_test.for error.

Show solution to this error

The error is caused by some X-Plane definitions in the resource library that refer to this file, while it is missing (at least at the location that is referred to). Although it doesn’t cause any serious problems I find it annoying and it doesn’t help when scanning the log for real errors.

I found a simple solution: place the missing files (see download) in the folder X-Plane 10\Resources\default scenery\airport scenery. It adds a folder (\Custom objects\test) with two files: AGtrees_test.for file and treeset_e.png. That’s all……(no more errors… 🙂 )