What clouds and what TML in fsx.cfg?And funny you say that about EVGA, everyone else said EVGA is top of the line, like, a reference card, one of the best. And btw. it only makes problems in FSX. No other game.

EVGA here and no problem with BP=0(see one of my previous post in this thread with settings)

Hi David,Remember AA can also be tweaked inside FSX... [GRAPHICS]MultiSamplesPerPixel=8MultiSampleQuality=2

Can you explain these settings a little more? How do you get the best image quality possible?

How do you get the best image quality possible?

With nHancer.. the above settings control in-game AA which is like a dumbed down version of AA, so no matter if you use 32x AA you'll never get the quality of nHancer.

With nHancer.. the above settings control in-game AA which is like a dumbed down version of AA, so no matter if you use 32x AA you'll never get the quality of nHancer.

but you also apply AA to objects which shouldn't have it (like clouds), seriously lowering your fps in bad weather

but you also apply AA to objects which shouldn't have it (like clouds), seriously lowering your fps in bad weather

You could experiment in-sim with the following if you don't want to use nHancer:[GRAPHICS]MultiSamplesPerPixel=8 // 4, 8 or 16MultiSampleQuality=2 // you can try 1, 2, 3... really don't know what it means.

And you matched FPS as well?I notice you have the Evga card, notorious for problems with bad voltage regulation, many a RMA, might check in EVGA video card forum, I never ever get snow.Stephen, Have you tried this yet?I just had this 20 min light with all settings maxed, this is full AG and Full scenery on top of LOD8.5 in the CS757, it killed the frames mind you but no problems with corruption as long as I had Bloom and groundshadows set to off with everthing else maxed.I think now I can go back to Very dense settings and be happy...Still testing

Going to try it right now. I will report back shortly, hopefully this evening.Stephen

What clouds and what TML in fsx.cfg?And funny you say that about EVGA, everyone else said EVGA is top of the line, like, a reference card, one of the best. And btw. it only makes problems in FSX. No other game.

Good questions, I have been biting into this slowly but near max and doing ok, however clouds are default and TML=1024As far as EVGA 285GTX's I'm not sure how big of an issue it is but you can read about some of it here as well as in the evga forums.I would look into it, try getting it RMA'd. since your CPU is water cooled how is your card cooled and how cool does your card run?As I mentioned I have never gotten snow.

Going to try it right now. I will report back shortly, hopefully this evening.Stephen

TBM=30 was horrible, like stuck in glue and very unstable with corruption making the sim unflyable. I have another couple of ideas. I will try them out first to see if I might be right on something.Stephen

TBM=30 was horrible, like stuck in glue and very unstable with corruption making the sim unflyable. I have another couple of ideas. I will try them out first to see if I might be right on something.Stephen

I dont follow you, it should have no FPS effect on your performance, its to help limit blank textures as when panning views etc, reducing helps take the allocated load of textures off of the GPU so it stops looking too far ahead of things, since the Buffer is gone.sure you altered the right flag? The point is to reduce this value, but not lower than your FPS limit.TBM=30 was tied to my limit of 30 FPSSo many here have it up into the 80s and 100's like I did, soon as I reduced it, no more screen coruption at BP=0, while all filtering and screen res is full blast.Just flew Fly Tampa Hong kong VeryDense AG and Scenery, never before...

but you also apply AA to objects which shouldn't have it (like clouds), seriously lowering your fps in bad weather

This is true with my system as well, and the best cure for me is to lower cloud density medium in heavy weather -- I set cloud distance to out to 110nm's. I do like nHancers 8xS and it is pretty much only heavy weather in dense scenery that stresses my system.I do want to move to a 1920 x 1200 display but I am concerned the perf impact will be significant. I have very good perf now, but I like the idea of finer res and also the pixel pitch is lower on the model I have been eyeing, now on sale at Dell.Noel

I dont follow you, it should have no FPS effect on your performance, its to help limit blank textures as when panning views etc, reducing helps take the allocated load of textures off of the GPU so it stops looking too far ahead of things, since the Buffer is gone.sure you altered the right flag? The point is to reduce this value, but not lower than your FPS limit.TBM=30 was tied to my limit of 30 FPSSo many here have it up into the 80s and 100's like I did, soon as I reduced it, no more screen coruption at BP=0, while all filtering and screen res is full blast.Just flew Fly Tampa Hong kong VeryDense AG and Scenery, never before...

I don't understand it either. It was like my graphics card was packing it in, jumping, flashing, hugh corruptions. I stopped it withing a couple of minutes for fear of damage.Stephen

I don't understand it either. It was like my graphics card was packing it in, jumping, flashing, hugh corruptions. I stopped it withing a couple of minutes for fear of damage.Stephen

Sorry you got the scare StephenMake certain it was not lower than your FPS is set at.What value have you been using before for TBM? and what is your FPS at?Also as Word Not Allowed pointed out what value for TML do you use? Best to reset to 1024 for now...

