10 hours ago, spilok said:

1/2 refresh rate under VSync checked in NCP worked quite well for me on a flight this afternoon.  Seems like a viable option for smoothing out P3dv5.  I'm using a 60hz LG 4K monitor (32"), and I set the sim to UNLIMITED.   I expect to keep trying this setting and hopefully it could prove to be the best solution.  Who knows?  It sure is worth trying since it does NOT affect the mouse movement .

Stan

Stan thats exatly how i and many others have it set, in my case for many years it seems to work very well 

Adding to Noel's advice I would say this. Find your most demanding airport and slew up to 500ft in your favourite aircraft.

Now slew slowly through 360 degrees noting the load on CPU1 and GPU. Any time CPU1 hits 100% that means your settings are too high for the hardware you have. The ideal monitor refresh rate is 30Hz. If your monitor doesn't support that consider using RTSS 1/2 refresh rate feature. Anything higher than 60Hz is doomed to failure.

As for the 2-3 second pause turn off Road Traffic and see if that helps. It's been improved in v5 but maybe not completely.

You should either turn off Ai during this exercise or limit it to a fixed number of aircraft. Keep weather to a fixed settings of maybe 5/8 cumulus.

Finding and eliminating these performance issues requires the patience of Sherlock Holmes but the key thing is to be organised in how you approach it.

Once you have satisfactory performance at a major airport it should be fine elsewhere although heavy weather will undoubtedly have an impact.

Also, be aware that 80nm from an airport will cause multiple Ai to be loaded into the sim. EGLL, KLAX will cause major stutters for a few seconds. That's unavoidable. If you have means of monitoring Ai numbers that will be helpful. A Lua script running on a WideFS PC interrogating the relevant offsets will show the numbers both airborne and on the ground. I'm happy to share mine for those interested.

3 hours ago, Ray Proudfoot said:

Adding to Noel's advice I would say this. Find your most demanding airport and slew up to 500ft in your favourite aircraft.

Now slew slowly through 360 degrees noting the load on CPU1 and GPU. Any time CPU1 hits 100% that means your settings are too high for the hardware you have. The ideal monitor refresh rate is 30Hz. If your monitor doesn't support that consider using RTSS 1/2 refresh rate feature. Anything higher than 60Hz is doomed to failure.

As for the 2-3 second pause turn off Road Traffic and see if that helps. It's been improved in v5 but maybe not completely.

You should either turn off Ai during this exercise or limit it to a fixed number of aircraft. Keep weather to a fixed settings of maybe 5/8 cumulus.

Finding and eliminating these performance issues requires the patience of Sherlock Holmes but the key thing is to be organised in how you approach it.

Once you have satisfactory performance at a major airport it should be fine elsewhere although heavy weather will undoubtedly have an impact.

Also, be aware that 80nm from an airport will cause multiple Ai to be loaded into the sim. EGLL, KLAX will cause major stutters for a few seconds. That's unavoidable. If you have means of monitoring Ai numbers that will be helpful. A Lua script running on a WideFS PC interrogating the relevant offsets will show the numbers both airborne and on the ground. I'm happy to share mine for those interested.

Seems a little "detailed", to say the least, Ray.  However, I will certainly try this bit of research.

Stan

1 hour ago, spilok said:

Seems a little "detailed", to say the least, Ray.  However, I will certainly try this bit of research.

Stan

There's no obligation Stan. Once you've done it the results make the effort worthwhile. Pete Dowson uses this method.

10 hours ago, Ray Proudfoot said:

Adding to Noel's advice I would say this. Find your most demanding airport and slew up to 500ft in your favourite aircraft.

Now slew slowly through 360 degrees noting the load on CPU1 and GPU

From which view should I slew? Locked spot, spot or VC?

1 minute ago, Luis Hernandez said:

From which view should I slew? Locked spot, spot or VC?

External views are better as more of the scenery is shown. Try Locked spot.

Understood. Should this test be with no frame locks at all (either internal, NCP or RTSS) or it doesn't matter?

22 minutes ago, Luis Hernandez said:

Understood. Should this test be with no frame locks at all (either internal, NCP or RTSS) or it doesn't matter?

It depends on what your monitor is capable of. If it can support 30Hz then use NCP to change to that. Keep frame rate slider in P3D to unlimited and enable Vsync. That will ensure fps goes no higher than 30.

Then adjust scenery complexity to try and maintain 30 during 360° rotation. It may prove impossible depending on CPU/GPU power so aim for minimal time when it drops below 30.

If your monitor cannot run at 30Hz, set it to 60Hz in NCP, same settings as above and use RTSS to set 1/2 refresh rate.

Don't set fps limiter in NCP or RTSS. The monitor refresh rate is the driving force.

Looking at your system spec it may prove very difficult unless scenery sliders are set quite low.

Right now I'm using my laptop display at 60 Hz. However, using RTSS Scanline X/2 pegs Core0 to 100% by default. Either RTSS framerate lock or NCP do not show that behavior (the one useful for testing); so I used either one for tuning my system and then Scanline X/2 for actual flying.

