- Category: Tileproxy
- Last Updated: Thursday, 06 October 2016 14:13
Installing Tileproxy for FSX under Windows 7, 8 and 10
1. Summary and Prerequisites
- Tileproxy download: http://sourceforge.net/projects/tileproxy/files/tileproxy/ (353.3 MB zip file Beta 8 November 2008)
- Driver Signature Enforcement Overrider : http://www.ngohq.com/?page=dseo (706KB exe file)
- A pre-configured proxyuser.ini file downloadable at the end of this article (will require tweaking)
- UAC (User Account Control) set to Never notify me
- Windows needs to run in Test Mode
- FSX folder requires write permission.
- Tileproxy cache best placed on separate partition or disk for faster performance and so as not to fragment the main drive. It may be useful to understand the cache further by looking at the full manual (see below). Note: never try defragmenting an SSD.
- Firewall and file scanning by antivirus/security programs needs setting so as not to block Tileproxy downloads or cause time outs due to scanning each tile downloaded.
- fsx.cfg in C:\Users\username\AppData\Roaming\Microsoft\FSX is overwritten when Tileproxy is installed. It is backed up during install and needs putting back to replace the fsx.cfg file that Tileproxy creates (make your own backup if you wish).
- The Tileproxy cache folder needs full control by the appropriate user. Probably best to give full control to user ‘EVERYONE’. Click here for details on how to do this.
- If you have photo scenery installed for particular areas then you will see this rather than the Tileproxy data. To use the Tileproxy data you will need to deactivate the photo scenery.
- WORLD_LOD8 needs to be below the other Tileproxy areas. e.g. in your Scenery Library Tileproxy WORLD_000 may be Priority 90 therefore WORLD_LOD8 needs to be a number greater than 90.
- Tileproxy can be uninstalled in the usual manner through ‘Programs and Features’. Note: The uninstall does not seem to be compatible with Windows 10. Run it and if it fails to complete then delete everything manually and use a registry cleaner (e..g. CCleaner) to 'tidy up'.
- This guide is to assist with the installation of Tileproxy and to get you up and running. There is a lot more to it you want to delve further! For the full manual see: http://www.edtruthan.com/tileproxy/manual.htm
- This can be carried out before following the guide which is the same as the install process for Windows 7. Thanks to Darrell for this update March 2015.
Subsequent to Darrell Scott helping myself and others with the install process we have put this guide together. Do contact us if you have suggestions or questions.
2. Installing on Windows 8 and 10 (this step required for Windows 8 and 10 only).
The way to setup TileProxy on Windows 8 and 10 is the same as for windows 7 apart from one additional initial step. This involves running a command from the Command Prompt. When installing or running any applications, it is best to right click and run as administrator.
- In Charms got to Search
- Type cmd which will find the Command Prompt
- Right click and choose run as administrator
In the command prompt window type the following (note the spaces):
bcdedit -set TESTSIGNING ON
Press enter and it should return with the message The operation completed successfully. You can then close the command prompt and reboot.
Upon rebooting you should see the Windows Test Mode logo in the lower right corner. From here everything is the same as Windows 7 including using the dseo (Driver signature Over rider) program as usual but only after having performed the above step.
However the command may fail and will return the error message as below.
If this is the case you will need to Disable Secure Boot. This is accomplished within the UEFI (the up to date equivalent to the BIOS) and is beyond the scope of this tutorial. The subject is covered in this excellent video on Youtube.
Having disabled Secure Boot you will then be able to run the bcdedit command and continue with the install.
3. Install Tileproxy
Extract TileproxyInstaller.exe from the archive downloaded from Sourceforge and run the executable as administrator. Accept license etc.
The first screen is Choose Components.
All check boxes can remain ticked. You may however like to untick the C source code… and Display User Manual… check boxes as this is not necessary.
Next screen is installation location (ensure write permission is granted for this folder).
This can be anywhere but the default FSX folder is fine.
Next screen is install locations options page. Note carefully the information about the locations – do not use the FSX folder. The faster and larger the drive the better as there can be many thousands of files.
Notes on Windows 10 Installation Options
When installing on Windows 10 and wanting to place the cache on another drive (internal) I had success with the following using Virtual Earth:
- The drive on to which I wanted to place the cache was E:
- Therefore I put E:\ for both options in the above image.
- This created just one folder E:\TileProxy Photoreal World
- Then I created a folder E:\cache.virtualearth
Next screen is install options for terrain resolution which can be tweaked later if desired. Try 60 cm/pixel.
Next screen is install options for terrain detail radius, which can be tweaked later if desired.
Next screen is water masks
Next screen is Install Options page
Untick all but Optimize for high speed
Next screen is a Windows message box.
Ignore this screen for now. It will be dealt with later.
Installation will complete and the user manual will open which you can shut down. The ProxyUser.ini file will also open in your Notepad program and you can also close this (we will deal with it later). You should now be left with the Completing the Tileproxy Project for Microsoft FSX/2004/2002 Setup window and you can click Finish.
4. Update ProxyUser.ini file
In this step you need to replace the ProxyUser.ini file with the sample pre-configured ini file below. If you used the default location this will be in:
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\TileProxy
Having replaced the file with the preconfigured one, it can now be tweaked as necessary. Open the ini file in a text editor and look for the service sections.
Sample Pre-Configured tileproxy.ini file
# Start a line with # to comment it out.
# Turn your text editor's Word Wrapping OFF for editing this document.
# Read the manual for help with configuration. Do not contact the
# author about the configuration for particular services. Thank you.
# Enable or disable worldwide photographic scenery coverage (Yes/True/On to enable)
# Write a logfile to disk. In recommend to only turn this on for debugging purposes.
# When using FSX RTM or FS 2004, the logfile may grow VERY fast and affect performance.
# If you have concerns about possible copyright violations by caching JPEG and BMP tiles
# on your hard drive, this switch is the solution. By enabling diskless mode, Tileproxy
# will not store a single tile on your hard drive. Expect higher network usage though.
# Note that offline mode will depend on tiles being available in the cache.
# Offline Mode - No network access will occur (Yes/True/On to enable)
# Resolution limiter: 17 = 30cm/pixel, 16 = 60cm/pixel, 15 = 1.1m/pixel, 14 = 2.3m/pixel, 13 = 4.75m/pixel
# Lower resolutions load faster, but are visually less appealing. The 30cm resolution may only be feasible
# if you have at least 2GB of system memory.
# The following two settings allow you to tune Tileproxy to not preload specific LOD levels. This can
# be used in conjunction with third party scenery products like "FS Altitude" that provides data only
# up to a specific resolution. If you place this scenery higher than Tileproxy's world folders in the
# scenery library then it will have precedence over Tileproxy for the specific LOD levels that it
# contains. You can then instruct Tileproxy to not preload these low resolution LOD circles because
# they are not needed anyway.
# Lowest LOD ring to automatically preload tiles for. Must not be lower than 8.
# Lowest LOD ring to automatically preload tiles for. Must not be higher than 17.
# The maximum number of tile contexts that Tileproxy will send to the filter driver. A context
# is essentially a very fast buffer for graphics data sitting in kernel memory that delivers
# data right into FSX. Each tile context can hold an entire LOD 8...15 tile. Higher values
# mean more use of your precious kernel memory though. The maximum number is 512. Lower if
# you run out of RAM during flight and the PC starts to use the paging file a lot.
# Generate Water Mask. This brings back shader-rendered water and allows
# for the use of planes with floats (Goose, Beaver, etc...). If you turn this
# option off, you get the Tileproxy behavior of Beta 5 and earlier versions.
# Recommendation: FSX users: Use water_blending=on, water_smoothing=off
# to get soft land/water transitions
# FS9 users: Use water_blending=off, water_smoothing=on
# to get hard land/water transitions which
# Tileproxy tries to match pixel-exact against coast-lines
# Combining water_smoothing and water_blending is discouraged.
# It's slow and gives weird results.
# Use blending techniques to create a soft land/water transition with some
# transparency effect near the shoreline. Compatible with FSX only.
# The distance in meters that you want land/water blending to extend from the
# shore line. Larger values require more processing. Large values are now possible,
# useful values are up to 2000 meters. Very high values may be detrimental to water
# mask resolution. Loading speed however remains mostly unaffected by this setting.
# The rate at which terrain is blended into the water color. 1.0 means a linear
# blending, values > 1.0 blend faster. Values < 1.0 blend slower. This works
# similarly to a Gamma Curve. An exponent of 2 gives a quadratic blend function,
# an exponent of 0.5 results in a square root behavior.
# The minimal and maximal transparency of the water. The lower you choose the min value,
# the more reflective the deep water will be. The higher the max value is chosen, the less
# reflective the water will be directly at the shore line. The reflectiveness transitions
# linearly from max to min throughout the distance given by blend_distance from the shore.
# Allowed values are between 0 and 1, and alpha_min should be smaller than alpha_max or
# things may look weird.
# The following alpha_min values will not give you any dithering artifacts on all-water tiles,
# so the use of these is recommended. It is multiples of 16/239 (rounded up slighty)
# 0.0700, 0.1339, 0.2009, 0.2678, 0.3348, 0.4017, 0.4687
# 0.5356, 0.6026, 0.6695, 0.7365, 0.8034, 0.8703, 0.9373
# The water color in hexadecimal RGB notation. Prefix with #. This should be blue
# or greenish blue or some shades of brown, depending on your preference.
# Values of #000000 are discouraged when using water blending - it will result
# in weird behavior at the shorelines.
# Try to smooth land/water boundaries by trying to match the water mask to the image content.
# This is a a somewhat experimental algorithm.
# The decision threshold for water/land when water_smoothing is enabled. 0 means everything
# will be turned to land, 1 means everything turns to water. Chose some value inbetween.
# Maximum number of bytes allocated to BMP graphics tiles in RAM at any time (0 for unlimited)
# The value below states 100 MB.
# Maximum number of BMP tiles to cache in RAM at any time (0 for no limit).
# The currently active service is configured here. Only ONE active source please.
# The other source statements should be commented out.
source=Service Virtual Earth
#source=Service Example 1
#source=Service Example 3
#source=Service Example 4
# The sources you want to be able to switch from the GUI menu.
# Separate the list entries with | and enclose in quotes. Make sure the
# names specified here are valid services which are defined below.
# You may want to rename the services according to your preference,
# but make sure you replace all occurences of the strings.
menu_sources="Service Virtual Earth"
# Experimental API Hooking section. Disable if you see strange crashes and effects.
# Currently we only have the DirectX 9 hook. More hooks are planned.
# The DirectX 9 hook enables the moving map overlay. More features are planned.
# A flag whether to show the moving map overlay initially or not.
# Dimensions and overlay colors of the moving map. Positions are percentages of the screen.
# Width and Height refer to the full 512x512 pixel texture used for the map. To get a round
# map circle, the ratio of width and height should match your screen's aspect ratio (e.g. 4:3)
# Radius is given in the map texture's pixels where one pixel represents a LOD 15 tile. A
# radius of 0 disables the round stencil and shows the entire 512x512 texture. Color is given
# in a hexadecimal ARGB notation.
# Here begin the service specific configurations
# This is new when you specify captcha_module
# On encountering HTTP 302 redirects the captcha module will send Internet Explorer's cookies
# stored for the specified service domain to the web server. It will also display whatever web
# page the service redirects you to. This could be a page requiring you to enter a so-called
# captcha. After entering the captcha correctly, the resulting session cookie will be stored as
# a permanent cookie (expiration 1 day) in your IE Cookies folder and sent to the service on
# subsequent requests. You will then be able to use the service as long as you wish, given that
# you correctly enter the captcha dialog which may nag you once every 20 minutes or so.
# Explaining the captcha_config arguments:
# cookiedomain from captcha_config specifies the domain name for which cookies are stored.
# This might be the service name plus a top level domain like ".com"
# cookieurl specifies a HTTP url from which an identifying cookie will be retrieved first, if
# no existing identifying cookie is found. This may be required sometimes to make the captcha
# dialog appear in the first place. This could be the service's front page URL (e.g. a search
[Service Virtual Earth]
module_config="conn=20|rate=2.0|verbose=0|server=http://a*.ortho.tiles.virtualearth.net|path=/tiles/a%s.jpeg?g=%v|quad=0123|balance=0123|useragent=Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727;.NET CLR 3.0.04506; .NET CLR 1.1.4322)"
#level_mapping=9,10,11,12,14,14,15,16,17,18,19 more radius HQ (13->14)
level_mapping=9,10,11,14,14,14,15,16,17,18,19 even more radius in HQ (12,13->14)
Use # to comment out the services not required. Only one service can be active at a time. Note that the Google service is no longer available.
The cache_folder path needs setting to what was chosen during installation
map_version can be checked for versions updates at http://aviation.allanville.com/tileproxy/
5. Replace fsx.cfg
In Windows Explorer go to %AppData% or use Windows search for %AppData% and go to:
Replace the fsx.cfg file with the original that you backed up at the start or the backup that Tileproxy created.
6. Driver Signature Enforcement
Run dseo13be.exe (as administrator) and accept the software license. From the options screen of bullet points select Enable Test Mode and click Next.
A message will appear stating a computer restart is required to apply this change.
DO NOT restart at this stage. Click OK and carry on.
Next select Sign a System File and click Next. In the Insert Filename field, put
and click OK.
Next select Exit and click OK. Restart Windows which should now be in Test Mode. The Test Mode message should appear in the lower right portion of the screen. NOTE: if you have run the bcdedit -set TESTSIGNING ON command as per section 2 above then the Test Mode logo should already be there.
7. Turn Off UAC (User Account Control)
Set UAC to Never notify
8. Firewall and Virus Software
Virus software and firewall software should be set so as not to block any Tileproxy processes.
e.g. if there is real time file protection that scans every tile being downloaded the system can time out or may not be able to write to the Tileproxy folders. In this case exclude the folders from the scanning process including the cache folder if on another drive. e.g.
C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Tileproxy\*.*
T:\TileProxy Photoreal World\*.*
Note the TileProxy Photoreal World folder must never be renamed.
9. Run Tileproxy before Starting FSX
N.B. for Windows 8 the usual shortcut to TileProxy (which is a .bat file) does not work. Instead find the file in the TileProxy folder named Proxuser.exe and run that instead (Right click and run as Administrator). You obviously could create a shortcut to it on the Desktop too (Right Click and Send to Desktop).
If Tileproxy is not started first, FSX will start as normal.
With Tileproxy running the DOS window should appear as per the screen shot, stopping at:
TileProxy is ready for takeoff.
Now run FSX
Notes on running/starting Tileproxy
NOTE ensure the cache folders, and the Tileproxy folder (in the FSX folder by default) has full write permissions and that any firewall/anti-virus and malware software is not blocking any of these locations.
When running Tileproxy under Windows 8 or Windows 10 do not use the batch file that Tileproxy installs for you. Instead change this batch file to run ProxyUser.exe which is in ...\Microsoft Games\Microsoft Flight Simulator X\Tileproxy remembering to Run as administrator. Failing to do this can lead to the TP DOS window momentarily flashing on the screen and disappearing.
N.B. when FSX terrain data is loading with Tileproxy active, the progress bar will slow down around the 30% to 50% point. This is normal.
The DOS window now changes to ovals being populated with stars. The first oval may remain blank which is correct as it is WORLD_LOD8 which is already part of FSX Scenery.
DOS Window not showing ovals correctly
If the ovals do not show correctly formed, then try setting the layout as per the image below.
This makes no difference to the performance of Tileproxy but is easier to look at.
10. FSX Scenery
In the FSX Scenery Library Settings all the WORLD_XXX entries must be at the top and the WORLD_LOD8 must be below them.
Tileproxy installation ends here.
Select the folder you want to set or modify permissions for. Right click the folder and click Properties in the dropdown menu. In the popup window select the Security tab and click Edit…
In the next popup window click Add…
In the Select Users or Groups popup type everyone in the empty field and click Check Names.
Everyone is a standard object name so should appear underlined. Click OK.
This returns to the Permissions popup where you can select Everyone and put a tick in the Allow check box against Full control