For me, TBM=30 works pretty OK, I don't see much difference. I will go into more extensive testing, not changing anything for couple of days, see if it's stable. Nhancer set as usual, 8xS, 16AF, VSync on, preload now 1.FSX.cfg:[bufferpools]Poolsize=0[Display]ChangeTime=4.000000TransitionTime=4.000000ActiveWindowTitleTextColor=255,255,255ActiveWindowTitleBackGroundColor=0,28,140,64NonActiveWindowTitleTextColor=255,255,255NonActiveWindowTitleBackGroundColor=24,33,87,64InfoUpperRightTextColor=255,0,0InfoUpperRightBackGroundColor=0,0,0,0InfoLowerLeftTextColor=255,255,255InfoLowerLeftBackGroundColor=255,0,0,128InfoLowerRightTextColor=255,255,255InfoLowerRightBackGroundColor=255,0,0,128InfoBrakesEnable=TrueInfoParkingBrakesEnable=TrueInfoPauseEnable=TrueInfoSlewEnable=TrueInfoStallEnable=TrueInfoOverspeedEnable=TrueBLOOM_EFFECTS=0SKINNED_ANIMATIONS=1TEXTURE_BANDWIDTH_MULT=30UPPER_FRAMERATE_LIMIT=30WideViewAspect=False[Main]DisablePreload=1User Objects=Airplane, HelicopterSimObjectPaths.0=SimObjects\AirplanesSimObjectPaths.1=SimObjects\RotorcraftSimObjectPaths.2=SimObjects\GroundVehiclesSimObjectPaths.3=SimObjects\BoatsSimObjectPaths.4=SimObjects\AnimalsSimObjectPaths.5=SimObjects\MiscLocation=7,-29,1514,1114,\\.\DISPLAY1Maximized=0HideMenuNormal=1HideMenuFullscreen=1ProcSpeed=8724PerfBucket=7[Weather]WindshieldPrecipitationEffects=1MinGustTime=10MaxGustTime=500MinGustRampSpeed=1MaxGustRampSpeed=200MinVarTime=5MaxVarTime=50MinVarRampSpeed=10MaxVarRampSpeed=75TurbulenceScale=1.000000WeatherServerAddress=fs2k.zone.comWeatherServerPort=80WeatherGraphDataInDialog=0AdjustForMagVarInDialog=1DynamicWeather=2DownloadWindsAloft=0DisableTurbulence=0CLOUD_DRAW_DISTANCE=3DETAILED_CLOUDS=1CLOUD_COVERAGE_DENSITY=8THERMAL_VISUALS=0[DISPLAY.Device.NVIDIA GeForce GTX 285.0]Mode=1600x1200x32TriLinear=1[GRAPHICS]SHADER_CACHE_PRIMED=1693458432TEXTURE_MAX_LOAD=1024NUM_LIGHTS=8AIRCRAFT_SHADOWS=0AIRCRAFT_REFLECTIONS=1COCKPIT_HIGH_LOD=1LANDING_LIGHTS=1AC_SELF_SHADOW=0EFFECTS_QUALITY=2GROUND_SHADOWS=0TEXTURE_QUALITY=3IMAGE_QUALITY=0See_Self=1Text_Scroll=0SHADER_CACHE_PRIMED_10=1693458432D3D10=0[TERRAIN]LOD_RADIUS=8.500000TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=600MESH_COMPLEXITY=100MESH_RESOLUTION=25TEXTURE_RESOLUTION=29AUTOGEN_DENSITY=3DETAIL_TEXTURE=1WATER_EFFECTS=6

Shockwave, do something for me please - load the GPU-Z while flying, load your situation with 15fps, fly around a while in windowed, and read the GPU Load. I can't help to notice that GPU crashes happen when I overload the card with the FSX. If I'm careful not to do it, like REX 1024 clouds and not 4096, not using REX weather engine but ASA, clouds range of 60miles, but boost CPU settings (terrain, LOD 8.5, autogen), I "only" get low FPS, but no crashes. To me it seems like I can do ANYTHING I would like around CPU heavy stuff, but have to be careful with anything connected to clouds as those eat away the GPU... It is just what it seems to me. I would like someone to confirm or disconfirm.

I can't help to notice that GPU crashes happen when I overload the card with the FSX.

Correct... Autogen being the one hitting the GPU harder *IF* you are under a excesive FPS condition. This is due to Object batching ocurring at a 'per frame' basis, so the higher the frame rate, the hardest the hit on the GPU, BP=0 is 'very sensitive' to your 'autogen' setting inside the sim, followed by scenery complexity and scenery detail next, clouds won't affect you that much unless you antialias via nHancer.The above are the 'in-game' settings with the biggest impact on GPU...now, outside of the sim, having Vsync ON is the one most sensitive to BP=0, followed by 'filtering' (AA & AF) evidently, the 'higher' the frame rate, the hardests is for your GPU to keep up, this is specially true for autogen.If you want to see how AutoGen taxes your GPU you could set Vsync to OFF and set frames to unlimited in FSX, then lower EVERY SINGLE SLIDER, ALL OF THEM, except AutoGen, and you'll see what I mean. no other slider, no matter how high will make the GPU jump to 100% so, the GPU does become the limiting factor when you use BP=0 effectively shifting the balance in FSX to a GPU bound app like I previously said.Unfortunately, the performance 'gain' in FSX when you use BP=0 doesn't mean much if you are GPU limited, btw, I purchased today a 5870, so I can provide more info next week on how it compares to a GTX 285 (which is the one I currently have, by the way I'm about to sell it on ebay, if anyone is interested let me know) I guess I can price it in the $200-$250 range (its the 2GB version) or make me an offer.