With my display at 60 Hz, it's hard to get a good result as you say, Ray. However, with my display at 50 Hz, it's easier to achieve smoothness and never getting 100% peaks with just 25 FPS using your tuning method. I was shopping for an actual 1080 monitor. I guess I'll need something that can deal with a multiple of 24 or 25. 4K 30 Hz is not an option for me.

On 3/12/2021 at 7:11 AM, Noel said:

Stan, set screen refresh to 30Hz, set frame limit in P3D to UNLIMITED, and turn VSYNC on in P3D--you can also turn on triple buffering if that's till an option in v5.x.  Use all default Global settings in NCP.   There is NO JERKY, no weird mouse lag, nothing but the smoothest flight possible at 30fps, w/ the LEAST amount of work for your CPU & GPU.  The key is setting up P3D and MSFS so you always have some headroom in both CPU & GPU:  ideally, tune settings such that you never see worse than 95% utilization for both, in the most demanding settings.  This method asks your CPU and GPU to only deliver 30fps--because of this you can easily see how much headroom you actually have to work with, which is not the case w/ some other methods.

15 hours ago, Ray Proudfoot said:

It depends on what your monitor is capable of. If it can support 30Hz then use NCP to change to that. Keep frame rate slider in P3D to unlimited and enable Vsync. That will ensure fps goes no higher than 30.

NCP limited to 30 FPS, VSync unlimited in P3D, monitor set at 60 FPS.

Buttery smooth.
Frames didn't even drop below 26 FPS at CYYZ with EA on, overcast weather and 80 AI aircraft. I've never had an experience that smooth with that level of detail on display in Toronto.

Thanks for the recommendation.

1 hour ago, Luis Hernandez said:

With my display at 60 Hz, it's hard to get a good result as you say, Ray. However, with my display at 50 Hz, it's easier to achieve smoothness and never getting 100% peaks with just 25 FPS using your tuning method. I was shopping for an actual 1080 monitor. I guess I'll need something that can deal with a multiple of 24 or 25. 4K 30 Hz is not an option for me.

Dropping to 50Hz has clearly relieved the bottleneck. Excellent! When looking for a suitable monitor go to the manufacturers website for that model and look at Support. You should find the user manual which contains all the supported refesh rates. The better monitors will support 30Hz which makes things simpler. You need a minimum of a 1080Ti for 4K and even then sensible settings are still required.

32 minutes ago, F737NG said:

NCP limited to 30 FPS, VSync unlimited in P3D, monitor set at 60 FPS.

Buttery smooth.
Frames didn't even drop below 26 FPS at CYYZ with EA on, overcast weather and 80 AI aircraft. I've never had an experience that smooth with that level of detail on display in Toronto.

Thanks for the recommendation.

v5.1 is a very different animal to v4.5. You'll get much better performance. Glad it helped. I've just bought v5.1 and am downloading it now. Several days of setting everything up to follow!

51 minutes ago, F737NG said:

NCP limited to 30 FPS, VSync unlimited in P3D, monitor set at 60 FPS.

Buttery smooth.
Frames didn't even drop below 26 FPS at CYYZ with EA on, overcast weather and 80 AI aircraft. I've never had an experience that smooth with that level of detail on display in Toronto.

Thanks for the recommendation.

Near as I can tell using the NCP frame rate limit was not the recommendation, but it sounds like you may be getting a comparable result w/ your screen at 60hz, correct?  I've not tried this because I have a 30Hz capable screen, but I wonder if you also get the benefit of being able to see your realtime CPU and GPU demand with this approach, which you do not get using RTSS x/2 approach.   

47 minutes ago, Noel said:

Near as I can tell using the NCP frame rate limit was not the recommendation, but it sounds like you may be getting a comparable result w/ your screen at 60hz, correct?  I've not tried this because I have a 30Hz capable screen, but I wonder if you also get the benefit of being able to see your realtime CPU and GPU demand with this approach, which you do not get using RTSS x/2 approach.   

I don't understand your comment about not getting realtime figures.

My RTSS  x/2 shows all those figures.

Hi Ian, I will do a screen capture of what I'm talking about sometime later today.

Sorry the red text is hard to read perhaps.   Notice the main thread shows 100% in the first image using RTSS x/2 60hz.  The 2nd image is straight vsync to 30Hz which shows only 55%.  The third image is back to RTSS x/2, however this time at 30hz, so a frame rate of 15.  The main thread still shows 100%.  Therefore, you can't tell how much head room you have using this method, whereas you do using Vsync to 30Hz.   My assumption is even though it's indicating 100%, there is still the same headroom, or not.   It appears as if the CPU is being asked to crank out maximum frames, then the frame limit comes after that.  The issue is you can't tell until your frame rate starts struggling to maintain 30fps.  That's what I was referring to about real time utilization. 

 

 

Edited March 13, 20215 yr by Noel

And it was misleading to call that real time utilization.  What I should have said is w/ RTSS x/2 you can't see how much CPU headroom you have during runtime.