Hi guys,So I've installed FSX as per Nicks guide and flying with no adds at the moment trying to tune my system before adding more complexity.I have the sliders setup as per Nicks recommendations and find I get good smooth flight and can easily acheive 24-30fps when locked at that within FSX over Seattle in the F18.What I'm seeing though are occasional "flashing" texture tiles.....little parts of the scenery which flash to white and then are redrawn as quickly as the dissappear. Sometimes I can go without seeing any for 10-15 seconds and I might then see a few in a couple of seconds....there doesn't seem to be any pattern to it.I also get the clouds doing the same thing except they seem to dissappear completely for a split second and then get redrawn.I have tried turning off the limiter, overclocking the CPU and I've used Bojetes tool to configure my .cfg all to no avail. I've now let FSX rewrite the .cfg and it's stlll exactly the same.Has anyone ever noticed similar behaviour or know what could be causing it? I run a factory OC GTX260 896MB, i7 860 and 4GB 6-8-6-24 at 1600. Does this sound like some kind of graphics corruption? Like I say, OC the CPU to 3.8 had no discernable effect. I did think it may be to do with flying low and fast over dense scenery but even when I slow to 200kts (or indeed when I first rotate from KSEA) I still see the occasional flashing tile.Any help, advice or suggestions would be very much appreciated as I'm going mad trying to tie this down and it's really spoiling what is otherwise a smooth flying experience!

the occasional flashing tile.

Hi,Can you tell me what the TextureMaxLoad, WATER_EFFECTS and SWAP_WAIT_TIMEOUT values are in your fsx.cfg? Do not confuse TextureMaxLoad with TEXTURE_MAX_LOAD they are not the same.

Have you ever heard about a guy named *******?Or his alias: Bojote!Have a look here:http://forum.avsim.n...g-tool-for-fsx/The white flashes - to my limited knowledge - is something about textures not being read fast enough, but if you take the time to study the above thread, you will know it...Good luck... Edit: Bojote, you´re fast! Don´t know how to delete this post, so lets keep it, and thanks for helping us all, Bojote..:(

Yep, this is usually a sign of over taxing the video cardYou may be able to tune it out using *******' tweaks, but usually you either have to accept the problem or turn down some of the settings a little.Reducing the fps via theinternal or external limiter may help.IAN

Hi,Can you tell me what the TextureMaxLoad, WATER_EFFECTS and SWAP_WAIT_TIMEOUT values are in your fsx.cfg? Do not confuse TextureMaxLoad with TEXTURE_MAX_LOAD they are not the same.

Hi Bojote,Unfortunately I'm out of the house at present but will be sure to get the information to you tomorrow! If anyone knows what's likely to be causing this I'm sure you do!Ian, PFL....thanks for your responses. Yes, I too think it's something to do with the textures either not being read fast enough or not at all. I'm thinking of investing in a new gtx570 but would hate to make that expenditure only to find it's something else causing this in my system!Just seems strange how it occurs only at certain times and in some places in particular (rotating from runway at ksea, coasting out over Seattle harbour are two that spring to mind)I should add I am using a vrap 600 as my dedicated fsx drive so have kind of ruled out any drive bottlenecks.

Hi Bojote,Unfortunately I'm out of the house at present but will be sure to get the information to you tomorrow! If anyone knows what's likely to be causing this I'm sure you do!Ian, PFL....thanks for your responses. Yes, I too think it's something to do with the textures either not being read fast enough or not at all. I'm thinking of investing in a new gtx570 but would hate to make that expenditure only to find it's something else causing this in my system!Just seems strange how it occurs only at certain times and in some places in particular (rotating from runway at ksea, coasting out over Seattle harbour are two that spring to mind)I should add I am using a vrap 600 as my dedicated fsx drive so have kind of ruled out any drive bottlenecks.

