Since everything is working great, I think I'm going to skip the level mapping for now unless it does something amazing. As good as everything looks now, I can't imagine what level mapping would do to improve things, but obviously it does or it wouldn't be an option. I'm surprised I don't miss the autogen as much as I thought I would. I imagine it's because without it I get a huge boost in performance. Plus the autogen would cover up all the wonderful photoscenery I know get to see. :)If I wanted to run the level of detail radius on large and the mesh complexity at 100% (right now they are set on medium and 85%), do I have to change anything in the ProxyUser.ini file or do I simply have to adjust the sliders in FSX? I'd like to try it and see what happens. I looked through the .ini file, but couldn't see anything that refers to those two settings.

If I wanted to run the level of detail radius on large and the mesh complexity at 100% (right now they are set on medium and 85%), do I have to change anything in the ProxyUser.ini file or do I simply have to adjust the sliders in FSX? I'd like to try it and see what happens. I looked through the .ini file, but couldn't see anything that refers to those two settings.

No, you just adjust FSX to suit yourself. Tileproxy makes scenery to "meet the needs" of FSX - it's the 'servant', not the 'master'. It can only make scenery so fast though, and as you increase speed or scenery range you soon reach the point of it not being able to stay ahead of you. Also, FSX has to convert the scenery into displayable form for the screen. The Asterisks in the 'ovals' indicate scenery tiles that are ready for FSX. When the ovals start staying blank at the edges you're at Tileproxy's limit; when the resolution on-screen loses it's sharpness, you're at FSX's limit. An evening of flying into a new area at high resolution will create several gigabytes of scenery. It's difficult to grasp how fast photoscenery becomes simply massive but it's so impressive that's it's hard to stop wanting to see new places. Be sure and monitor how large the Tileproxy Photoreal world folder is getting. The 'flush scenery' utility in Tileproxy will delete it all - and you may not want to do that. Scenery is stored in folders that correspond to FSX's scenery folder structure and you can manually delete specific regions that get overly large without destroying many evenings worth of enjoyment.Baby steps. You can't grasp it all in one or two days, but you'll get there. Some time spent with the FSX Scenery and Terrain SDK will be advantageous.Loyd

Thanks for the info. So far I have been deleting scenery after every session, although I imagine that I should keep the files that download for my home area since I fly that most often. If the files TP needs already exist in cache, does TP skip downloading them again? If so, then I will definitely stop flushing the files from my area so that I save bandwidth usage. I need to call my internet provider and make sure I don't have any bandwidth restrictions before I go to crazy with this program.With regards to performance, I did up the sliders and mesh resolution back to the maximum. That introduced some bad stutters and performance loss. So what I did was set my affinity for TP to only use Core0 and set the affinity for FSX to my last 3 cores. Doing that eliminated the stutters altogether.

If the files TP needs already exist in cache, does TP skip downloading them again? If so, then I will definitely stop flushing the files from my area so that I save bandwidth usage.

Yes, TileProxy checks caches first, then seeks them on the 'net. If you fly a lot in the home area, definitely keep those tiles.Ready for a tweak? for the home area, I mean...cache-service1 or whatever is just a name for a cache that has to be matched in the ini with a detail entry to use it. Any name at all.Were it me, I'd:1. create a folder called my_KPITcache or something. This will be equivalent to servicecache3 but you'll only use it for around the home area.2. make a complete copy of the entry section you are currently using "service3", for instance.3. make the copy's header read [KPIT]4. entry inside reads: cache_folder=H:\my_KPITcache (or wherever you put it)5. adjust source entry above to select new section: source=KPIT vs (previous "source=service3")6. Fly only in the home area with those settings and KEEP the tiles you have.7. Switch source=(whatever you had before) when you go exploring somewhere elseI'd probably just use the comment markers and keep all the lines in one .ini file so as to not forget what I'm supposed to be using...#source=Service3 (ignored)source=KPIT ( used for flight)[KPIT]#------------ this for the home area ONLY---------cache_folder=H:\my_KPITcacheetc etc#---------- this is for everywhere else ------------[service3]no changes made here, just not used this time...easy enough?Tiles accumulate rapidly! To keep the single "service1", "Service3" caches from becoming impossibly large, I subdivide into regions:NewEngland is cacheNE, Florida is cacheSE, Seattle is cacheNW, Arizona/Colorado is cacheSW, Calif/Nev is cacheWC, northern Europe is cacheEUN, the Med is in cacheEUS, etc, etc. This way if I accidently delete a cache it won't be the whole world and defragging doesn't take a week to accomplish.Loyd

That's sounds easy enough to do even for a dummy like me. I will get right on that and thank you for the tip.I have found that Service3 has nice coverage area and so far has worked great everywhere i've gone. Service1 seems to be lakcing in quality overhead images in a lot of places I've tested so far and the ground images are horrible. Funny thing is, Service1 looks best for my home area so that is probably the one I will use for making my home area cache. For exploring, I think it's best to stick to Service3 based on my tests.