GianXXIV

In fsx.CFG try removing this string: MipBias=6 Then report back please. If nothing happens then restore that string back.

And I've been referring to offline pre-cached files from the first post to learn a bit more about your machine behaviour and loading times and then troubleshoot. But since you don't need my help, I gladly step aside. Have a good Sunday.

If loading speed is slow at already-downloaded scenarios then a better internet connection won't obviously help. When you load locations whose tiles have already been downloaded, ProxyUser.exe, from what I understand, reads those tiles from the disk, then writes them into ProxyUser.exe memory allocation and then they're transferred to FSX.exe memory allocation. Furthermore, still in my understanding, .jpg to .bmp conversion happens only in the downloading phase which, apart from being pretty logic, is confirmed by the lack of ProxyUser.exe CPU usage in the already-downloaded environment (and in the "TileProxy Photoreal World" carpet are stored .bmp files only). Moreover, Internet isn't accessed by ProxyUser.exe. Personally, I don't have any problems with TileProxy at all, and my 40 seconds are acceptable to me. What storage drives are you using and how have you disposed OS, FSX and TileProxy? Besides, as above-mentioned, try to set AffinityMask=15.

Also, disable OS paging file since you've got plenty of memory.

When loading a scenery whose tiles have already been downloaded it takes to me around 40 seconds to load. How long does it take to you? Windows should be tweaked for FSX, did you do that? Also FSX needs an extensive tweaking. A good thing is to allocate the OS & FSX to one disk and TileProxy to another one. If the disk for OS & FSX is composed of a RAID0 array it would be better (If using an SSD, due to its behaviour, the OS should have its own SSD, FSX its own SSD or HDD and TileProxy its own SSD or HDD). Disabling unnecessary programs & windows services and indexing also helps (and keep TileProxy drive defragmented, unless you have it on an SSD in which case you mustn't). 1. Go here for W7 and FSX tweaks: http://www.simforums...topic29041.html 2. When done, this page can tweak your FSX configuration with a tailored calculation (fsx.CFG): http://www.venetubo.com/fsx.html 3. Then, backup the modified fsx.CFG and make this change below its section. Use notepad find function: ctrl+f: [JOBSCHEDULER] AffinityMask=15 Then report back please.

Loading? That has nothing to do with internet connection. EDIT: Sorry, I had in mind the already-downloaded scenery. First, you could try to load locations where tiles have already been downloaded to see if loading times are decent.

1. HyperThreading is even counterproductive for FSX; I have a 2600k @ 4.4 GHz and I get stuttering and lower framerates with HT on (temperature never exceeded 60°C, so it can't be CPU throttling). That's because FSX wasn't programmed for HT. 2. Interesting question, but I don't have the answer. 3. It all depends on graphics card horsepower and, specifically, amount of video memory. For instance, I've never monitored more than 500 MB of video memory with TileProxy (and I have almost everything maxed out at 1600x900, 8xS AA, 16x AF + ENB Series + REX + textures at 4096 pixels of resolution). If you have 1 GB or more of dedicated v-memory, no worries with the 1920x1200x32 resolution. Perhaps you need more video memory with the three-monitor setup. 4. As point #2.

That's not TileProxy dependent. Back up your current FSX.ini file, then edit it and put these strings under the relative sections (for fast PCs, quad core and quick storage - if you have HT, disable it): [Display] TextureMaxLoad=15 [MAIN] FIBER_FRAME_TIME_FRACTION=0 //default=0.33 [sCENERY] MAX_ASYNC_BATCHING_JOBS=3 [TERRAIN] SWAP_WAIT_TIMEOUT=2 [Graphics] HighMemFix=1 [JOBSCHEDULER] AffinityMask=15 [bufferPools] Usepools=0 PoolSize=0 RejectThreshold=98304 Consider these as Beta settings, as any system is different (even the same system is different after formatting). Recommended sites: http://www.simforums...topic29041.html http://www.venetubo.com/fsx.html

That sounds feasible. First, we need a reasonable number of participants to make the collection.