--------------------------------------------------------------------------------I have FSX internally, cranked right up. What I didn't have cranked right up was water. It was originally at 2Mid, but now is fully opened up. I have to say, inside PNW, the highest setting is stunning! Run Nick's nHancer to the letter EXCEPT: Prerender now set to 1, and Vsync now set to OFF. That's about it. With the water on highest, drivers at 197.13 beta and the above....BP=0 is stable until I end FSX, or wake up from having fallen asleep at the desk.... :( Mitch

Hm, OK, to go correctly about this: did you manually change TEXTURE_MAX_LOAD or LOD_RADIUS?Thanks

Hm, OK, to go correctly about this: did you manually change TEXTURE_MAX_LOAD or LOD_RADIUS?Thanks

Here's the whole deal:[bufferPools] PoolSize=0[sOUND]AmbientUIMusicVolume=-6.000000SOUND=1SOUND_QUALITY=2SOUND_LOD=0UISound=1AmbientUI=0SOUND_FADER1=0.150000SOUND_FADER2=0.200000SOUND_FADER3=0.210000SOUND_FADER4=1.000000AmbientUIMusic=FSX01PrimaryDevice={DEF00000-9C6D-47ED-AAF1-4DDA8F2B5C03}VoiceDevice={DEF00002-9C6D-47ED-AAF1-4DDA8F2B5C03}[Display]RUNWAY_LIGHTS_SURFACE_SCALAR=1.0RUNWAY_LIGHTS_VASI_SCALAR=0.8RUNWAY_LIGHTS_APPROACH_SCALAR=0.9RUNWAY_LIGHTS_STROBE_SCALAR=1.2 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=80UPPER_FRAMERATE_LIMIT=0WideViewAspect=True[Main]DisablePreload=1User Objects=Airplane, HelicopterSimObjectPaths.0=SimObjects\AirplanesSimObjectPaths.1=SimObjects\RotorcraftSimObjectPaths.2=SimObjects\GroundVehiclesSimObjectPaths.3=SimObjects\BoatsSimObjectPaths.4=SimObjects\AnimalsSimObjectPaths.5=SimObjects\MiscSimObjectPaths.6=ORBX\FTX_AU\FTXAI_AIRCRAFTSimObjectPaths.7=MyTraffic\AircraftHideMenuNormal=0HideMenuFullscreen=1ProcSpeed=9054PerfBucket=7Maximized=1Location=444,198,1476,964,\\.\DISPLAY1[PANELS]IMAGE_QUALITY=1QUICKTIPS=0PANEL_OPACITY=100PANEL_MASKING=1PANEL_STRETCHING=1UNITS_OF_MEASURE=0DEFAULT_VIEW=0[Weather]WindshieldPrecipitationEffects=1MinGustTime=10MaxGustTime=500MinGustRampSpeed=1MaxGustRampSpeed=200MinVarTime=5MaxVarTime=50MinVarRampSpeed=10MaxVarRampSpeed=75TurbulenceScale=1.000000WeatherServerAddress=fs2k.zone.comWeatherServerPort=80WeatherGraphDataInDialog=0AdjustForMagVarInDialog=1DynamicWeather=1DownloadWindsAloft=1DisableTurbulence=0CLOUD_DRAW_DISTANCE=5DETAILED_CLOUDS=1CLOUD_COVERAGE_DENSITY=8THERMAL_VISUALS=0[DISPLAY.Device.NVIDIA GeForce GTX 285.0]Mode=1920x1200x32TriLinear=1[CONTROLS]Controls_Default=StandardControls_Current=StandardKBDAIL=64KBDELEV=64KBDRUD=64force_master_gain=10000force_stick_force_enabled=1force_stick_shaker_enabled=1force_gear_bump_enabled=1force_crash_enabled=1force_ground_bumps_enabled=1force_master_enabled=1[TextInfo.1]Latitude=1,1Longitude=1,2Altitude=1,3Heading=1,4AirSpeed=1,5WindDirectionAndSpeed=1,6[TextInfo.2]FrameRate=1,1LockedFrameRate=1,2GForce=1,3FuelPercentage=1,4[TextInfo.3]Latitude=1,1Longitude=1,2Altitude=1,3Heading=1,4AirSpeed=1,5WindDirectionAndSpeed=1,6FrameRate=2,1LockedFrameRate=2,2GForce=2,3FuelPercentage=2,4[slewTextInfo.1]Latitude=1,1Longitude=1,2Altitude=1,3Heading=1,4AirSpeed=1,5[slewTextInfo.2]FrameRate=1,1LockedFrameRate=1,2[slewTextInfo.3]Latitude=1,1Longitude=1,2Altitude=1,3Heading=1,4AirSpeed=1,5FrameRate=2,1LockedFrameRate=2,2[DynamicHeadMovement]LonAccelOnHeadLon=-0.020000LonAccelOnHeadPitch=-0.010000RollAccelOnHeadLat=0.010000YawAccelOnHeadLat=-0.100000RollAccelOnHeadRoll=0.100000MaxHeadAngle=5.000000MaxHeadOffset=0.300000HeadMoveTimeConstant=1.000000[VirtualCopilot]VirtualCopilotActive=0[GRAPHICS]SHADER_CACHE_PRIMED=1693458432TEXTURE_MAX_LOAD=1024NUM_LIGHTS=8AIRCRAFT_SHADOWS=1AIRCRAFT_REFLECTIONS=1COCKPIT_HIGH_LOD=1LANDING_LIGHTS=1AC_SELF_SHADOW=1EFFECTS_QUALITY=2GROUND_SHADOWS=0TEXTURE_QUALITY=3IMAGE_QUALITY=0See_Self=1Text_Scroll=1SHADER_CACHE_PRIMED_10=1693458432D3D10=0[uSERINTERFACE]PageID=1OpenATCOnCreate=0SHOW_MISSION_CAPTIONS=0PAUSE_ON_LOST_FOCUS=1PROMPT_ON_EXIT=1Map_Orientation=2ShowAllACPaintSchemes=1SelectAircraftManufacturer=AllSelectAircraftPublisher=AllSelectAircraftType=AllDisplayFuelAsWeight=0SITUATION=C:\Users\Sesquash\Documents\Flight Simulator X Files\Baron 58 at Olympia Washingto[ATC]ShowATCText=0COMM_MSG_NONE_COLOR=FFFFFFFFCOMM_MSG_ATC_USER_COLOR=FFB6FFB6COMM_MSG_USER_ATC_COLOR=FFFFD21BCOMM_MSG_ATC_AI_COLOR=FF00FF00COMM_MSG_AI_ATC_COLOR=FFFF7840AutoOpenAirTrafficWindow=1UsePilotVoice=1PilotVoice=196608[PointOfInterestSystem]CycleSetting=0[sCENERY]LENSFLARE=1DAWN_DUSK_SMOOTHING=1IMAGE_COMPLEXITY=5[TrafficManager]AirlineDensity=40GADensity=25FreewayDensity=25ShipsAndFerriesDensity=0LeisureBoatsDensity=0IFROnly=0AIRPORT_SCENERY_DENSITY=0[TERRAIN]TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=600LOD_RADIUS=4.500000MESH_COMPLEXITY=100MESH_RESOLUTION=24TEXTURE_RESOLUTION=29AUTOGEN_DENSITY=4DETAIL_TEXTURE=1WATER_EFFECTS=7[AContain]ShowLabels=0ShowUserLabel=0ShowLabelManufacturer=1ShowLabelModel=1ShowLabelTailNumber=0ShowLabelDistance=1ShowLabelAltitude=1ShowLabelAirline=0ShowLabelAirlineAndFlightNumber=0ShowLabelFlightPlan=0ShowLabelContainerId=0ShowLabelAirspeed=0ShowLabelHeading=0LabelDelay=1000LabelColor=FFFF0000[iNTERNATIONAL]ASLAT=2ASLON=1MEASURE=0[REALISM]PFactor=1.000000Torque=1.000000GyroEffect=1.000000CrashTolerance=1.000000General=1.000000UnlimitedFuel=FalseTrueAirspeed=FalseAutoCoord=FalseRealMixture=FalseStressDamage=TrueGEffect=TrueManualLights=TrueGyroDrift=FalseCrashWithDyn=TrueCrashDetection=TrueAutoTrim=False[sIM]SYSCLOCK=1[sTARTUP]DEMO=0SHOW_OPENING_SCREEN=0STARTUP_DEMO=LoadWindow=1[FACILITIES]COUNTRY=STATE=OregonCITY=Crescent LakeGTL_BUTTON=1317[Misc]Com_Rate=7[RWW_WEATHER_MAP]SHOW_AIRPORTS=0SHOW_VORS=0SHOW_NDBS=0SHOW_APPROACHES=0SHOW_INTERSECTIONS=0SHOW_VICTOR=0SHOW_JET=0SHOW_AIRSPACE=0SHOW_FLIGHTPLAN=1SHOW_WEATHERSTATIONS=1SHOW_WEATHERSYSTEMS=1SHOW_DATATAGS=1SHOW_TERRAIN=1[FlightPlanMap]LineWidth=2SHOW_AIRPORTS=1SHOW_VORS=1SHOW_NDBS=1SHOW_APPROACHES=1SHOW_INTERSECTIONS=1SHOW_VICTOR=0SHOW_JET=0SHOW_AIRSPACE=1SHOW_FLIGHTPLAN=1SHOW_WEATHERSTATIONS=1SHOW_WEATHERSYSTEMS=1SHOW_DATATAGS=1SHOW_TERRAIN=1show_waypoints=1show_airways=1show_markers=1show_volume_boundaries=1show_ac_twr=1[MAPVIEW_MAP]SHOW_AIRPORTS=1SHOW_VORS=1SHOW_NDBS=1SHOW_APPROACHES=1SHOW_INTERSECTIONS=0SHOW_VICTOR=0SHOW_JET=0SHOW_AIRSPACE=1SHOW_FLIGHTPLAN=1SHOW_WEATHERSTATIONS=1SHOW_WEATHERSYSTEMS=1SHOW_DATATAGS=1SHOW_TERRAIN=1show_flight_history=1[MULTIPLAYER]condAccoutPassword=0VoiceVolume=2.000000