KSEA, especially combined with PNW scenery is just very hard on "Any" system...Try flying over Hawaii for a nice change :(

I'm really starting to think the 1st tweak to have is 4Ghz for your rig or forget it. Then there's -you have to be a computer guru- to put a lot of this stuff in, like the external frame rate limiter, well i still can't get it to work,then this tweak http://www.venetubo.com/fsx.html well can't get that going either cause how do you clip it on the clip board? very frustrating this can be ----Louis

Try flying over Hawaii for a nice change :(

Bert,You don't want to see what my Honolulu looks like when I have everything going, it's not a pretty sight! I've got a stock i7 930 and it makes whimpering noises and cries for it's Momma until I get away from Honolulu...

Hi,Can you tell me what the TextureMaxLoad, WATER_EFFECTS and SWAP_WAIT_TIMEOUT values are in your fsx.cfg? Do not confuse TextureMaxLoad with TEXTURE_MAX_LOAD they are not the same.

Hi again Bojote,Having run your optimisation tool I have the following in my .cfg fileTextureMaxLoad=12Water_Effects = 4Swap_Wait_Timeout=2Hope these provide some insight?

TextureMaxLoad=12Water_Effects = 4Swap_Wait_Timeout=2Hope these provide some insight?

Sure, try again with this values:TextureMaxLoad=30Water_Effects = 6You should see no more texture flashes

Sure, try again with this values:TextureMaxLoad=30Water_Effects = 6You should see no more texture flashes

Sorry Bojote but they're still there.....any other ideas? please! :(

Sorry Bojote but they're still there.....any other ideas? please! :(

Ok, leave WATER_EFFECTS=6 and TextureMaxLoad=30 and increase SWAP_WAIT_TIMEOUT to 20, then 30, and finally 60. Let me know if increasing it changes anything.

Ok, leave WATER_EFFECTS=6 and TextureMaxLoad=30 and increase SWAP_WAIT_TIMEOUT to 20, then 30, and finally 60. Let me know if increasing it changes anything.

Hi Bojote,I increased Swap_Wait_Timemout to 20 and that cured the flashing white tiles (Still get some but maybe 1 or 2 every minute as opposed to 5 or 6 every 10 seconds) but has resulted in the dreaded "blurries" ie textures near the plane taking a long time to load up. If I pause the flight, the ground textures are eventually rendered in about 5 secs. Also, the autogen seems to be appearing much later (ie popping up at about 2/3 miles rather than 5/6 before). This could be placebo effect though...I'll check it again without the increase and see what I get.Are you able to explain why this tweak has cured my original problem? I LOVE that it works but I like to understand why and what implications it has on the system. Why is it I require a SWT of 20 when others have it set to 2 or even lower? Presumably it's a hardware issue and if so, I'd love to know what I could change in the hope of helping get back to SWT=2?

Bojote, having read this thread here http://forum.avsim.net/topic/317709-blurries-fix-for-fsx-experimental/page__st__75 am I right to think that maybe my 896MB GPU RAM on the slower GTX260 may be my bottleneck in that the new tiles are not being "available" to the terrian engine in time and so are therefore rendered as white tiles?"If after SWAP_WAIT_TIMEOUT frames the texture still isn't available, the terrain engine starts using the new triangles anyway. This usually results in a tile of terrain that is either missing or textured strangely/incorrectly for a few frames until the texture finally shows up in video memory"Presumably, in that case I need to find a balance between SWT & MaxTextureLoad that will reduce the blurries whilst at the same time keeping the flashing white tiles to a minimum? I've also read in that thread that you recommend the use of FIBER_FRAME_TIME_FRACTION on higher spec machines? Presumably with my i7 860 and GTX260 you would not recommend it's use in my situation?

Bojote, having read this thread here

Very good ;) you are a good observer.Correct, when I told you to increase TextureMaxLoad I was hoping that by pumping textures faster into your Video card memory textures will be 'available' for the terrain engine, since this not solve it, increasing SWAP_WAIT_TIMEOUT makes the terrain engine wait a little longer.. of course, this has the problem of inducing 'blurries' because of the aditional 'wait' time. Also, FIBER_FRAME_TIME_FRACTION determines how much CPU will be allocated to 'loading' terrain, so if you increase this, more CPU time will be dedicated to 'loading' terrain (faster) and can induce the white flashes. All three settings are related as you can see.You can keep trying increasing TextureMaxLoad, reducing FIBER_FRAME_TIME_FRATION and increasing SWAP_WAIT_TIMEOUT until you find a good balance. Now.. you are right about your video card being a limiting factor. Probably it does not have enough memory (this might be possible if you are using a higher than usual LOD_RADIUS) so, experiment a bit more or consider upgrading your GPU. You got all the analysis right, so, I'm pretty sure you can troubleshoot this on your own now.