Tileproxy - FSX and FSX-SE Together

Installing a Second Copy of Tileproxy

When running FSX boxed (FSX) and FSX Steam (FSX-SE) on the same computer it is necessary to install a second copy of Tileproxy for the Steam edition. Installing TP for FSX-SE, is exactly the same as installing it for FSX. Do not miss out any steps. When setting the cache folder it makes sense to use the same location as that used by the boxed version thus saving disk space.
 
Having installed the second copy for FSX-SE these will be the resultant folders (some relevant files shown in brackets):
 
Note: All folders referred to are for a default install. Adjust accordingly if you installed to different folders.

FSX boxed

  • C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ (fsx.exe)
  • C:\ProgramData\Microsoft\FSX\ (Scenery.cfg)
  • C:\Users\Username\AppData\Roaming\Microsoft\FSX (fsx.cfg)
  • C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Tileproxy\ (ProxyUser.exe)

FSX-SE

  • C:\Program Files (x86)\Steam\steamapps\common\FSX\ (fsx.exe)
  • C:\ProgramData\Microsoft\FSX-SE\ (Scenery.cfg )
  • C:\Users\Username\AppData\Roaming\Microsoft\FSX-SE (fsx.cfg)
  • C:\Program Files (x86)\Steam\steamapps\common\FSX\ Tileproxy\ (ProxyUser.exe)

During the install of TP for FSX-SE the Scenery.cfg file is built but there are no entries relating to Tileproxy WORLD entries as the installation is fooled in to thinking they are present as it reads the boxed version Scenery.cfg. All the WORLD entries therefore need copying from the boxed version to the Steam version.

Note: WORLD_LOD8 must also be copied and must be below all other WORLD entries. 


Duplicate Layer NumbersHaving copied the WORLD entries to the FSX-SE scenery.cfg file they should be checked to ensure there are no conflicts with layer settings i.e. there are no duplicate priorities.

The Open Source Scenery Config Editor can be used to check for errors.
 
If the SCE finds any duplicates there will be a warning, Issues found. Click No to automatically correct the errors. Clicking Yes loads the scenery.cfg data in to the SCtext editor where changes can be entered manually.
 
When Tileproxy is run the ovals should start populating with data. If they do not and the DOS window remains open, it will be necessary to install SimConnect.
 

No ovals showing in DOS window

Tileproxy no ovals

It may happen that no ovals show but that all that is displayed is:

<0> - Done!

In this case wait until FSX loads and Tileproxy may be working correctly. Allow FS to finish loading and check to see if the scenery has loaded successfully.

 
SimConnect is only required for FSX-SE.There are five files to install: Three are installation packages (.msi) and  SimConnect.cfg and SimConnect.xml  (note names are case sensitive).
 
First run the three .msi installers in these folders:
 
C:\Program Files (x86)\Steam\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-RTM\SimConnect.msi
 
C:\Program Files (x86)\Steam\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-SP1\SimConnect.msi
 
C:\Program Files (x86)\Steam\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-XPACK\SimConnect.msi
 
Second place the SimConnect.cfg and SimConnect.xml files in the following folders. These files are in the downloadable zip file below.
 
C:\Users\Username\Documents\SimConnect.cfg
 
C:\Users\Username\AppData\Roaming\Microsoft\FSX-SE\SimConnect.xml
 

SimConnect.xml

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="SimConnect" version="1,0">
<Descr>SimConnect Server Configuration</Descr>
<Filename>SimConnect.xml</Filename>
<Disabled>False</Disabled>
<!-- Example Global (remote) Pipe Server Configuration-->
<SimConnect.Comm>
<Disabled>True</Disabled>
<Protocol>Pipe</Protocol>
<Scope>global</Scope>
<MaxClients>64</MaxClients>
<Port>4506</Port>
</SimConnect.Comm>
<!-- Example Global (remote) IPv6 Server Configuration-->
<SimConnect.Comm>
<Disabled>True</Disabled>
<Protocol>IPv6</Protocol>
<Scope>global</Scope>
<MaxClients>64</MaxClients>
<Address>::</Address>
<Port>REPLACE_WITH_PORT_NUMBER</Port>
</SimConnect.Comm>
<!-- Example Global (remote) IPv4 Server Configuration-->
<SimConnect.Comm>
<Disabled>False</Disabled>
<Protocol>IPv4</Protocol>
<Scope>global</Scope>
<MaxClients>64</MaxClients>
<Address>127.0.0.1</Address>
<Port>4506</Port>
</SimConnect.Comm>
<!-- Example Local Pipe Server Configuration-->
<SimConnect.Comm>
<Disabled>False</Disabled>
<Protocol>Pipe</Protocol>
<Scope>local</Scope>
<MaxClients>64</MaxClients>
<Port>4600</Port>
</SimConnect.Comm>
<!-- Example Local IPv6 Server Configuration-->
<SimConnect.Comm>
<Disabled>True</Disabled>
<Protocol>IPv6</Protocol>
<Scope>local</Scope>
<MaxClients>64</MaxClients>
<Address>::1</Address>
<Port>REPLACE_WITH_PORT_NUMBER</Port>
</SimConnect.Comm>
<!-- Example Local IPv4 Server Configuration-->
<SimConnect.Comm>
<Disabled>False</Disabled>
<Protocol>IPv4</Protocol>
<Scope>local</Scope>
<MaxClients>64</MaxClients>
<Address>127.0.0.1</Address>
<Port>4600</Port>
</SimConnect.Comm>
</SimBase.Document>

SimConnect.cfg

Protocol=IPv4
Address=127.0.0.1
Port=4506
MaxReceiveSize=4100
DisableNagle=0

 RELE0005

 

Attachments:
FileDescriptionFile size
Download this file (SimConnect.zip)SimConnect filescfg and xml0.7 kB