Very obliged. Thank you.What I now noticed that GPU usage hardly goes over 80%. I also lowered the quality of clouds from 4096 to 1024 and TEXTURE_MAX_LOAD, disabling the HD clouds.Before when I had all GPU crashes and snow - btw. now it's gone if I set settings as you do - could it really be from overloading the GPU? Not memory-wise but rather GPU Load and that it has almost nothing to do with the CPU?And if for some reason GPU usage goes up to 98%, I get flashes, errors and voila - keep doing it and GPU is gonna crash and it starts snowing...EDIT: Interesting thing enough - I get this with the REX2 weather engine. Using default FSX weather, no problem. And the difference in GPU Load usage is "only" 10-20% (50% vs 700% when using 1024 clouds and 4096 ones). This is with maximum draw distance.

Some stand-outs from Mitch's Cfg (doesnt mean their bad wrong etc, just relevant)[bufferPools] PoolSize=0[Display]TEXTURE_BANDWIDTH_MULT=80[DISPLAY.Device.NVIDIA GeForce GTX 285.0]Mode=1920x1200x32TriLinear=1[GRAPHICS]TEXTURE_MAX_LOAD=1024[TERRAIN]TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=600LOD_RADIUS=4.500000MESH_COMPLEXITY=100MESH_RESOLUTION=24

