I'm great at 20 and very good at 25 fps too. I don't have 3 monitors so with all my recent HT exploration I should settle on 25 finally. 

I was thinking about UTL but you mentioned you saw some stutters with it. UT2 used to give me some tiny regular micro stutters in FSX-SE so I'm on the fence about it.

Thanks.

Yes that's right but now everything is off 0-1-2 all is perfect again. (Apart from P3d and chaseplane)

Running 6 things on top of P3D and chaseplane at the same time is not a good idea all on the same cores.

3 minutes ago, Nyxx said:

Yes that's right but now everything is off 0-1-2 all is perfect again. (Apart from P3d and chaseplane)

Do you give Chaseplane all 4?

2 minutes ago, Dirk98 said:

Do you give Chaseplane all 4?

yes all, same as P3D 0-1-2-3-4-5-6-7-8

Everything else runs on 3-4-5-6-7-8

2 hours ago, Dirk98 said:

I bought the Booster, but got no time to study it yet. Can't it work changing values automatically according to the preset FPS in it?

 

Thanks

You have to set the value . You can set the slider to another value while flying.

The moment I see blurries in heavy scenery I set the slider more to the left till I am able to fly that scenery without blurries. That value will be the value I immediately use next time I make the same flight. If you look I  an earlier post you will see the Booster values for several arrival airports.

Uimited + FTFF 0.01 was nice when the scenery was not very taxing on the system.

A lower FTFF of 0.20-0.40 will help curing those blurries. Your framerate might drop a little, so make sure that you do not use Everything Maxed Out settings...

This year I am going to built a new pc with an 8-12 core processor , so I can be certain that my triple view system will have enough terrain cores ...

 

1 hour ago, Dirk98 said:

But soon as we move that FPS slider in P3D from Unlimited to ANYthing else P3D gfx engine begins to work in a different way, that requires some additional overhead.

Therefore limiting FPS by using Unlimited+VSYNC ON+Mon.refresh 30Hz (or 20, or 25) should normally be the most efficient performance wise.

 

 

This is the key message. Monitor the primary P3D thread you can see core utilization measurably drop if you set FPS to unlimited. If it's pinned at 100% (as it often is for me when FPS limiter is on) then I'm likely seeing some form of stuttering.  

2 hours ago, odourboy said:

This is the key message. 

SteveW was the source who explained it right and I just imitated ))

 

Hi,

Many thanks everyone for all your enthusiastic input and very helpful advice.

However, that was not really the original intention behind my post at the top of this thread, namely the benefits of rebooting your system before commencing a new flight scenario. A few have confirmed this to be worthwhile, perhaps even mandatory, but it would be nice to hear from other members. In particular, whether this procedure helped to eliminate persistent stuttering that may have appeared during a simming session.

Much of what has been posted has been discussed at length in other similar threads and, to be fair, I may have encouraged these 'off topic' responses with various content in my somewhat lengthy preamble. Still, it's all good stuff and does help to consolidate our understanding of this tricky subject and the methods employed to mitigate and, indeed, eliminate the problem. So, thanks for that!

Regards,

Mike

39 minutes ago, Cruachan said:

Hi,

Many thanks everyone for all your enthusiastic input and very helpful advice.

However, that was not really the original intention behind my post at the top of this thread, namely the benefits of rebooting your system before commencing a new flight scenario. A few have confirmed this to be worthwhile, perhaps even mandatory, but it would be nice to hear from other members. In particular, whether this procedure helped to eliminate persistent stuttering that may have appeared during a simming session.

Much of what has been posted has been discussed at length in other similar threads and, to be fair, I may have encouraged these 'off topic' responses with various content in my somewhat lengthy preamble. Still, it's all good stuff and does help to consolidate our understanding of this tricky subject and the methods employed to mitigate and, indeed, eliminate the problem. So, thanks for that!

Regards,

Mike

Mike , it is even better to shutdown the pc , disconnect power and wait at least 3 minutes before rebooting.

Then you are sure that the mainboard is clean again and that there is no electric current left on it.

3 minutes ago, GSalden said:

Mike , it is even better to shutdown the pc , disconnect power and wait at least 3 minutes before rebooting.

Then you are sure that the mainboard is clean again and that there is no electric current left on it.

I don't think the above is practical. Whereas Mike made a valid point about something that is left in the memory that needs to be reset after a flight and I don't know any other way but rebooting my main PC.

 

I agree with Mike. Of all the tweaking, stuff I have seen over the years, the reboot does better than all of them combined. Must be something either FS or the OS is leaving in memory. I notice they take forever to shut down.

4 minutes ago, Dirk98 said:

I don't think the above is practical. Whereas Mike made a valid point about something that is left in the memory that needs to be reset after a flight and I don't know any other way but rebooting my main PC.

 

I can asure you that sometimes a shutdown is better.

As I am beta tester for several companies I sometimes experience a slowdown in framerate after several times restarting P3D.  Not like it is dropping to half but still.

Just a reboot does not always solve it. A shutdown, wait for a few minutes and then reboot has always solved it for me ...

4 minutes ago, GSalden said:

I can asure you that sometimes a shutdown is better.

Not that I never do a cold reboot. But I always do a hot reboot after a flight if I want to continue.

 

I agree with you Mike and it do kill what i was so happy about going 64 bit. "Finally a return leg option" but stutter or low fps is often the price.

We are back to those saved scenarios that just feels more fresh second time on that approach.

Thanks Michael Moe 

3 hours ago, GSalden said:

I can asure you that sometimes a shutdown is better.

As I am beta tester for several companies I sometimes experience a slowdown in framerate after several times restarting P3D.  Not like it is dropping to half but still.

Just a reboot does not always solve it. A shutdown, wait for a few minutes and then reboot has always solved it for me ...

Hi Gerard,

I'm quite sure you are correct. Warm rebooting or restarting the sim usually doesn't work. To assure success it seems to be necessary to clear RAM memory content completely before starting again.

While this is being proposed as one solution I think it's important to emphasise that you may get away without having to do this during a particular flight sim session. I think much depends on where you fly, the addons in play, the quality of their construction and what is actually being loaded/unloaded into/from memory. I can spend several hours without any issues and a session might include several flight scenarios. However, when the stutters do appear, and I know from experience that previous flights in the same scenario produced no stuttering, then a cold reboot following a short wait (1-3 mins) is the answer.

If time is pressing and you are anxious to resume a session, a quick and effective way to discharge your PC's components of all electrical charges is by disconnecting the power supply, after shutdown, and holding down the power button for approximately 4 seconds.

Doubtless for some of us, all this is probably old news. The rationale behind my original post was to encourage others to at least consider carrying out this simple procedure first before changing settings unnecessarily thereby compounding your frustrations.

Regards,

Mike