Ok So I am new,Been reading the manual. But thought I would ask here while still reading.Tileproxy is wokring, I am using the bing server but. . . When looking on bing,it is higher detail then what is displayed in FSX. I have tried and tried toget it to display higher detail. Perhaps you could try to see if you have the sameproblem in the same area. Load up to KODO and let it load then, compare what you see there to bing map.Perhaps I am missing something.Thanks!Xendoshi

I think I know what the problem was, Still messing around with it.I think it was the color hack, but not sure. . . I incresed the LOD as well so it's taking a bit longer. . .

I think I know what the problem was, Still messing around with it.I think it was the color hack, but not sure. . . I incresed the LOD as well so it's taking a bit longer. . .

color hack is ONLY useful in areas that have old Black and White high resolution imagery; you shouldn't need it.If you go to KODO via Airnav.com and click the Bing map link you get the view at zoom 14... which IS the same as level 14/LOD12/10m resolution in TP. You can see the zoom that shows in the address window (www.bing.com/maps/?cp=31.921415|-102.387133&style=h&lvl=14&v=1)To get the same resolution with TP just setmax_lod=12I advise not bothering with the level mapping option; set the level min/max from 10-19 and just leave alone after that. All you really need to change in different areas is that max_lod value. Check areas for best resolution before you fly there and don't set the max lod any higher than the imagery that is available. The resolution setting is FSX is NOT critical; it doesn't affect what TP makes, only how it is displayed (I leave mine at 1m) . High resolution is only displayed by FSX in the relatively small area immediately below the aircraft position - from the cockpit you may not even be able to see the 1m resolution below you. The Scenery RANGE setting in FSX does control the range of the scenery made by TP. Making long-range scenery is slower because of the extra workload on the cpu. I typically make at medium range and enjoy afterward at long range or manually override to 5.5 radius.Before I commit to making 2m or 1m scenery in a new area, I frequently start with 10m (level 14/max_lod=12) to see what it 'feels' like. If I like what I see, then I raise the resolution to 2m or 1mLowering the max_lod value alone will NOT make currently existing scenery lower than it is; raising the max_lod WILL increase the resolution of the scenery tiles up to the new resolution.The scenery tiles that TP makes are equivalent (in coverage) to default scenery tiles in FSX, LOD13-size tiles - a nominal 1.2km per side. At medium scenery LOD you will get full coverage of level 15 scenery by flying a back-and-forth pattern at about 7km spacing. To get full coverage at level 16, the spacing has to be 3.5 km. At 1m resolution (level 17), you have to sweep at 1.5km intervals. Use the cache viewer utility to make sure that you are not missing imagery in your flying about. You must have imagery to cover an entire scenery tile or TP will use the next lower complete 'set' to make the tile. Should there be an actual missing jpg image from the server, there is no fix; the scenery tile from that spot will always be made at some lower resolution.When planning to cover a large area, it may be easiest to make a flightplan that can run on autopilot, reduce FSX settings and start TP AFTER FSX. You won't see the photoscenery like this but it will be made at faster speeds because the CPU load is less - Then restart TP before FSX and the completed scenery should be available and ready to enjoy.Loyd

Ok I got it to work good now, great detail but a week now a new problem is here. . .Tileproxy stops downloading tiles, so I have to refresh it to get it to work again.Can't figure out how to fix it. I have a quad core 2.8ghz or so 4 gig ram.Any Ideas?

I forgot to add I have WIn 7 64 ultimate.

I forgot to add I have WIn 7 64 ultimate.

When I was on XP, I had virtual memory (Pagefile) fixed at 4G. It would gradually fill over several hours and when it got to 4G, FSX would stop/lockup and I had to restart. After that I would restart when it was in the 2-3G range, just so I wouldn't forget and let it lock up.Here on W7, the Program Manager displays are different so I'm never sure just what I'm seeing. If you have a fixed size pagefile, you might change it to "let Windows manage" and see what happens. I'm NOT running TP in this install, however so I can only offer my thoughts about what I might check in the same situation.Loyd