Do you use the build in frame limiter in Nvidia Inspector ? I have no issues with it, runs perfectly limited at 30.

 

I didn't actually. Should give that a try.

 

Do you have a link to download ?

 

Cheers.

Do you use the build in frame limiter in Nvidia Inspector ? I have no issues with it, runs perfectly limited at 30.

 

Found it when I googled it.

 

Did what you said and limited it to 30 FPS.

 

Its so stable now, wouldn't of spotted that If you hadn't mentioned it.

 

And its much better than the other external FPS limiter, because its built in and you don't have to keep opening that stupid bat file every time you start FSX if you were using the other external FPS limiter.

 

Cheers for that, another benefit of choosing Nvidea !

Happy enough with the FPS im getting now anyway.

 

Keep any suggestions coming if they haven't been mentioned.

 

I think I gave you all the suggestions you need!?

 

And its much better than the other external FPS limiter, because its built in and you don't have to keep opening that stupid bat file every time you start FSX if you were using the other external FPS limiter.

 

Be aware of external limiters, they tend to cause:

- possible blurry textures, due to limiter also limiting the CPU (from the looks of it in the task manager), thus also limiting the cycles the texture loader is getting on the core0 (a bit technical stuff)

- more stutters than when on internal limiter (proven to be true, but most people are not bothered by it, but you can see every now and then a post popping up with "stutters!!", then just need to ask if internally or externally limited, lol)

 

UK2000 EGLL (high scenery amount) + UTX EU + NGX + REX2 clouds + 4096 textures + 6.5 LOD + AG/Scenery one notch below highest, no AI, no cars, clouds 90nm, bloom off, rest on MAX

 

EI-ROB, listen to Word Not Allowed, he knows what he's talking about! Try his suggestions, he told you everything you need to know. There are tons and tons of tweaks on the internet and most of them are a complete waste of time.

My computer runs at just 3.8 with 2 years old graphics card and I get much better FPS than you. Basically I use the same tweaks as Word Not Allowed, that's why I recommend you to try them.

EI-ROB, listen to Word Not Allowed, he knows what he's talking about! Try his suggestions, he told you everything you need to know. There are tons and tons of tweaks on the internet and most of them are a complete waste of time.

My computer runs at just 3.8 with 2 years old graphics card and I get much better FPS than you. Basically I use the same tweaks as Word Not Allowed, that's why I recommend you to try them.

+1

I can confirm the blurries w/ external limiter.. I was under the impression they were good (externals).. I'm now on team `internal limiter' now. I'll take the trade off for sharp textures over fast framerates and every slider maxed out. I finally decided to tackle my blurries issue.. Started with a Vanilla config and internal limiter of 35. One by one added the few tweaks I actually use and textures remained sharp. My test bed was Seattle Tacoma under Orbx PNW. Then set FSX to unlimited, external limiter to 35 and out came the blurries..

 

Only difference in anything here is external limiter vs internal limiter.

 

Before

 

 

After

 

I have auto overclocked the processor to 4.5 Ghz when its needed, but still have FPS problems at big airports such as ( Heathrow EGLL ) and Charles de Gaulle when using the PMDG NGX. I run most of the graphics on High, but The FPS in the NGX will run under 10 in the flight deck. Is this normal for an over clocked i7 to do this or could I be getting better performance by applied more tweaking ?

 

Will Dunn is correct, Rob; the 550Ti is a slow (for FSX) card compared to the 560Ti, but it's not the only thing which governs your frames - As Kos suggests - Nvidia Inspector set too high will easily cause the same thing in high density areas.

 

My suggestion for that area would be AA Setting - 4 xS and 2 x SS, with AF filtering setting at 8x and Quality set to High Performance. Select TriLinear and uncheck AA in the sim. Lock Inspector at 30 <-- this is where mine is at this moment, with 24 set internally. You need to test this a number of times, running the same flight over and over.

 

You are still going to need to play with many of the settings, as your system will have it's own 'sweet spot', and will be different from other simmer's experiences. My only change from Kos's excellent recommendations - all of them - would be to lower the frame limit into the 20's, along with reducing the TML to 1024 so that your gpu will have some 'breathing space'.

