Using "Level Mapping" to increase the diameter of high resolution areas around your aircraft.

Before discussing Level Mapping techniques is best to make sure that users remember that the "max_lod=" setting in the upper half of the ProxyUser.ini file represents the Flight Simulator's "Level of Detail" (LOD) setting, (i.e. it's specified maximum resolution to be loaded) and is always 2 digits lower than the equivalent "max_level" entry in the "service entries" that represent the online map service's equivalent level.

Here's a basic chart to make that clearer:

max_lod=8 >   is equivalent to the "service example x" > min or max_level=10   which equals 304 meters per pixel
max_lod=9 >   is equivalent to the "service example x">   min or max_level=11  which equals 152 meters per pixel
max_lod=10 >  is equivalent to the "service example x">  min or max_level=12  which equals 76 meters per pixel
max_lod=11 >  is equivalent to the "service example x">   min or max_level=13  which equals 19 meters per pixel
max_lod=12 >  is equivalent to the "service example x">   min or max_level=14  which equals 9.5 meters per pixel
max_lod=13 >  is equivalent to the "service example x">   min or max_level=15  which equals 4.7 meters per pixel ( FS9 max resolution)
max_lod=14 >  is equivalent to the "service example x">   min or max_level=16  which equals 2.4 meters per pixel
max_lod=15 >  is equivalent to the "service example x">   min or max_level=17  which equals 1.1 meters per pixel (Default FSX resolution)
max_lod=16 >  is equivalent to the "service example x">   min or max_level=18  which equals 60cm per pixel (FSX High Resolution, slow!)
max_lod=17>  is equivalent to the "service example x">   min or max_level=19  which equals 30cm per pixel (FSX High Resolution, slower!)

Got that? Good. Now on to level mapping...

Tiles are loaded around your aircraft in concentric "rings" of decreasing resolution. The ProxyUser "level_mapping" entry is a feature that allows you to re-map any zoom level of the map tile service to another level. You can entirely skip certain zoom levels or you can substitute specific zoom levels for others. This parameter expects a comma separated list of numbers. The total number of values you have to specify MUST be equal the total number of allowed zoom levels (within the min_level and max_level range).

In the first example none of the default levels (9 thru 19) have been changed. Because no levels have been "re-mapped" the result would be the same as using no level mapping at all:


In the following example, level 9 to 11 display normally, whereas level 12 and 13 are substituted for zoom level 14. Levels 15 to 19 again display normally:


As you can see, there are a potential variety of "mapping" strategies you can try to your liking. Be cautious though, because increasing more than a few of the highest resolution levels to lower levels can kill performance as the number of tiles and their loading times increase exponentially. To turn off level mapping either remove the entry or comment it out with a "#" sign like so:


Note: Remember If you're limiting your max_lod resolution to the default FSX level of "max_lod=15" (1.1 pixels/meter) then TileProxy wont be loading levels 18 (60cm) and 19 ( 30cm) anyway... so don't fool with them because as you recall from the top of this section... "max_lod=15 equals "max_level=17" those levels are already inactive. Thus, you'll only want to substitute levels 9-17 because these are the currently active levels.

If your min to max levels have a different range like 5 thru 19, as in the "Service Example 3" default range of:


then you'll want to make sure you add the SAME number of levels to your level_mapping=" entry, like this:


Remember: The total number of values you specify in the "level_mapping=" entry MUST be equal the total number of allowed zoom levels (within the min_level and max_level range). Thus you must remember to SUBSTITUTE one level for another, and not ADD one!