I also lowered the quality of clouds from 4096 to 1024 and TEXTURE_MAX_LOAD, disabling the HD clouds.Before when I had all GPU crashes and snow - btw. now it's gone if I set settings as you do - could it really be from overloading the GPU? Not memory-wise but rather GPU Load and that it has almost nothing to do with the CPU?And if for some reason GPU usage goes up to 98%, I get flashes, errors and voila - keep doing it and GPU is gonna crash and it starts snowing...EDIT: Interesting thing enough - I get this with the REX2 weather engine. Using default FSX weather, no problem. And the difference in GPU Load usage is "only" 10-20% (50% vs 700% when using 1024 clouds and 4096 ones). This is with maximum draw distance.

Yes Word Not Allowed, its all the difference as has been stated over and over, notice Mitch also uses Tri not Aniso, also Stock max LOD of 4.5I think the first thing you could lose was chosen well, turning the T_MAX down to 1024 or 2048.TRI and LOD 4.5 are not exceptable to my eye, nor for the hardware I am running...

Yes Word Not Allowed, its all the difference as has been stated over and over, notice Mitch also uses Tri not Aniso, also Stock max LOD of 4.5I think the first thing you could lose was chosen well, turning the T_MAX down to 1024 or 2048.TRI and LOD 4.5 are not exceptable to my eye, nor for the hardware I am running...

