All of a sudden I am getting bad scenery spikes and artifacting all over. What could cause it? I reduced my buffer pools to 48000000 .(edit) my temps seem to be okay and there isn't any overheating.OS Win 7 64 biti920 OC to 3.8ghz6 gb RamNvidia GTX275

All of a sudden I am getting bad scenery spikes and artifacting all over. What could cause it? I reduced my buffer pools to 48000000 .(edit) my temps seem to be okay and there isn't any overheating.OS Win 7 64 biti920 OC to 3.8ghz6 gb RamNvidia GTX275

Hey Frankla,Ideally, you have to ask yourself what changed before you noticed the spiking? Did you install a new add-on? Change a setting? (However innocent it may seem.) Then you can try going backwards to see if that makes a difference.That said, your bufferpools could be too low now. You didn't say what you had before but try around 150 - 200 million.This also depends on other factors such as what your other FSX graphics settings are, what you're flying (add-on aircraft), where you're flying at the time (cities) and whether you have any other add-ons such as ground textures. All of these quickly fill up the graphics memory banks.Cheers,

All of a sudden I am getting bad scenery spikes and artifacting all over. What could cause it? I reduced my buffer pools to 48000000 .(edit) my temps seem to be okay and there isn't any overheating.OS Win 7 64 biti920 OC to 3.8ghz6 gb RamNvidia GTX275

Not that this will help you but I had the same thing happen to me a few months ago, along with suddenly losing external a/c textures and other graphic anomalies. I posted on the forum and most people said it was since I was running a 32 bit system and a lack of RAM since I only have 2 gb.Turned out something was wrong with the sound card that my Asus mobo came with, which was a SoundMax card. Once I replaced it with a SoundBlaster card I haven't had any issues since and I even gained a little more performance.Just goes to show that even something simple but unassuming like a sound card can completely foul up your experience.BTW, I was reading an article in the Sept-Oct issue of PC Pilot and they were mentioning that the original version on FSX set the default Bufferpool value of Poolsize=1000000 or 1,000,000 with commas to make it easier to read. Then in SP1 they upped the stock Poolsize to equal Poolsize=4000000 or 4,000,000. So according to them they recommend a value of anywhere from 4,000,000 to 10,000,000 or Poolsize=4000000 to Poolsize=10000000, only using the 10,000,000 value if you area on a 64 bit system with a load of RAM. Then I noticed yours was set to 48,000,000, which is way high. Have you ever tried a lower setting like 10,000,000 or deleting the entry all together.On a side note, I never used a bufferpool entry in my cfg, but a few weeks ago I read another thread somewhere regarding it and they were suggesting a really low value of 100,000 to 500,000 or Poolsize=100000 to Poolsize=500000. I actually thought what the heck i'll try it and I can always delete it. I used the Poolsze=500000 and my sim has actually never run better. Although I only have 2gb RAM and a video card with 1gb RAM.Hopefully some of this info may help.Good luck.

Hey Frankla,Ideally, you have to ask yourself what changed before you noticed the spiking? Did you install a new add-on? Change a setting? (However innocent it may seem.) Then you can try going backwards to see if that makes a difference.That said, your bufferpools could be too low now. You didn't say what you had before but try around 150 - 200 million.This also depends on other factors such as what your other FSX graphics settings are, what you're flying (add-on aircraft), where you're flying at the time (cities) and whether you have any other add-ons such as ground textures. All of these quickly fill up the graphics memory banks.Cheers,

Nothing has been added/deleted. But thanks. Will try increasing it.

Thanks for your suggestion. Nothing is helping. Tried lowering the bufferpools. [edit] I did realize that it only happens in heavily forrested areas only and lowering the autogen setting helps.

Thanks for your suggestion. Nothing is helping. Tried lowering the bufferpools. [edit] I did realize that it only happens in heavily forrested areas only and lowering the autogen setting helps.

You just nailed it. Turn down your sliders. You are taxing your system too hard and your specific configuration cannot handle the amount of autogen being thrown at it. The bufferpools tweak being set to high (indcreasing the buffepool setting is never a fix for this issue. It will only make it worse) can also play a large role in autogen spikes developing as well as can memory depletion.

Thanks for your suggestion. Nothing is helping. Tried lowering the bufferpools. [edit] I did realize that it only happens in heavily forrested areas only and lowering the autogen setting helps.

Edit the trees down in the fsx.cfg file: This is mine; all after each "//" is an older setting. The defaults are the last setting in each row.TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=1500 // 300 // 4500TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=2500 // 3500 // 3000 // 3500 // 4500 // 3000

The problem is a combination of especially seeing you are on i7 is that your FPS setting is too high for the slider settings being used/scenery flying around. i learned this when flying into EHAM I noticed what you are seeing. I had never seen this problem ever untill flying into EHAM. After many hours of differnt settings I found that if I lowered my max FPS (in my case from 30 down to 26) eliminated the spikes and random surges i was seeing. Another area I saw this was kJFK but is far better using a lower FPS. So long story short:Reduce your FPS lock lower. Try lowering 2 FPS increments untill the problem is resolved. If you are unable to resolve it that way then remove the bufferpool edit from your CFG. and retest trying lower FPS. I know... iys hard to LOWER the fps but trust me, you will get a far better more consistant sim experience once you tune in your FPS to what is best for your system.Jim

Thank you all. Wasn't Nick doing something with GEX to change some of the trees that are known to be resource hog?

Edit the trees down in the fsx.cfg file: This is mine; all after each "//" is an older setting. The defaults are the last setting in each row.TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=1500 // 300 // 4500TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=2500 // 3500 // 3000 // 3500 // 4500 // 3000

Why can't I find the above lines in the fsx.cfg file? Are they left out by default?

Why can't I find the above lines in the fsx.cfg file? Are they left out by default?

By default the entry is not there and in reality you are better off adjusting your autogen slider than editing the .cfg file because it messes with autogen priority.However if you wish to add the entires, add them just below the [TERRAIN] section in FSX.CFGTERRAIN_MAX_AUTOGEN_TREES_PER_CELL=4500TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=3000The figures above are the default that FSX uses and you should set them to a lower amount. Setting to 0 for instance will mean that you see no objects in the simulation. Please note that the maximum setting for each item is 6000 and it is suggested that you use a minimum of 10 to avoid issues within the game.

Why can't I find the above lines in the fsx.cfg file? Are they left out by default?

Yes. You have to add them under the section Terrain.