OK, I'm going mad. I've had FSX since the beginning and have run it up until december last year on an old AMD 2200+ powered PC. FSX ran wll on that setup scenerywise, unless I added some of the more complex aircrat into the mix.Now that I've gotten a new and powerful PC I just can't seem to get FSX running the way I want it to. I use quite concervative settings and have 30+ fps wherever I fly, including New York. There is nothing wrong with the overall smothness. It's as good as FSX gets.However I get texture flashing/flickering. Ground textures fliker into white, and ocean textures flicker into light blue. You can see the whole squares flashing.I've tried Bojotes tweaks, but still the same. I've got no addons installed - not even FSUIPC. Could this be an NVidia driver problem - I'm running the latest ones, 290 something. Anyone have these flickers?

We need to know what speed you're runninhg the 2700K at, but to stop the ground flashing you need the BufferPools mod: Add this anywhere in the cfg as a new section..[bufferPools]UsePools=1 // "0" means no pools, all data goes direct to the GPU. A "1" here = 'Use a pool'PoolSize=850000000 //8388608 // My first figure here is 850Mb; the 2nd is 8MB, It can be almost any size, but try 100000000 to start.RejectThreshold=921440 // 131072 // 524288 // 262144 // 131072 Any data bigger than the RT will go directly to the GPU. Try all of these sizes.If it works, and this is dependent on your proc speed, you can try BufferPools=0 (or PoolSize=0), and "//"-out the PoolSize & RT values.HIGHMEMFIX=1, under [GRAPHICS]You probably already have this in the cfg, but just in case - this also stops flashing.

Edited March 2, 201214 yr by Paul J

Thanks for the quick reply Paul! You're a gent as always!I'm running my 2700K at stock speed (Don't have time now to learn how to O/C and the defualt BIOS profiles gave me boot problems).Bojotes tool added those tweaks, but with other numbers for poolsize and rejectthreshold. I'll try your numbers and see if that makes a difference.

Thanks for the quick reply Paul! You're a gent as always!I'm running my 2700K at stock speed (Don't have time now to learn how to O/C and the defualt BIOS profiles gave me boot problems).Bojotes tool added those tweaks, but with other numbers for poolsize and rejectthreshold. I'll try your numbers and see if that makes a difference.

Please let me know, if you find a solution for that..Our rigs are similar, and I do get same ground flashing when flying with a fast complex aircraft.

We need to know what speed you're runninhg the 2700K at, but to stop the ground flashing you need the BufferPools mod: Add this anywhere in the cfg as a new section..[bufferPools]UsePools=1 // "0" means no pools, all data goes direct to the GPU. A "1" here = 'Use a pool'PoolSize=850000000 //8388608 // My first figure here is 850Mb; the 2nd is 8MB, It can be almost any size, but try 100000000 to start.RejectThreshold=921440 // 131072 // 524288 // 262144 // 131072 Any data bigger than the RT will go directly to the GPU. Try all of these sizes.If it works, and this is dependent on your proc speed, you can try BufferPools=0 (or PoolSize=0), and "//"-out the PoolSize & RT values.HIGHMEMFIX=1, under [GRAPHICS]You probably already have this in the cfg, but just in case - this also stops flashing.

PJ, how can I know that Bufferpool really works ? If I give 850mb bufferpool, is there a software that I can see that GPU using that amount ram while FSX on ?

It worked. I set poolsize to 1 000 000 000, and rejectthreshold to the lowest value 131072.Did not need to apply the highmemfix tweak for the flashing to disappear.

The HIGHMEMFIX=1 should be put in, SH, as it also has some impact in other areas of the sim - cloud flashing is one.You probably wouldn't need a BufferPool at all, Simmerhead - IF you were just using ordinary rotating disc drives: but SSD's are nothing more than very large chunks of ram - very fast RAM - and can supply data 1000 times faster than discs can - hence this data needs to be included in the buffering process - and you're doing this. Your 580 is still chewing all you can throw at it, but the issue was keeping it up with the SSD's - not the proc. Now - if you bring the proc up to 4.6-gig+ you will have a very balanced system!A gig of ram devoted to a buffer is too large: bring it to 200 meg and see how that goes. There is no point devoting much-needed ram to a buffer that never gets fully utilized. If it's still good - drop it some more, until you find the sweet spot.

Edited March 2, 201214 yr by Paul J

Thanks again Paul. I struggled to keep the O/C stable so I'll leave it for now, but if I ever get the time to learn the baics I will try to push my 2700 a bit higher. My motherboard manual doesn't make sense to me, and I've found no good tutorials, so no go for now.BTW. Your explenation of the bufferpool tweak is the best I've read in five years of fsx.cfg tweaking :)

However I get texture flashing/flickering. Ground textures fliker into white, and ocean textures flicker into light blue. You can see the whole squares flashing.

Try1. Turn on AF in FSX and Force it to 16x in NVCP.2. Use 2x SGSSAA (4x if you can run it with 30 fps :( )good luck

simmerhead,It looks like you have a flashing texture problem because of bp tweaks. Then set water to high 2.x is the way to fix it.ps. a high bufferpool will decrease your FSX performance!

simmerhead,It looks like you have a flashing texture problem because of bp tweaks. Then set water to high 2.x is the way to fix it.ps. a high bufferpool will decrease your FSX performance!

My FSX is 100% pure. No tweaks and no addons installed.

The HIGHMEMFIX=1 should be put in, SH, as it also has some impact in other areas of the sim - cloud flashing is one.You probably wouldn't need a BufferPool at all, Simmerhead - IF you were just using ordinary rotating disc drives: but SSD's are nothing more than very large chunks of ram - very fast RAM - and can supply data 1000 times faster than discs can - hence this data needs to be included in the buffering process - and you're doing this. Your 580 is still chewing all you can throw at it, but the issue was keeping it up with the SSD's - not the proc. Now - if you bring the proc up to 4.6-gig+ you will have a very balanced system!A gig of ram devoted to a buffer is too large: bring it to 200 meg and see how that goes. There is no point devoting much-needed ram to a buffer that never gets fully utilized. If it's still good - drop it some more, until you find the sweet spot.

Paul, I've put in an hour or two of testing this evening. I added the usepools, poolsize, rejectthreshold and highmemfix to a clean fsx.cfg file. I started with a poolsize of 100 000 000 and rejectthreshold of 131072. I had to increase the poolsize to 850 000 000 before the flashing textures dissapeard. Then I removed both higmemfix and rejectthreshold. I can see no change, so for me the only thing I needed to fix the problem was:[bufferPools]UsePools=1PoolSize=850000000Man how I wish FS11 was in the works, or even better, that someone picked up the Outerra engine and made a sim out of it. I've been playing around with the Outerra demo all night and it's breathtaking stuff even though it is in its infancy.Anyway, thanks for all the help. Have a nice weekend!

850000000 BP would work for me too, but I get Fatal Error on exit if I put more than 400000000 BP. :(