I'm now getting stutters and micro stutters _only_ when looking out the window. On top of that when flying planes like the vfr f18 or the t38 talon speeds above 280-300 give me the blurs.The duke and other slower planes only give me micro stutters here and there but are annoying nevertheless.Bojote's tool is a no no here as it makes things way worse.I can't use the external limiter either. I'm using Nvidia inspector ( 8xS)My question is how do I get rid of the stutters I get when looking out the window ?Of course all help appreciated.ThanksVicSpecs:i7 980x (@4.27)-Asus 1366 Rampage II Extreme (X58)-2XWestern Digital VelociRaptor 300Gb SATA2 WD3000HLFS 10.000rpm-Seagate Barracuda 7200.12 1TB 32MB SATA-Zotac gtx 480-CORSAIR 950W CMPSU-950TXEU-NOCTUA dh 14-SE2 1366/1156/775/AMD/AM2/AM2+-OCZ DDR3 PC3-12800/ 1600MHz/Platinum XTC /Triple Channel Kits CL7-Antec Twelve Hundred Ultimate Gamer Case-Samsung SyncMaster 24" LCD P2450H Rose Black

Mr Beak,do you use the internal limiter? Have you tried to set bp=0 in your .cfg? Or possibly use the RejectThreshold setting instead of bp=0

do you use the internal limiter? Have you tried to set bp=0 in your .cfg? Or possibly use the RejectThreshold setting instead of bp=0

Yes I do use the internal limiter. I have it at 30. No bp=o (as it causes more issues than it cures) and no RT.

Yes I do use the internal limiter. I have it at 30. No bp=o (as it causes more issues than it cures) and no RT.

This is very system specific. I run it at 0 with no problems whatsoever.

This is very system specific. I run it at 0 with no problems whatsoever.

Yes. I meant it doesn't work on my machine. I should have added it "on my machine it causes more issues than it cures".Vic

Edited January 24, 201214 yr by MindYerBeak

Vic, Did your stutters just start? I had a pretty good setup until I migrated my operating system to a SSD, then the stutters started. I am now doing a complete reinstall of FSX to see if that fixes it.

You'll need to post your cfg, Vic, and a screenshot of you Inspector.I also went to the latest nVidia drivers and Inspector version, as this includes the ability to set an external frame limit from Inspector, thus allowing you to go 'unlimited'. I had all kinds of grief with the external limiters, and found that the internal was the way to go until these two came out.

Did your stutters just start?

They've always been ,more or less, there .I thought I could not get rid of them and it so tried to live with the "lag" but I really can't stand it.

You'll need to post your cfg, Vic, and a screenshot of you Inspector.I also went to the latest nVidia drivers and Inspector version, as this includes the ability to set an external frame limit from Inspector, thus allowing you to go 'unlimited'. I had all kinds of grief with the external limiters, and found that the internal was the way to go until these two came out.

