I limit FFTF to 0.18, Word Not Allowed, - this gives me the smoothest without blurring.

 

Regarding Clutch's comment - I haven't found any multiple of fps limit which makes one iota of difference with regard to syncing to the monitor's refresh rate. One would think that - in limiting to 30 or 60 - in the States/Canada, and/or 25 and 50 in (some parts of) Europe - one would see a marked 'lock' around the power line frequency - but I've never seen that with FSX. It paints frames as per the gpu's ability. Turning on (Force Vsync) vsync in Inspector works very well, while forcing it within the fsx.cfg consumes up to five fps, which is a no-go for most people.

I did run unlimited within the sim for a month or more Clutch, 30 externally but found it better if I did both. I went from 30/30 down to 30/24, and am 'happy' with that at this moment, but now that Word Not Allowed's mention running the OS without limit - I'm going to work with that for a while.. it's worth exploring, as if one can gain a few fps here and there - we can get so much more enjoyment out of the hobby. It's truly a pain in the b*** when it stutters or blurs. We're a lot more fortunate now that the hardware has advanced to the degree where FSX is pretty stable - and capable of delivering the performance and content that we've all been looking for.

Paul, if it works for you, great, but with your system you should be able to go much lower and gain quite a few frames. Try 0.1. You can always get back if it fails

 

For the record, I use no Vsync in windowed, and Vsync on in full screen.

 

We're a lot more fortunate now that the hardware has advanced to the degree where FSX is pretty stable - and capable of delivering the performance and content that we've all been looking for.

 

The pain is though, you still need those tweeks to run all you feed it. I don't think it's ever gonna get better. As our hardware is getting better, so do the aircraft, scenery and all. It's gonna be a long time yet untill we hit the upper limit.

If you want a couple of absolute 'musts' in the cfg - FFTF at around 0.15 to 0.20 is must. If one carries out a series of six or seven very short, 30-second flights over the top of a stuttering 21fps KSEA airport - roughly 3000' with the C172, watching the counter (save the flight as default and then keep loading it, changing the FFTF down from its' 0.33 default in say steps of three each flight) - you will observe a small increase in fps and the sim will become significantly smoother - all the way down to 0.07. The test should then go just north of the city at about 800' in a faster aircraft, looking at the streets: You'll find that after a few seconds or so - they will blur - turning a muddy purple colour. This is when you move the number upwards. 0.15 will do quite nicely as the lower limit.

 

Paul, if it works for you, great, but with your system you should be able to go much lower and gain quite a few frames. Try 0.1. You can always get back if it fails

I assume you're talking FFTF here, right? I've done this one to death, Word Not Allowed. She sits at 0.18 in all my cfg files.

 

For the record, I use no Vsync in windowed, and Vsync on in full screen.

I don't use it at all anymore, Word Not Allowed, since the last few iterations of the driver and the latest Inspector. There is no tearing evident.

 

The pain is though, you still need those tweaks to run all you feed it. I don't think it's ever gonna get better. As our hardware is getting better, so do the aircraft, scenery and all. It's gonna be a long time yet untill we hit the upper limit.

+1

 

I have an ssd, so texture loading should be faster, I see faster loading when I raise the bandwidth multiplier number, just trying to find a sweet spot

Good thread. I'm new to tweaking FSX. Does FSX provide a frame rate counter within the sim or is that a 3rd party add on I see in the screenshot above?

Shift-Z will do it for you, Jason. What you see is configurable in the fsx.cfg, too. Repaet to go to the second one, then there's a third one, too, but I removed it. The SDK gives you a list of the various parameters.

 

[TextInfo.1] // Red info print at top-left corner - Shift-Z

LockedFrameRate=1,1

FrameRate=1,2

AverageFrameRate=1,3

 

[TextInfo.2]

Altitude=1,1

Heading=1,2

AirSpeed=1,3

FuelPercentage=1,4

GForce=1,5

WindDirectionAndSpeed=2,1

 

[slewTextInfo.1] // Red info print at top-left corner when slewing

AirSpeed=1,5

Altitude=1,3

Heading=1,4

Latitude=1,1

Longitude=1,2

Thank you Paul J

I started this agenda against the external limiter, but you try going versus thousands of posts telling ya that external limiter is awesome! ^_^

 

The external limiter is awesome for some because they get much more FPS with it in comparison to internal limiter. For example, some may get 20FPS with internal but 30FPS with external. Yes, they get blurries but the sim appears to be smoother. I think that's why.

Fully correct. You basically trade one evil for the other. What I am trying to do is to find the perfect balance between the two evils. Best possible FPS without least possible loss of FPS. This is what my combo is giving me.

Let me just be short about this:

[JOBSCHEDULER]

AffinityMask=14 <- if you have disabled HT in BIOS, meaning running 4 cores in the task manager

 

Then why does bojote's tool give me affinitymask 14 when I select 8 cores (hyperthreading active) on the site??

I have i7 720qm (4 cores 8 threads in taskmanager...)

Fully correct. You basically trade one evil for the other. What I am trying to do is to find the perfect balance between the two evils. Best possible FPS without least possible loss of FPS. This is what my combo is giving me.

I've been at MAX internal FPS and no external limiter for a while now, and using BP_TOOLS and FFTF and haven't noticed any problems... But that might be because with NGX FPS are never high than 25 anyway :P

Then why does bojote's tool give me affinitymask 14 when I select 8 cores (hyperthreading active) on the site??

I have i7 720qm (4 cores 8 threads in taskmanager...)

 

Don't know, I only know that running 14 on the 8core machine (HT active on a quad) is wrong. Very wrong.

 

I've been at MAX internal FPS

 

What is MAX internal FPS?

What's BP_TOOLS?

FFTF how much?

 

But that might be because with NGX FPS are never high than 25 anyway

 

Generally or yours?

Word Not Allowed,

 

Why do ou say not to use Bojote's tweaks when you suggest most of them ? Which setting is wrong in Bojote's and wh (just for my knowledge) ?

 

Thanks

Because RT tweak was used for slower hardware, before SB. Instead BP=0 with a correct FFTF is IMO a better option.

All other tweaks apart those that I mentioned also have little to no impact on today's systems. So why use a tweak and possibly cause a problem, if you have no real use from it?

Holy Microstutter!!! Word Not Allowed, what have you done to my FSX system, this is the smoothest it's ever been, wow.

 

I'm one of the guilty ones that used various external limiters plus the BP tweak and have gotten very frustrated of stutters. Until today, when I saw this thread and Word Not Allowed's suggestions and voila, I'm currently on my way in the CS 732 from Cleveland to Chicago and it is suuuuuper smooth. For the first time in my 15+ years of simming I don't even want to CTRL-Z anymore, because it does not care if it's that smooth.

 

As a "fsx induced hobby tweaker" I've tried many things, read and researched too many suggestions but I think Word Not Allowed's point about many tweaks applying to older hardware is spot on.

 

Thanks for sharing this again Word Not Allowed, although I'm sure you've shared that a million times already...

 

Cheers,

Pete

Thanks Peter for very kind words. Glad you are enjoying it!