Well after messing about with this parameter and that parameter, and being amazed at the detail then dismayed cause I couldn't get a decent flight without it all blurring, it's finally all come together with 200 knots without blurring and long flights over pre-cached areas. Amazing.The only trouble is is that I cant put my finger on anything that I can say that did it. Hmmm and worse still I seem to have parameters now that would not work no matter what I did.An example. No matter how I ran it it wapped the kernel memory at 90+%. Always. So eventually I twigged onto the max_contexts parameter after browsing the manual once again and dropped it to 256. This immediately dropped this figure to 46% from 90+ and a dramatic drop in loading time although no real improvement in updating in flight.

Hey William, would you mind posting your FSX .cfg file and the TP .ini file for inspection? I am always interested to try out other peoples settings.... cheers, Mark

Sure Mark I'll post them and a screenie. After your reply in the other thread and I read the thread you directed me too and on the strength of that restored the fsx cfg to the defaults recommended. Perhaps that along with the released kernel memory swung the trick for me.diskless_mode=Offoffline_mode=Nomax_lod=16preload_min_lod=9preload_max_lod=17max_contexts=512water_mask=Onwater_blending=Onblend_distance=500.0blend_exponent=1.0alpha_min=0.2678alpha_max=0.7water_rgb=#004D5Awater_smoothing=Offwater_threshold=0.33cache_bytes_limit=102400000000cache_tiles_limit=0source=Service Example 1menu_sources="Service Example 1|Service Example 2|Service Example 3|Service Example 4"enable_hooking=Noenable_dx9hook=Noenable_movingmap=No

max_lod=16preload_min_lod=9preload_max_lod=17min_level=9max_level=19level_mapping=9,10,12,14,14,14,15,16,16,16,17 this works great

I don't understand your use of numbers here. Max lod=16 yet in level mapping you're no higher than 17 which is really 15.Then you have a max level of 19 using all ten rings yet you're only going to 17 detail, why not just have a max level of 17 and save a lot of unnecessary loading of the last 2 rings.What am I missing here?

Like I said it's a black art so I don't know the answer either, but they do work. These numbers allow me to fly around at a decent rate of knots and therefore represents the balance of quality and performance that satisfies me on my limited system. My computer wont let me run at higher resolutions than this if I want to say, fly at 150kts along the river Thames. I'm not into flying along and stopping every few mins to let the graphics catch up. I'll post a couple of screen shots so you can see the quality of graphic they represent which is IMO better than the numbers suggest.RegardsWilliam

Continuous flight at 150kts + no pauses, no waiting for graphics to load. Taken over the lake district with weather effects etc.

I don't understand your use of numbers here. Max lod=16 yet in level mapping you're no higher than 17 which is really 15.Then you have a max level of 19 using all ten rings yet you're only going to 17 detail, why not just have a max level of 17 and save a lot of unnecessary loading of the last 2 rings.What am I missing here?

This might be all wrong.max_lod=16.......... refers to the level of resolution displayed in the game.The two lines below represents the resolution of tiles downloaded from the service provider. So the number 9 to 17 makes sure the highest possible resolution tiles are downloaded. It does not mean a separate tile is downloaded for each level. The lower lower level tiles displayed in the game are rendered from the highest level tile available. (17 means it's 19 to the service provider)# Lowest LOD ring to automatically preload tiles for. Must not be lower than 8.preload_min_lod=9# Lowest LOD ring to automatically preload tiles for. Must not be higher than 17.preload_max_lod=17level_mapping=9,10,12,14,14,14,15,16,16,16,17.....This has ten levels to make to make for a smooth transition and displays the highest available resolution at the approriate distance from the aircraft but bear in mind that all the levels lower than 17 are derived from the level 17 tiles.This might all be wrong I'm trying to work whats going on and I might be completely off the mark here.regardsWilliam

Hey William, I have not got time for a detailed reply as I am going out, but i noticed that your max texture resolution in the FSX .cfg file was only 64. This is not good for quality. Also, and I dont mean this in a nasty way, your screenshots were not showing what I would call good results. I appreciate my PC may be more powerful, but take a look at this:Now thats crisp!!!!I think we can get it much better for you.Also Hardcore has it right as far as I know, regarding the relation between the various lod level figures. But I am no expert, pretty much as new to Tileproxy as you are, so I am not making pronouncements hhere....Incidentally, i have tried putting the LOD8 folder at position 1 in my scenery library and strangely, I did see improvements in spped of texture loading and tile processing. I have no idea why this should be. Ganna try and squeeze in some more tests , will carry this on tomorrow, cheeers, Mark

Two Screenshots one at 64 the other at 1024. As you can see there isn't any difference. These were shot by making a save and restarting FSX to make sure that the relevant parameter was being used. However in flight, the higher setting causes blurring whilst the lower one does not. I would speculate that at the higher setting the cpu is loaded up much more trying to render it to higher degree.