1 hour ago, sho69607 said:

Ok it seems that helped a bit as the screen tearing is gone. However, the fps is going between 28-32FPS and anytime I make turns on the ground I get some non fluid motion/stuttering. Maybe I am not used to using a lower framerate. I will try reducing some more settings and see if that helps.

When using P3D vsync @ 30Hz (or any hz value) and P3D is internally set to unlimited, P3D will flutter its fps around the vsync rate.

For example my monitor is 30 Hz capable and when using the P3D info display for fps I see the value go above and below the 30 fps 30 Hz provides for.

So I don't use the P3D indicator, instead I use the fps counter built into reshade which displays a far more stable fps.

fps momentarily dropping below the Hz rate is usually not a problem unless there is an extended fps drop, then P3D will drop out of vsync where the drop out effect will be somewhat jaring.

The best way to avoid such a drop out of vsync to to have a reserve of fps, that is if you were to disable vsync in P3D it is still able to maintain the Hz fps rate + at least 10% (given 30 Hz = 30 fps, 10% is just 3 fps, ideally 30% is a better amount of headroom).

Getting the reserve of fps though can be tricky and means defining a P3D configuration where such headroom is able to be maintained.

Complex planes and scenery 3D objects will just kill fps and at times you'll not be able to achieve headroom or even enough fps to manage a vsync at all (although I believe the situation is improved with P3D v5.x and the use of Gsync and variable Hz rates would also help), I am still on 4.5. HF3 awaiting version 5.0 to gain stability and updatred addons to reelase, also for new CPU/GFX cards to release and thus build a new PC for the new generations of flight sims coming online.

I've built several different P3D configurations and use whichever one is best suited to the date/time/weather/place/scenery I'll be flying at.

These addtional configs work quite well, and typicaly I'll only need to drop down the AA while in flight to reduce GPU load and thus boost fps.

Also something to be aware of is the way Windows 10 manages fullscreen optomisations can have a detrimetal effect on fps for some apps, P3D appears to be especially effected.

https://devblogs.microsoft.com/directx/demystifying-full-screen-optimizations/

Additonally this thread might also be of use.

Cheers

8 hours ago, sho69607 said:

Ok it seems that helped a bit as the screen tearing is gone. However, the fps is going between 28-32FPS and anytime I make turns on the ground I get some non fluid motion/stuttering. Maybe I am not used to using a lower framerate. I will try reducing some more settings and see if that helps.

Spencer, in order to maintain fluid video using this method it is fairly critical always maintain 30 or greater FPS.  As soon as you start dipping below 30 you will lose the nice fluid video.  Since GPU load also affects the ability to maintain 30 FPS you can monitor GPU load as your flying and adjust sliders (predominantly the lighting sliders) accordingly.   RTSS' on screen display will allow you to monitor everything you need to including GPU load/temp, CPU load/temp etc.  For those fortunate to have a 30Hz capable screen they also can monitor CPU load as well, whereas w/ RTSS that is not useful since the main thread stays pretty much at 100% regardless of conditions.  I found the RTSS/scanline sync to x/2 performed otherwise the same as vsync to 30Hz screen, so you haven't lost much by using the RTSS method.

Unless you're using P3D in windowed mode you will want to 'disable full screen optimizations' in the shortcut that launches P3D.  This caused recurrent rhythmic stutters/shimmers until I learned about this maneuver.

Edited June 18, 20205 yr by Noel