For e.g.

fps = 24

TML = 1024

TBM = 100

 

These figures should give you a better result. You can push the TML to 2048 (more detail)and reduce the TBM to 50. At the lower (24) you are allowing the pc to use the extra time between frames to increase the average throughput - which means not so many dips into the teens.

Keep us posted.

would be to lower the frame limit into the 20's, along with reducing the TML to 1024 so that your gpu will have some 'breathing space'.

 

I would go along that. 25 might be a good solution, though if he offloaded the GPU by lowering the IQ and the texture load, 560ti is going to be singing nicely, there is nothing standing the way of getting a bit more FPS out of that CPU, which is in that more than capable of that. Here just some testing is needed.

 

Oh and btw. PJ, please say(write) Word Not Allowed, not Kos :) That sounds so terrible to me. Thx.

 

I can confirm the blurries w/ external limiter.. I was under the impression they were good (externals).. I'm now on team `internal limiter' now.

 

I was doing one of those hardcore tests here, my blurries testing is with Learjet flying quite fast 3000ft over Megascenery Las Vegas.

After couple of minutes, I would approach some mountains there and could observe blurries taking place, and it was SO obvious. I started this agenda against the external limiter, but you try going versus thousands of posts telling ya that external limiter is awesome! ^_^

The funny thing was, what I observed was that the limiter was somehow limiting the CPU... usually CPU is always running at 100% in FSX, even if you are at peak locked frames. Meaning something ELSE is going on in the background. If you limit it with the limiter, I guess those processes also get limited, and one of those is the texture loader on the main core or cores. I can only explain it to myself like that.

I tend to go around those hundreds of explanations on how things work and test it myself and make opinions myself. But I don't do them (unlike you and me) on some generic flight that I just started. You need exactly those comparison sessions. Least people do those...

I'm glad that finally someone has seen the light!

Oh and btw. PJ, please say(write) Word Not Allowed, not Kos :) That sounds so terrible to me. Thx.

 

haha - No problem, Word Not Allowed. Born in '46, being a Limey, growing up and in the air force - almost everyone had a nickname, and /or a shortened name... just a bad habit, and I can easily break it! I only get upset by being called late for dinner!

haha - No problem, Word Not Allowed. Born in '46, being a Limey, growing up and in the air force - almost everyone had a nickname, and /or a shortened name... just a bad habit, and I can easily break it! I only get upset by being called late for dinner!

 

:lol: Haha, thx.

Completely agree with the testing philosophy, and the cpu's 'other services and processes' also being limited, Word Not Allowed: I'm going to do some more playing with the Inspector limiter turned off, limiting only within the sim. I usually have a single setup default flight - starting in the air and running around Vancouver (Jon Patch/Holger Sandeman's Vancouver Plus, along with Don Grovestine's Victoria 2010 and the OrbX PNW, with 99% of the PNW airports), and it's a very heavy area.

I was doing one of those hardcore tests here, my blurries testing is with Learjet flying quite fast 3000ft over Megascenery Las Vegas.

After couple of minutes, I would approach some mountains there and could observe blurries taking place, and it was SO obvious. I started this agenda against the external limiter, but you try going versus thousands of posts telling ya that external limiter is awesome! ^_^

The funny thing was, what I observed was that the limiter was somehow limiting the CPU... usually CPU is always running at 100% in FSX, even if you are at peak locked frames. Meaning something ELSE is going on in the background. If you limit it with the limiter, I guess those processes also get limited, and one of those is the texture loader on the main core or cores. I can only explain it to myself like that.

I tend to go around those hundreds of explanations on how things work and test it myself and make opinions myself. But I don't do them (unlike you and me) on some generic flight that I just started. You need exactly those comparison sessions. Least people do those...

I'm glad that finally someone has seen the light!

 

I'm always willing to listen.. It's obvious you've been at this longer than I have so until I'm in your shoes I'm just a student.

 