Here they come. One thing to note is that the limiter that comes with the inspector does not accomplish much here.I mean even if i cap the fps at 30 they go up at 40 at times and I do not see any improvement over the internal limiter. Thanks in advance.--------fsx.cfg-----------[GRAPHICS]HIGHMEMFIX=1SHADER_CACHE_PRIMED=1693500672D3D10=0TEXTURE_MAX_LOAD=1024NUM_LIGHTS=8AIRCRAFT_SHADOWS=0AIRCRAFT_REFLECTIONS=1COCKPIT_HIGH_LOD=1LANDING_LIGHTS=1AC_SELF_SHADOW=0EFFECTS_QUALITY=2GROUND_SHADOWS=1TEXTURE_QUALITY=3IMAGE_QUALITY=0See_Self=1Text_Scroll=1SHADER_CACHE_PRIMED_10=1693500672[sOUND]AmbientUIMusicVolume=-6.000000PrimaryDevice={DEF00000-9C6D-47ED-AAF1-4DDA8F2B5C03}VoiceDevice={DEF00002-9C6D-47ED-AAF1-4DDA8F2B5C03}SOUND=1SOUND_QUALITY=2SOUND_LOD=0UISound=1AmbientUI=0SOUND_FADER1=0.640000SOUND_FADER2=0.660000SOUND_FADER3=0.650000SOUND_FADER4=0.500000AmbientUIMusic=FSX01[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=60UPPER_FRAMERATE_LIMIT=0WideViewAspect=True[Main]DisablePreload=1User Objects=Airplane, HelicopterSimObjectPaths.0=SimObjectsAirplanesSimObjectPaths.1=SimObjectsRotorcraftSimObjectPaths.2=SimObjectsGroundVehiclesSimObjectPaths.3=SimObjectsBoatsSimObjectPaths.4=SimObjectsAnimalsSimObjectPaths.5=SimObjectsMiscSimObjectPaths.6=MyTrafficAircraftProcSpeed=13902PerfBucket=7Maximized=0Location=0,0,1920,1080,.DISPLAY1HideMenuNormal=0HideMenuFullscreen=1[PANELS]IMAGE_QUALITY=1DEFAULT_VIEW=1QUICKTIPS=0PANEL_OPACITY=100PANEL_MASKING=1PANEL_STRETCHING=1UNITS_OF_MEASURE=0[Weather]WindshieldPrecipitationEffects=1MinGustTime=10MaxGustTime=500MinGustRampSpeed=1MaxGustRampSpeed=200MinVarTime=5MaxVarTime=50MinVarRampSpeed=10MaxVarRampSpeed=75TurbulenceScale=0.000000WeatherServerAddress=fs2k.zone.comWeatherServerPort= WeatherGraphDataInDialog=0AdjustForMagVarInDialog=1DynamicWeather=0DownloadWindsAloft=1DisableTurbulence=1CLOUD_DRAW_DISTANCE=5DETAILED_CLOUDS=1CLOUD_COVERAGE_DENSITY=8THERMAL_VISUALS=0[DISPLAY.Device.NVIDIA GeForce GTX 480.0]Mode=1920x1080x32TriLinear=1[AccelerationPack]ControlsFirstRun=0HomePageFirstRun=0[CONTROLS]Controls_Default=StandardControls_Current=StandardKBDAIL=64KBDELEV=64KBDRUD=64[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[Trusted]D:FSXfsdreamteamcouatlcouatl.exe.kltqzlqbuciiuiwnioqnzkirkiuhnhtaqeiczqhi=1C:Program Files (x86)FSDiscover!FSDiscoverFSX.dll.zbacqqikeuhblatzwcahantlrnerkrborwbiizwq=1D:FSXbglmanx.dll.hnccnnbteucwkbzbnnebreznkzabkiekriqktutl=1D:FSXPMDGDLLsPMDGOptions.dll.qqzlcorneterwqwrbbrarhbcecacerbecrwerwtk=1D:FSXPMDGDLLsPMDGEvents.dll.uzaanoaoeaheqeawcewuuqataqtwaztzttrlkwuw=1D:FSXPMDGDLLsPMDGSounds.dll.ielehtiwlbclenkanulrrbucabtquiioltzbzcwu=1D:FSXAddon ModulesAirbusNewHUD.dll.kuuulaqiiiozibruieqkrwqeoetnctiraknwazeb=1D:FSXModulesLVLD.dll.buzntlwkhuhrwalzhnzholqabblekwnhlhataabu=1D:FSXFeelThereErjE145XH.dll.unutcwlcbwqralnckkoewbekzblwbtncibcowchw=1D:FSXFeelThereE170EJetH.dll.kwhkqawzlttkhqkrqbikawiezczqniucuqcrtnqc=1D:FSXVistaMareViMaCoreX.dll.aancrkrtuuhakrrrrulqaeaiecrzhqkwnazrkbub=1D:FSXCaptain_Sim520cs.sound.dll.kzuwbweqilloncazlqbunecwrzziuewewnoeakrb=1D:FSXFSCaptainbinFSCaptain.dll.zchchlhcieciwuckakzzihrelwiccknbnaoitreo=1D:FSXPMDGDLLsPMDG_HUD_interface.dll.olaukwqouciozllnaequbhkcbhlrznitatuzenqk=1D:FSXCaptain_Sim767cs.sound.dll.kzuwbweqilloncazlqbunecwrzziuewewnoeakrb=1D:FSXModulesFSUIPC4.dll.enbiluctceiilrllzhlrkacqaeuikoeehikzkwii=1D:FSXGAUGESXGauge.DLL.bzqnkeickbuazauwreicqlebqnolaornwcwwuhwl=2D:FSXGAUGESPMDG_737NGX.DLL.wakkbzuhlawahctqlrllueubttztnobttrwanctz=2D:FSXGAUGESPMDG_737NGX_3.DLL.bqrrhqlhuozqlzuqlorqllnoibqrnoroheqbltln=2[DynamicHeadMovement]LonAccelOnHeadLon=-0.020000LonAccelOnHeadPitch=-0.010000RollAccelOnHeadLat=0.010000YawAccelOnHeadLat=-0.100000RollAccelOnHeadRoll=0.100000MaxHeadAngle=5.000000MaxHeadOffset=0.300000HeadMoveTimeConstant=1.000000[VirtualCopilot]VirtualCopilotActive=0[uSERINTERFACE]PageID=1OpenATCOnCreate=0ShowAllACPaintSchemes=1SelectAircraftManufacturer=TuttiSelectAircraftPublisher=PMDGSelectAircraftType=TuttiSHOW_MISSION_CAPTIONS=1PAUSE_ON_LOST_FOCUS=0PROMPT_ON_EXIT=1SITUATION=c:usersvickydocumentsfile di flight simulator xSafeFSX.FLTMap_Orientation=2DisplayFuelAsWeight=1[ATC]ShowATCText=1COMM_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=0[PointOfInterestSystem]CycleSetting=0[sCENERY]LENSFLARE=1DAWN_DUSK_SMOOTHING=1IMAGE_COMPLEXITY=4[TrafficManager]AirlineDensity=61GADensity=31FreewayDensity=0ShipsAndFerriesDensity=17LeisureBoatsDensity=18IFROnly=0AIRPORT_SCENERY_DENSITY=0[TERRAIN]LOD_RADIUS=4.500000MESH_COMPLEXITY=100MESH_RESOLUTION=23TEXTURE_RESOLUTION=29AUTOGEN_DENSITY=3DETAIL_TEXTURE=1WATER_EFFECTS=4[AContain]ShowLabels=0ShowUserLabel=0ShowLabelManufacturer=1ShowLabelModel=1ShowLabelTailNumber=0ShowLabelDistance=1ShowLabelAltitude=1ShowLabelAirline=0ShowLabelAirlineAndFlightNumber=0ShowLabelFlightPlan=0ShowLabelContainerId=0ShowLabelAirspeed=0ShowLabelHeading=0LabelDelay=1000LabelColor=FFFF0000[iNTERNATIONAL]ASLAT=2ASLON=0MEASURE=0[REALISM]PFactor=1.000000Torque=1.000000GyroEffect=1.000000CrashTolerance=1.000000General=1.000000UnlimitedFuel=FalseAllowEngineDamage=FalseTrueAirspeed=FalseAutoCoord=TrueRealMixture=TrueStressDamage=FalseGEffect=TrueManualLights=TrueGyroDrift=FalseCrashWithDyn=FalseCrashDetection=FalseAutoTrim=False[sIM]SYSCLOCK=1[sTARTUP]DEMO=0SHOW_OPENING_SCREEN=1STARTUP_DEMO=LoadWindow=1[FACILITIES]COUNTRY=STATE=CITY=GTL_BUTTON=1264[Misc]Com_Rate=7[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[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[MULTIPLAYER]condAccoutPassword=0---------------------------------------------end of fsx.cfg---------------------Inspector's screenshot: ( btw sparse grid is the only thing that removes shimmering here).

Edited January 25, 201214 yr by MindYerBeak

Hey Vic; Yeah - there's a couple of things which impact stuttering, that I would change:[Graphics]GROUND_SHADOWS=1 <- make it '0'[Display]UPPER_FRAMERATE_LIMIT=0 <- This is only good if you are using an external limiter, that's why I suggested the newer version of "Inspector" - it does do this, and along with the newer gpu driver - will yield an extra 3-5 fps.[Weather]CLOUD_DRAW_DISTANCE=5 <- Make this '3'DETAILED_CLOUDS=1 <- Make this '0'CLOUD_COVERAGE_DENSITY=8 <- Pull this down a tad.[Main]FIBER_FRAME_TIME_FRACTION=0.18 <- Put this line into Main. It will make her much smoother. 0.33 is default. If you fly fast and low you may get blurries, and if so - move it up to 20, and then 22, etc.[Traffic]AirlineDensity=61 <- KILLER! Bring back it to 35 if doing 'tube' flight. Make it 10 if doing a GA flight.GADensity=31 <- Make 10 if doing tube flight. Make it 35 if doing GA flight.ShipsAndFerriesDensity=17 <- Make '0'. 10 max.LeisureBoatsDensity=18 <- Make '0'. 20 max if GA around Orcas Island, for e.g. [Terrain]LOD_RADIUS=4.500000 <- Make 3.5MESH_COMPLEXITY=100 <- down a tadWATER_EFFECTS=4 <- Make this '6', a heck of an improvement with v. little hit. (Bojote)Re the Inspector:-Texture Filtering Quality <- Make this one "High Performance"and limit the frames to 30. It will make a difference when combined with these other settings.These changes should all be done first, all at the same time, Vic, as doing so will improve it: your speed is good enough to give you smooth. Then push the ones that you like (like the ship & boats, 4.5 LOD, etc) slowly upwards.There may be other changes you can do, but do these first, then come back. Cheers.

Will do as you suggest. Thanks a ton Paul J.

DETAILED_CLOUDS=1 <- Make this '0'

I agree with everything except the above. By making that 0, you remove all 3D clouds, which is really a very drastic step. The only people who should be using simple clouds are people with really, really old machines. Turning this off on a machine like the OP's is really a bit mad.

To BFG: We're trying to get rid of stutters: let's bring him back to a base where they don't exist - then he can add whatever he considers necessary, and, in any event - 3d clouds may not be Vic's cup of tea - he might want those ships, instead!... and when I'm trying to help someone - I DON'T appreciate the suggestion that I'm being "mad". Keep your personal insults to yourself.

Edited January 25, 201214 yr by Paul J

Paul J,I tested your settings and changed a little bit here and there. I tested on a few flights back and forth egll-lfpg with my pmdg ngx using uk2000 egll and aerosoft lfpg addon and as2012.I had cloud draw at 60, detailed coulds on and cloud coverage max.I had traffic as you suggested.I had fiber frame*.* at 0.18 and lod_radius at 3.5I had mesh comp*.* at 100water effects at 6.Inspector's Texture Filtering Quality on high performance.For some reason after I made those changes to the *.cfg the inspector's limiter did not work anymore and so I used the internal one.The stutters when looking out the side windows are still there tho.Less of them but more pronounced.If I look down at the terrain the buildings "shake" a little bit.(earthquake-like).Thanks for your help anyway.It's appreciated.Vic

Edited January 26, 201214 yr by MindYerBeak

That's too bad, Vic: certainly, cloud coverage at Max will pull it down some; heavy cloud has a similar effect to high traffic settings.I don't know why the Inspector should not work: You might ask Inspector support for this. My internal FSX setting is 'unlimited', with the Inspector setting at 30, and it stays there for the most part: never more than 32, never less than 28, and certainly more stable that FPS_Limiter02 did.OK - still in the testing mode, Vic - I'd still suggest the cloud density backed off a bit, and then - as Johan P. suggested - add this to the cfg, and run FSX again. At 4.27gig with a 480 you might be able to use it.[bufferPools]UsePools=1PoolSize=8388608RejectThreshold=1048576 // 524288 // 262144 // 131072 IF the 1048756 makes an improvement - try the next size down.//PoolSize=0 <--- the 480 is not powerful enough to handle a complete data stream: the processor will have to buffer the larger pages to memory.

While we're talkng about buffering, reading Belopez's post and others - here's some solid info, gleaned from MS - and possibly Bojote, that is worth reposting:-TEXTURE_BANDWIDTH_MULT and BUFFERPOOLS.TEXTURE_BANDWITH_MULT (Edit - this is in [DISPLAY], not [GRAPHICS] )The mysterious sounding TEXTURE_BANDWITH_MULT is our first target. This is a setting in the [DISPLAY] section of the file, formatted like this:

[DISPLAY]

TEXTURE_BANDWIDTH_MULT=n

Where n can range from 10 to some reasonable value that is related to your frame rate limit.From Rafael Cintron, member of the FS Graphics and Terrain team, comes this description:

“The TEXTURE_BANDWIDTH_MULT option in the Graphics section is the target frame rate use for calculating texture bandwidth. The higher you set this value the more textures we will allocate and copy per frame to the graphics card. The lower you set this value, the less we will allocate and copy up to a minimum limit. As an example, the default rate in the “high” perf bucket setting is 40. The lowest perf bucket setting is 10.

Higher settings on this flag can cause stutters on frames where the terrain system has finished compositing lots of textures. Lower settings can reduce stutters on busy frames and spread out the load across multiple frames“

So thinking this thru, if the value you set is 40, and your frame rate limit is 30, then we will send 40/30 or 4/3 as much textures per frame.Moving this value to 400, like I have seen some users post in the forums, is probably *not* what you want to do since that increases the texture load on the graphics card by 10x, eg 400/40 = 10x. And after talking about this to Raf, setting it to 0 is ignored and can be validated by setting it to 10 which should give no different results.BUFFERPOOLS[bUFFERPOOLS] is a section of its own in the fsx.cfg file. There is a setting in there called Poolsize, as in[bUFFERPOOLS]Poolsize=nWhere n is the amount of bytes we will allocate for one pool of vertex and index buffers (storage within memory) to store geometry.Again from Raf:“In RTM, the default setting was 1MB (1000000). The lower this number, the more pools the allocator will have to rummage through to find space for buffers and the more stutters you may have. In Sp1, we raised the default to 4MB (4000000) and optimized the underlying algorithm for finding free buffers“So be careful here, making this smaller can hurt you, since searching for space takes time and can cause stutters, and making the number too large can waste space. 4-10m is probably the range to be thinking about using unless you have a very high memory graphics card ( >512 )Lastly - a small tad from Quest Software's presentation on DB2 BufferPool Tuning:-Q: With so many tuning areas to focus on why should we pay special attention to the buffer pool?A: DB2 uses the buffer pool to offset the performance disparity between CPU and disk, so they are vital for optimizing transaction throughput. From the 8.2 Admin Guide: Performance:“Because most data manipulation takes place in buffer pools, configuring buffer pools is the single most important tuning area.”Modern, high performance gpu's (generally) have much larger memory capacity than the older units, plus they have their own processing system, and so - provided it's fast enough - there is a lesser need for the central cpu to employ any kind of buffer so that it can manipulate video data: the gpu can do it - but only a). if the cpu can get and pass that data fast enough, and :(. if the gpu can 'manage' it at the same rate - or even faster. As Raf says, BP of 8 - 10MB should be fine for most pc's. Smaller - or none if the gpu is faster than the cpu, and larger if it's not: this is why a 580 and newer can handle a 'no pools' situation - although - as the cpu starts pushing >4.5gig - that situation can change.

Edited January 26, 201214 yr by Paul J