Hi there,i was wondering with new pc configuration like mine :ASRock 1155 P67 Pro3 SE B3 P67 DDR3 ATXSAMSUNG 500GB HD502HJ 7200rpm 16MB Spinpoint F3DDR3 1600Mhz PC12800 8GB Corsair Vengeance Low Profile 1.5V CL9 (2x4GB)ATI HD6950 MSI 2GB Twin Frozr IICorsair FORCE Serie 3 60GB SATAIII rtCorsair Enthusiast Series CMPSU-650TXV2EU V2 650WIntel Core i5-2500 3.3Ghz 6MB 1155 Sandy Bridge con GPU 95W BOXThermaltake Element T Casei would need an fps external limiter installed or there is a way i can set it on my graphic card by tweaking softs? if there are any?

I use the free version of Bandicam, it works just fine for an fps limiter. Plus you can activate/deactivate the limiting with the click of a button any time you want in the sim.

nice thanks, i ll try that

I've seen mention of often of a FPS limiter, why are they needed for FSX? What's the big deal if you get +55fps?

fsx runs way better in unlimited fps but uses too much cpu. therefore an external fps limiter to lock the fps to 30 will solve the problem

I've seen mention of often of a FPS limiter, why are they needed for FSX? What's the big deal if you get +55fps?

Interesting! Please, Bumpy - show us fully what your GPU driver settings are, what your hardware is, your bios settings, where and how you're achieving 55, and then post your cfg and some links to the screenshots of all of those settings - and that happening over Seattle. We need some sort of definitive tutorial about "how to do this", as these forums are full of hints, tips and suggestions from folks like ******* Altuve, Nick Needham and others, as to how to do this - but none of them will give the55 that you're claiming.

Interesting! Please, Bumpy - show us fully what your GPU driver settings are, what your hardware is, your bios settings, where and how you're achieving 55, and then post your cfg and some links to the screenshots of all of those settings - and that happening over Seattle. We need some sort of definitive tutorial about "how to do this", as these forums are full of hints, tips and suggestions from folks like ******* Altuve, Nick Needham and others, as to how to do this - but none of them will give the55 that you're claiming.

I think your not understanding the point of his post.

My answer would be that if you are happy with the way FSX works for you, you do not needany limiter.Many have found that there are situations where the framerates can swing wildly, which resultsin micro-stuttering. At that point a limiter (internal or external) improves the situation.Personally, I just set fps at 30 within FSX, others swear by external limiters - whatever works for you!

I've seen mention of often of a FPS limiter, why are they needed for FSX? What's the big deal if you get +55fps?

I understand his post very well: by implication - he is getting 55fps.. "What's the big deal?" . As I read it - it sounds (to me) as if getting 55fps is very much a trivial endeavour, and of course, it isn't. If I did mis-read it, then I apologise.No-one gets 55 fps unless everything is turned way down - or they're measuring over a desert - or they're bluffing. Hitting 55 will normally happen if you're set to 'unlimited' frames, and then they bounce around - anywhere from 18 all the way up to 65 - 70 or so. The symptom is random hesitations, stuttering and smoothness - all very random, and unpleasant. By limiting the OS to 30, one allows the cpu to devote more cpu cycles to the running app - FSX.As Bert says - limit it internally and forget about the Limiter - personally I do something similar, which has - for me - worked better yet: I limit the OS to 30, using NVidia INspector, and then limit FSX to 26fps internally. The more usual situation - the external limiter and unlimited within fsx - though, does work where a low-to-mid-range cpu is matched to a mid-range gpu, as even small tweaks are more noticeable in the mid-range system, and not so much in the high-end system.Below is my Single Piston (for FSUIPC purposes) with the 'normal' stuff removed, the Twin_Piston being similar.// Single_Piston.cfg[GRAPHICS]AC_SELF_SHADOW=0SHADER_OPTIMIZE=1SHADER_CACHE_PRIMED_10=1693458462SHADER_CACHE_PRIMED=1693458462AIRCRAFT_REFLECTIONS=1AIRCRAFT_SHADOWS=0COCKPIT_HIGH_LOD=1GROUND_SHADOWS=0HIGHMEMFIX=1LANDING_LIGHTS=1NUM_LIGHTS=8SHADER_CACHE_VERSION=30SHADER_PARTIAL_PRECISION=1STALE_BUFFER_THRESHOLD=24EFFECTS_QUALITY=2TEXTURE_MAX_LOAD=1024TEXTURE_QUALITY=3[sOUND]SOUND_QUALITY=2[JOBSCHEDULER]AffinityMask=15[bufferPools]UsePools=0//PoolSize=850000000 //8388608//RejectThreshold=921440 // 131072 // 524288 // 262144 // 131072//PoolSize=0[Display]TEXTURE_BANDWIDTH_MULT=157TextureMaxLoad=6 //30 // 30 ONLY when running 'unlimited' frames.UPPER_FRAMERATE_LIMIT=26WideViewAspect=True[Main]DisablePreload=1FIBER_FRAME_TIME_FRACTION=0.18ProcSpeed=15505PerfBucket=7[Weather]AdjustForMagVarInDialog=1CLOUD_COVERAGE_DENSITY=8CLOUD_DRAW_DISTANCE=4DETAILED_CLOUDS=1[DISPLAY.Device.NVIDIA GeForce GTX 580.0]Mode=3840x1024x32TriLinear=1[TextInfo.1] // Red info print at top-left corner - Shift-ZLockedFrameRate=1,1FrameRate=1,2[TextInfo.2]Altitude=1,1Heading=1,2AirSpeed=1,3FuelPercentage=1,4GForce=1,5WindDirectionAndSpeed=2,1[TextInfo.3][slewTextInfo.1] // Red info print at top-left corner when slewingAirSpeed=1,5Altitude=1,3Heading=1,4Latitude=1,1Longitude=1,2[uSERINTERFACE]SITUATION=C:UserspjDocumentsFlight Simulator X FilesChip at Diamond Point[sCENERY]DAWN_DUSK_SMOOTHING=1IMAGE_COMPLEXITY=5LENSFLARE=0MAX_ASYNC_BATCHING_JOBS=3MissingLibraryAlert=0//SmallPartRejectRadius=4.0[TrafficManager]AIRPORT_SCENERY_DENSITY=2AirlineDensity=47ChangeTime=4.000000FreewayDensity=21GADensity=47IFROnly=0LeisureBoatsDensity=14ShipsAndFerriesDensity=0TransitionTime=4.000000[TERRAIN]AUTOGEN_DENSITY=5DETAIL_TEXTURE=1LOD_RADIUS=4.500000MAX_DETAIL_TEXTURE_LEVEL=21MESH_COMPLEXITY=100MESH_RESOLUTION=24MIN_DETAIL_TEXTURE_LEVEL=21SWAP_WAIT_TIMEOUT=2TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=900TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=2000TEXTURE_RESOLUTION=29WATER_EFFECTS=6