Just did the Learjet test myself. 3,000ft 212kts and not a blurry in sight within the lod radius. :LMAO: With the limiter on the game was barely bothering to load the textures correctly. Like you I saw the blurries happening far out in front of me and would say "Yep, they aren't loading"... Then that area would be right under me and yep.. Still blurry.

 

This is beautiful and I'm still doing fine w/ framerates. I could probably tone it down a notch but all things considering in this very crowded area it was running and looking great.

 

My only complaint using the tips here, is the textures seem to take a little while to load when switching views. how can I help fix this? raise the t_b_m number from 40 to say, 80?

Just went through this thread so let me ask just to make sure of what I am hearing...

 

Word Not Allowed, you are say do NOT use the Nvidia Inspector frame limiter? Use only FSX's limiter to reduce tuxture blurries?

 

And then Paul you set your FPS to something like 24-25? Shouldn't that be 30? I thought the whole idea was to keep it vsync thus 30FPS most attainable as compare to setting at 60.

 

Of course I will try the above myself to see any differences but wanted to ask.

 

Clutch

Completely agree with the testing philosophy, and the cpu's 'other services and processes' also being limited, Word Not Allowed: I'm going to do some more playing with the Inspector limiter turned off, limiting only within the sim. I usually have a single setup default flight - starting in the air and running around Vancouver (Jon Patch/Holger Sandeman's Vancouver Plus, along with Don Grovestine's Victoria 2010 and the OrbX PNW, with 99% of the PNW airports), and it's a very heavy area.

 

Sure, do that. I suggest you play with BP=0, with internal limiter (but please, do limit to something meaningfull, like 30-35fps, depending what your machine is capable of - wishful limiting to 50fps like some others here ^_^ is only going to lead in wrong direction) AND FFTF tweak, going from some 0.2 or 0.15 down. The lower you set, the more frames you are gonna get, but will also sooner or later going to be introduced to heavy blurring and autogenloss. It's a fine balance between good sharp loading and best performance possible.

 

My only complaint using the tips here, is the textures seem to take a little while to load when switching views. how can I help fix this? raise the t_b_m number from 40 to say, 80?

 

Nope. Get faster disk, SSD... or PCIE3. Otherwise I never found ways to really speed up view change loading.

 

Word Not Allowed, you are say do NOT use the Nvidia Inspector frame limiter? Use only FSX's limiter to reduce tuxture blurries?

 

I say, I do not recommend external limiter, correct. I never tested extensively the Nvidia limiter, but I did the previous ones. The one from Nvidia is only causing stutters and same behaviour (but if I feel like it, I'll run it through my scenario later or tomorrow...). And yes, internal limiter.

 

And then Paul you set your FPS to something like 24-25? Shouldn't that be 30? I thought the whole idea was to keep it vsync thus 30FPS most attainable as compare to setting at 60.

 

The reason for lower FPS was due to quite a slow card if he wants to use quality. Still, he could maintain 30fps no problem if proper settings used in Nvidia Inspector. Not something like 8xS + 2xSGSS (discussed on other thread currently).

 

Of course I will try the above myself to see any differences but wanted to ask.

 

If you do, make sure you do it in the controlled circumstances. Testing by "flying and I think it's smoother/sharper" doesn't really count...

 

 

 

 

 

The reason why everyone loves the external limiter is the fact that when you do it like that, you effectively get about 20% more frames, which is nice, but you are introducing other problems.

 

Then many started using BP=0 tweak, WITH the ext. limiter, which is introducing even more problems.

 

Today's cards can manage the BP=0 tweak without real trouble (the only downside might be in really really heavy situations, you might get some minor graphical errors if you are really overloading your GPU).

 

After the problem with BP=0 giving the high boost, but instability, I went onto searching for another solutions. That is when I stumbled upon the FFTF=0 tweak, which caused the same frames as if like you were using ext. limiter. But after quite a short time, discovered that when your FPS drop below locked, you would lose autogen and get extreme blurries.

 

That is when I started experimenting heavily with FFTF and BP=0, and came to the conclusion I wrote earlier...