I noticed that LOD has very little or even any impact on GPU Load. I measured some 2-3% percent change, if even that.My problem was, I didn't know where to look for. Now I am starting to differ between what uses GPU and what uses CPU - and THAT's what's important. Just turning any setting down isn't gonna cut it. CPU doesn't care. GPU does, it seems.

NOK, I urge you to stop this nonsense... Efforts of people in this thread are simply gold-worth and I urge you to stop bringing the topic down. If you have something constructive to add, please do, if not, go read something else... thanks.

Amen! (Sorry, occupational hazard) Very well said!

...This topic has clearly become a topic to make BP=0 stable, no secret here. We all know FSX works (more or less) stable out of the box...

That's right. Perhaps it's more like FSX was stabilized out of the box by a precarious balancing of it's faults, as it were. Quite literally, FSX was a bigger and badder FS9. A bigger idea with a corresponding set of worse problems to solve. Hey, but that was then and this is now. Due to the generations ahead addon technologies, FSX has outgrown it's balance of compensating faults. Every worthwhile FS advance has been paid for in huge time and effort by those who were willing to do the hard work of research on the communities behalf, without which we'd be flying around in stick planes landing on long empty rectangles or still folding and throwing paper airplanes. Aces used to do much of the heavy lifting, but they are history. Developers are doing the best they can utlizing highly skilled and highly paid talent, but they can only afford to do just so much speculative experimentation.The real difference makers are those simmers that tinker and tweak away, using their own brand of analytical genius to produce small changes in the virtual landscape, but yet that do, from time to time, trigger a massive landslide that changes everything for everyone, for the better. That is where the real hope for a brighter flightsim idea becoming a reality lies. So, if anyone wants to help, that's great! If anyone does not want to help, that is OK. I am sure they will be most happy to freely benefit from any success derived.I want a better FSX based simulation. If I am not willing to help build it, I do not deserve to fly it. So, as they say, If it is to be, it is up to me..to help. Back to testing.Stephen

I noticed that LOD has very little or even any impact on GPU Load. I measured some 2-3% percent change, if even that.My problem was, I didn't know where to look for. Now I am starting to differ between what uses GPU and what uses CPU - and THAT's what's important. Just turning any setting down isn't gonna cut it. CPU doesn't care. GPU does, it seems.

Sorry not all just about GPU load, But I undewrstand what you are saying. For me its about trying to strike the balance that still allows for flying fast and low with out blurries and with a high LOD, with BP=0 it turns into a mess the higher the LOD. and That is all on the CPU @BP=xxxxxxxxx and then collides with the GPU.

Sorry not all just about GPU load, But I undewrstand what you are saying. For me its about trying to strike the balance that still allows for flying fast and low with out blurries and with a high LOD, with BP=0 it turns into a mess the higher the LOD. and That is all on the CPU @BP=xxxxxxxxx and then collides with the GPU.

Isn't that a kinda easy task, when we know what it's about? Max out the CPU relevant tasks, and then balance GPU relevant tasks to the CPU ones...? I know this is kinda oversimplified, but I am right now running a scenario that would usually kill my FSX, but as I lowered the cloud settings, which apparently ate away the GPU, it's stable without a glitch.

with BP=0 it turns into a mess the higher the LOD. and That is all on the CPU @BP=xxxxxxxxx and then collides with the GPU.