I understand his post very well: by implication - he is getting 55fps.. "What's the big deal?"No-one gets 55 fps unless everything is turned way down - or they're measuring over a desert - or they're bluffing. Hitting 55 will normally happen if you're set to 'unlimited' frames, and then they bounce around - anywhere from 18 all the way up to 65 - 70 or so. The symptom is random hesitations, stuttering and smoothness - all very random, and unpleasant. By limiting the OS to 30, one allows the cpu to devote more cpu cycles to the running app - FSX.

You are correct, but I dont think he is claiming he is getting 55fps all the time. He is asking what the advantage is of using a limiter versus running the sim without one. I have found using the internal limiter set to 30 gives me the smoothest and best looking sim. I get wild fps flucuations and blurry scenery using an external limiter. Like Bert said whatever works best for u.

[Display]TEXTURE_BANDWIDTH_MULT=157TextureMaxLoad=6 //30 // 30 ONLY when running 'unlimited' frames.

Paul, I am curious with the relationship and values i.e. 157 and the 6Most have used rather rounded numbers for TBM and 157 stood out to me as a little out of the mainstream. Also TML. I know this is one of the entries the Bojote came up with but never understood what it did nor it's relationship to TBM if there is a relationship at all.Sorry to hijack this one somewhat but just curious.Bob

Hi Bob; yeah - 157 is calculated, with the results posted here at the DigitalThemePark:-https://docs.google.com/spreadsheet/ccc?key=0ApGi-6dY72QqdG1DaXp6YlRWRjg2eFRxdGE1aVhoNXc#gid=10Mine is the #3 down from the top. It's an interesting spreadsheet. I think ******* posted the original calc, and I have to look it up to find it, so give me ten and I'll get back here.

If I did mis-read it, then I apologize.Apology accepted. I was just making an example is all. The symptom is random hesitations, stuttering and smoothness - all very random, and unpleasant. By limiting the OS to 30, one allows the cpu to devote more cpu cycles to the running app - FSX.As Bert says - limit it internally and forget about the Limiter - personally I do something similar, which has - for me - worked better yet: I limit the OS to 30, using NVidia INspector, and then limit FSX to 26fps internally. The more usual situation - the external limiter and unlimited within fsx - though, does work where a low-to-mid-range cpu is matched to a mid-range gpu, as even small tweaks are more noticeable in the mid-range system, and not so much in the high-end system.Thanks for the info, explains what I wanted to know.

I have found using the internal limiter set to 30 gives me the smoothest and best looking sim. I get wild fps flucuations and blurry scenery using an external limiter.

I also get not wild but at least some fluctuations with external limiters so as long as your computer can steadily produce at least 30 fps then I agree the internal gives the best result. However, when using really cpu-intense add-ons like PMDG's I sometimes get as much as 20% more fps when setting FSX to unlimited so to me it's worth a small amount of stuttering.I haven't noticed any blurry textures though but maybe that's just because I haven't thought about it. Will take a look at that later.

PaulWhy the AM=15 entry when 15 is the default (all 4 cores on)?With AM=15, sitting on a taxiway at KSEA, the landing AI seem jerky and artifacts in the smoke. With AM=14 everthing smoothes out/OP: Using a external limiter, locked at 30, workks best for most people. When you know more about it, then you can play with it.Have funDave