I only have one hard drive so I realize I might be a bit limited, but is it true that if I take my time online gathering tiles, in offline mode they'll load a lot faster? If so, how would I set this up, besides just turning it on? How fast could they load? should I switch to a lower resolution for jet flights? Will GA's be able to handle 1m?

I only have one hard drive so I realize I might be a bit limited, but is it true that if I take my time online gathering tiles, in offline mode they'll load a lot faster? If so, how would I set this up, besides just turning it on? How fast could they load? should I switch to a lower resolution for jet flights? Will GA's be able to handle 1m?

I find that TILEPROXY is not the most limiting factor; my hardware and FSX itself are.With FSX, "more is better". Good performance is a combination of CPU speed, speed of data flow, memory speed, HDD access time, Video board clock, video memory speed etc.The limitation of a single HDD is that you have to constantly jump around the HDD to read and write information, The OS has got to access it, FSX has to access it, and Tileproxy has to access it. TileProxy has to store the downloaded imagery in the caches folders and make .bmp scenery tiles to store in another location in the World scenery folder and re-access them as FSX needs to display those tiles. A Defrag program that allows YOU to move related files into contiguous blocks is an asset and reduces HDD 'seek time'. Ultimate Defrag is what I have.A lot of scenery is held in RAM and you can control this somewhat:cache_bytes_limit=800000000cache_tiles_limit=150000The individual scenery tiles (approx 1.2km square EACH) that are made range in size from around 2k (initially) for the most distant stuff on the horizon to 22Mb at 30cm resolution. Scenery tiles KEEP the highest resolution made so even when you fly away from them they are still the same file size and they have to be accessed as such even as you display them in lower and lower resolution as they get further away. Because of these types of 'limitations', I generally fly with a 2m maximum resolution (max_lod=14) and reserve 1m scenery to a few small areas.As far as the loading time: once the image tiles are initial downloaded they are accessed from the HDD and not from the internet. Scenery tiles are somewhat similar but with this important difference: they are constantly being accessed and 'enhanced' with higher resolution content as you get closer to them, up to the lod_max limit you define; after that they don't change any more. When you start a flight at a new location, the distant low-res tiles (lod8) from horizon to horizon are made first, then the central-most are enhanced to lod9, then the central portion of those are enhanced to lod10 etc. Each 'layer' of increasing resolution is smaller until you reach the lod_max which is the smallest, highest res area centered on the aircraft. Kinda like what happens when you spray-paint something; the highest density is the center and as you keep moving the center of the spray (flying) you increase the density wherever you spray (fly) until everything is covered completely (lod_max)Modest computer systems will best be served by flying slower, with scenery radius medium and limiting resolution to 2.4m (max_lod=14). From 2000'-3000' above ground level this is pretty good. If you fly from the VC, you wouldn't be looking at the higher resolution scenery directly under you most of the time anyway.1m and GA: if that means mostly doing circuits in a very limited area around a single airport, I think 1m might be quite usable. For cross-country flights, it might require frequent pauses to allow scenery to build, even after the scenery was already made - the higher the detail, the lower the performance.Jets: as FSX moves 'through' scenery, it 'recalculates' each time it crosses a scenery boundary. the faster you fly, the more frequently it has to 'start over'. Jets move faster than FSX can rebuild the scenery so you end up flying into increasingly blurry texture. This is default also, not just TileProxy. Jets, to me, means 30000' and if I do that, I usually limit resolution to 20m (lod_max=11) and reduce visibility range to 30-40nm.performance does improve a bit as you get an area covered and TP doesn't have to download or build scenery. If you have a particular ROUTE you'd like to have, you can start TP AFTER FSX, and the scenery will be more easily built by TP even though you don't see it on this 'pass'. After you restart both (with TP first) you will find most of the scenery already waiting for you and it does fly a little smoother. When you start running quad-cores at 4+GHz and scenery from SSD's then you can get pretty good 1m performance in jets but that is NOT YET for me...20m res / 40nm vis / 16000'. Coast of Portugal -this is a long way from 'great' but I like it better than the repetitive default tiles.Fully 'fleshed out' 2m over Wales, UK.Loyd