It makes sense, a higher LOD means more D3D calls to the buffer ring... in that case 'GPU Load' is completely irrelevant, because you are not saturating the actual GPU capability to render, but its ability to 'process' rendering commands (fast enough) in the command buffer if BP=0A high PoolSize will ease the problem because if the buffer ring is full the call will get 'queued' in the bufferpool and processed later with some lag, which will induce stutter BUT increase stability. BP=0 bypasses the bufferpool, so the experience is smoother, more CPU to do more, but also means more risk of stalling the GPU because there is no pool to store calls that can't be proceesed/batched/queued in time.. specifically in REAL TIME.DX10 reduces the number of D3D calls considerably, so a situation that fails under DX9 will most likely work using DX10 (which will prove not the actual GPU capability to render at fault, but the speed at which it processes rendering commands).. when I said that fermi could help you with the blurries is because you could use the increased LOD and have success with BP=0... the speed at which commands are read from the command buffer depends on the GPU architecture, so DDR5, increased bandwidth and faster clocks will definitely help lets wait and see.The way I see it now, is that BP=0 turns FSX into a more GPU bound app, and RAW speed is simply not enough because of how D3D works, the CPU sends actual 'commands' to the GPU for it to render, if the GPU cant keep up with the commands you stall it, doesn't matter if the GPU is used at 10%...

Run Nick's nHancer to the letter EXCEPT: Prerender now set to 1, and Vsync now set to OFF. That's about it. With the water on highest, drivers at 197.13 beta and the above....BP=0 is stable

Hey Mitch, I know you are stable, but add to the mix locking frames... running unlimited with VSYNC off can get you over 100FPS!!! and you don't want that, steady FPS will keep the GPU from being stalled by the CPU. specially, on heavy scenery areas.So, to wrap up... if anyone reading this, wants to give BP=0 a try with no artifacts or flashes follow what Mitch has posted to the letter!1) Prerender set to 12) Vsync set to OFF3) Water on highest setting (HIGH 2.0 or MAX 2.0)4) nVidia latest drivers (197.13)5) Lock your frames to 25 or 30 (but don't run unlimited!!)try the whole combo... and if you were one of the unlucky ones unable to make BP=0 work and the above fix it for you, please share. if you are still having problems, try lowering AA/ANISO and test to see if it is preventing you from using BP=0, what you can achieve will depend on how well you CPU/GPU are in sync reading/writing to/from the command buffer, so having a very fast video card will defenitely help, specially if running a fast CPU.

Tried it to the letter and it didnt fair well with my KSEA test flight and was only able to get 15 fps in the 172 with those settings. Went back to BP=10XXXXXX Pre Render 3 and I got 27 FPS on takeoff and then it quickly locked at 30 with very dense scenery/autogen. The VSYNC off is not an option for me as I get the tear effect when looking around. For me on my system I get much lower FPS using 0 BP when in higher demanding scenery, remove the tweek and its much better (for me). I stumbled on the pre render 1 when I first started testing this and found that it did remove my artifacting but my performance suffered in the bigger scenery areas. So for me at least I will stick with BP = 10,xxx,xxx for now. The 197.13 drivers do work nice.

For me on my system I get much lower FPS using 0 BP when in higher demanding scenery, remove the tweek and its much better (for me)

You could be GPU bound (when using BP=0). what clocks does your 260 Super Clocked Edition have?

Tried it to the letter and it didnt fair well with my KSEA test flight and was only able to get 15 fps in the 172 with those settings. Went back to BP=10XXXXXX Pre Render 3 and I got 27 FPS on takeoff and then it quickly locked at 30 with very dense scenery/autogen. The VSYNC off is not an option for me as I get the tear effect when looking around. For me on my system I get much lower FPS using 0 BP when in higher demanding scenery, remove the tweek and its much better (for me). I stumbled on the pre render 1 when I first started testing this and found that it did remove my artifacting but my performance suffered in the bigger scenery areas. So for me at least I will stick with BP = 10,xxx,xxx for now. The 197.13 drivers do work nice.

I get best perf in dense scenery/weather with something over BP=0. BP=0 is fine for lesser scenarios, but truly I get the same benefits with 1 or 2MB. I am usually perfect around 1MB, but 2MB seems good as well. Interestingly, it's worse at over 4MB or so. Some other changes that have left me with really smooth flight with excellent visuals has been setting process priority at HIGH via Prio.Did the 197.13's provide any real benefit for you?Noel

You could be GPU bound (when using BP=0). what clocks does your 260 Super Clocked Edition have?

626 core clock1350 shader1053 mem clockNoel: Yes I feel the 197.13 was a change for the better. I was running the 182.50 before the change. And BTW I tried 1 mb BP....... yeah baby... me likes it berry much!