longbreak754

WRT to .dll file - The .18000 seems to be the one that works for most people. Try it and test. If it doesn't work delete is and load the other one........

Something you can do when a freeze happens is to open task manger/resource monitor and see if a 3rd party app that you are not aware of is trying to do something in the background - for example trying to connect to the internet to update.

Walter,

Have you tried the tool I suggested. When your first install it, it reads the scenery.cfg file and creates a list of what it finds there. It will then highlight problem areas.

Another option to try, if you have not done so, is to simply delete (or rename) the current scenery.cfg file. When the sim is started it will create a new one based on what it finds.

Get the following freeware tool Scenery Config Editor (found at https://sourceforge.net/projects/fs-sceditor/).

Its a great tool that works for both FS2004 and FSX and can help you identify problem areas. Take time to read the included readme file as it gives some great tips. It also allows you to activate/disable scenery from outside of the sim - next time you start the sim it automatically updates the sim scenery database. It even has an option to do a 'batch' update of multiple scenery folders located within a single higher folder - i.e. if your scenery setup is based on a series of folders under a root folder - say, for example, something like C:\Addon Scenery\UK airports and C:\Addon Scenery\USA airports. you can use the tool to individually activate the UK or USA folders or you can tell it to activate everything under Addon Scenery. It will read both UK and USA folders and they will be activated as separate folders in the priority list.

Firstly, I an not sure from your post if you are a aware of the location that the .xml file is stored so here are the details - In FSX SP2, the exe.xml file will be located in C:\Users\Appdata\Roaming\Microsoft\FSX\ - along with other default FSX files such as the FSX.cfg file. Also note that there may be a file called dll.xml located here - more of which later.

I don't have FSX-SE but my understanding is that if you have both FSX and FSX-SE installed the SE files will be installed in the same location but under a different folder name - ie at C:\Users\Appdata\Roaming\Microsoft\FSX-SE. If there are no similair default entries there then they may well be buried in a steam specific directory, most commonly found at C:\ProgramFiles(x86)\steam\steamapps\common\.

A simple solution might be to install into FSX SP2 again - this will give you a copy of the .xml file. Then do a manual install into FSX-SE, copy the .xml from SP2 to SE and then edit it to reflect the SE location. It is worth noting that when you run the auto-installer it does specifically ask if you want to create an .exe.xml file - the box is unchecked by default so must be checked. Also, once the install is complete you can view the details of where it has installed items - so that can give you a pointer as to where it has created the .xml file.

The .xml file can be edited in notepad. If there is no .xml present you can create one by simply creating a new text document and naming it exe.xml. This is what the contents of the exe.xml should look like:

Launch

EXE.XML

False

False

False

False

AICarriers

D:\Addon Scenery\AI Shipping\AICarriersV2\aicarriers.exe

-nogui

In the example the items in BLACK are the basic file commands and should be present only once. The actual commands that are required to allow AICarriers (or any other addon that requires use of a .exe.xml type file) to work are in BLUE/RED and there can be multiple entries for each individual add-on. The lines in blue are common to most addons - those in red are the specific to the addon. The entry is what is displayed in the Add-on menu and the entry is the same as the location that the main AIcarriers folder and .exe file are located.

WRT the dll.xml file – if you have installed any other addons, for example the FSX SDK package, FSUIPC and other (mainly payware) addons, it may already be there. Basicially, the dll.xml is another name for (and does the same thing as the exe.xml does) and is the more commonly accepted file name used by developers. The contents of the dll.xml is exactly the same as those in the exe.xml. If one is present in FSX SP2 or FSX-SE you could simply cut and paste the BLUE/RED lines into the dll.xml file.

Bob,

RE the Error 1607 report: Look at the following link. I helped a friend who could not install a piece of software (not FSX but a financial product) with the same error and the first option in the link fixed the problem:

https://support.microsoft.com/en-us/kb/910816

RE DX issues - simply run the built-in DirectX Diagnostic Tool by clicking the Start button , typing dxdiag in the Search box, and then pressing ENTER. This will cgeck your DX install, which on W10 will be DX12 (note new versions of DX are backward compatible with older versions), and highlight any issues.