Sign in to follow this  
Noah101

Locked or Unlimited FPS

Recommended Posts

Help AVSIM continue to serve you!
Please donate today!

The ultimate answer is test it out on your machine and see.  With that said, I think there is some thought it seems that P3D does better with locked FPS that help limit micro stutters.  The effect of using the built in frame rate limiter is also not as dramatic.  I remember in FSX I'd lose 10-12 FPS with a locked frame rate vs unlimited, in P3D, it only seems about 1-2 FPS for me.

Share this post


Link to post

Which is the best option?

 

If there was a best option it wouldn't be optional :wink:

  • Upvote 1

Share this post


Link to post

I had been using unlimited since there was a significant drop in frame rates if I set it to anything else.  But I would get very bad blurry ground textures.

 

Now I set FIBER_FRAME_TIME_FRACTION=0.01, change frame rate limiter to 26 and also use NVIDIA inspector to lock frame rates to 26, which has been working well for me.  Don't get blurry textures, don't get frame rate drop, and don't get tearing.

 

i5-2500K with GTX-970.

Share this post


Link to post

I had been using unlimited since there was a significant drop in frame rates if I set it to anything else.  But I would get very bad blurry ground textures.

 

Now I set FIBER_FRAME_TIME_FRACTION=0.01, change frame rate limiter to 26 and also use NVIDIA inspector to lock frame rates to 26, which has been working well for me.  Don't get blurry textures, don't get frame rate drop, and don't get tearing.

 

i5-2500K with GTX-970.

I have same CPU/Video card as you.  Are you using an affinity mask at all?  I'm currently running with unlimited and then adaptive half sync in Nvidia Control Panel and also at 2x DSR.  But certain situations cause a barely acceptable situation.

 

Yesterday, for instance, I had stutters and tried messing with all kinds of display settings in P3D but couldn't find anything that would help it.  The next flight though is smooth and no problems.  But, different time of day.  For me, I seem to have issues at times of day where the sun is the highest in the sky and/or I'm closer to tropical latitudes.  I can fly in Orbx EU Norway and maintain a smooth performance all the time.  But then a flight to GCLP(which was where I was going to yesterday) will stutter.  Can't quite pin down why yet.  I'll maybe give these settings you use a try once and see what happens for me too.

Share this post


Link to post
 
 

 

 


have same CPU/Video card as you. Are you using an affinity mask at all? I'm currently running with unlimited and then adaptive half sync in Nvidia Control Panel and also at 2x DSR. But certain situations cause a barely acceptable situation.

 

I'm using all 4 cores. I do get some stutters around very high detailed airports, but not too bad.  I'm also using UT2 with pretty much all major airline liveries and GA traffic assigned.

 

I end up making compromises depending on what type of flying I'm doing so I can keep frame rates in the range of 20-26 fps.  If I'm flying PMDG 737, then I disable ORBX, GA traffic, and road/water traffic, but set airliner traffic at 100%.  If I'm flying a GA airplane, then I enable ORBX and GA traffic, but dial down airliner traffic significantly. 

 

I use SimStarter to set up scenarios so all the necessary settings (including UT2 settings) are tweaked automatically.

 

I also took the radical step of reducing all my default ground textures from 1024x1024 to 512x512.  I don't recommend this, but based on the type of flying I do, which is either GA flying in ORBX regions or long haul flights at high altitude, it works for me.  I actually have it set up to automatically switch back and forth between 512x512 and 1024x1024 using SimStarter, but I pretty much just stick with 512x512.

 

Oh, and I'm using a 43" monitor set at 3840x2160 :)

Share this post


Link to post

I had been using unlimited since there was a significant drop in frame rates if I set it to anything else.  But I would get very bad blurry ground textures.

 

Now I set FIBER_FRAME_TIME_FRACTION=0.01, change frame rate limiter to 26 and also use NVIDIA inspector to lock frame rates to 26, which has been working well for me.  Don't get blurry textures, don't get frame rate drop, and don't get tearing.

 

i5-2500K with GTX-970.

How did you limit the framerate to 26 in NVI ?

The lowest I have found is 29 and I would like to go a little lower...

Share this post


Link to post
 
 

 

 


How did you limit the framerate to 26 in NVI ?
The lowest I have found is 29 and I would like to go a little lower...

 

Open CustomSettingNames_en-EN.xml with a text editor and look for the following.  You can add custom settings.  See below for some examples.  I just changed some that I will never use to values that I want.

 

Not sure if it's just a placebo effect, but setting NVI frame rate to match what I have P3D set to seems to fix the bad ground texture tearing that I see otherwise.

 

 <CustomSetting>
      <UserfriendlyName>Frame Rate Limiter</UserfriendlyName>
      <HexSettingID>0x10834FEE</HexSettingID>
      <MinRequiredDriverVersion>280.26</MinRequiredDriverVersion>
      <Description />
      <GroupName>Sync and Refresh</GroupName>
      <SettingValues>
        <CustomSettingValue>
          <UserfriendlyName>Off</UserfriendlyName>
          <HexValue>0x00000000</HexValue>
        </CustomSettingValue>
        <CustomSettingValue>
          <UserfriendlyName>29 fps</UserfriendlyName>
          <HexValue>0xF000001D</HexValue>
        </CustomSettingValue>
        <CustomSettingValue>
          <UserfriendlyName>30 fps</UserfriendlyName>
          <HexValue>0xF000001E</HexValue>
        </CustomSettingValue>
        <CustomSettingValue>
          <UserfriendlyName>31 fps</UserfriendlyName>
          <HexValue>0xF000001F</HexValue>
        </CustomSettingValue>
        <CustomSettingValue>
          <UserfriendlyName>22 fps</UserfriendlyName>
          <HexValue>0xF0000016</HexValue>
        </CustomSettingValue>
        <CustomSettingValue>
          <UserfriendlyName>24 fps</UserfriendlyName>
          <HexValue>0xF0000018</HexValue>
        </CustomSettingValue>
        <CustomSettingValue>
          <UserfriendlyName>26 fps</UserfriendlyName>
          <HexValue>0xF000001A</HexValue>
        </CustomSettingValue>
        <CustomSettingValue>
          <UserfriendlyName>28 fps</UserfriendlyName>
          <HexValue>0xF000001C</HexValue>
        </CustomSettingValue>

Share this post


Link to post

In complex aircrafts i seem to have better results with unlimited frames. I have gtx980ti xtreme, 6700k @4.7ghz and 16gb ddr4.

Share this post


Link to post

i would say unlimited. My fps is cut to 60% in complex aircraft using limited

 

smooth enough for me using unlimited.

 

2 X GTX970SC

I7-47770k@4.6 ht on

 

Michael Moe

Share this post


Link to post

Why do we lose FPS when using the built in frame limiter?

 

Is it better if you leave that at Unlimited by use the NVIDIA frame limiting options?

Share this post


Link to post

 

 


Why do we lose FPS when using the built in frame limiter?

 

Unlimited will prioritize high frame rates over scenery generation, so you might end up with blurry ground textures, autogen not filling in fast enough when you are flying really fast, etc.  If you limit the frame rates, then more CPU cycles are given to scenery generation, which results in lower frame rates.  If you are happy with your scenery, then I would leave it set to unlimited.  If you have issues with scenery, then try limiting it.

 

FIBER_FRAME_TIME_FRACTION=???

This setting also is part of it.  If you set to unlimited, this setting is ignored.  If you limit the frame rates, then this setting applies and will determine how many CPU cycles are given to scenery generation.  For me, setting FIBER_FRAME_TIME_FRACTION=0.01 is a good compromise and improves scenery generation without much impact on frame rates.

 

Unlimited might also result in ground texture tearing on some setups.

Share this post


Link to post

Unlimited will prioritize high frame rates over scenery generation, so you might end up with blurry ground textures, autogen not filling in fast enough when you are flying really fast, etc.  If you limit the frame rates, then more CPU cycles are given to scenery generation, which results in lower frame rates.  If you are happy with your scenery, then I would leave it set to unlimited.  If you have issues with scenery, then try limiting it.

 

FIBER_FRAME_TIME_FRACTION=???

This setting also is part of it.  If you set to unlimited, this setting is ignored.  If you limit the frame rates, then this setting applies and will determine how many CPU cycles are given to scenery generation.  For me, setting FIBER_FRAME_TIME_FRACTION=0.01 is a good compromise and improves scenery generation without much impact on frame rates.

 

Unlimited might also result in ground texture tearing on some setups.

 

 

But why is someone using an external limiter from NI for instance. What advantage should that bring to the table ?

 

 

Thanks

 

Michael Moe

Share this post


Link to post

 

 


But why is someone using an external limiter from NI for instance. What advantage should that bring to the table ?

 

Might help if you disable v sync and have really bad texture tearing.  At least it seems to help for me.

Share this post


Link to post

To get smoothness with locked FPS you need to set the slider to half of what you get (the minimum possibly). Which means if you get 30fps at a dense area with heavy scenery and ai traffic such as EGLL with unlimited, you have to set 15 fps locked to get the best performance.

 

Which is why I've stopped using locked FPS, at least internally. 

Share this post


Link to post

You dont set your fps limiter to half of your unlimited fps AFAIK, but to half of your monitors refreshrate (30 if your monitor is 60 hz). If your fps dips below 30, you will have stutters if I understand this correctly.

Share this post


Link to post

Why do we lose FPS when using the built in frame limiter?

 

Is it better if you leave that at Unlimited by use the NVIDIA frame limiting options?

Unlimited automatically uses FFTF=0.01 internally.

Therefore it will give better framerates than a locked version.

Only when adding FFTF=0.01 manually it will be equal.

 

I choose to use Unlimited + VSync icw the Frame Rate Limiter from NVI.

Also I made a modified Limiter entry, 25 and use that ( 3 outside view screens ).

My monitors also are running at 25 Hrtz.

 

Now I have everything smooth, also at detailed addon airports with AI traffic and 4 cloudlayers ( max )

Share this post


Link to post

You dont set your fps limiter to half of your unlimited fps AFAIK, but to half of your monitors refreshrate (30 if your monitor is 60 hz). If your fps dips below 30, you will have stutters if I understand this correctly.

 

Well yes but that is considering you get 60 fps unlimited. Locked FPS supposedly renders the look ahead frames/buffer (from what I gather in other threads its about 2x the frames) which is why it gets stuttery or not smooth if you set it simply to half your monitors refresh without having the performance to hit 30fps.

 

You may get 30fps unlimited but as soon as you use locked its going to drop even further regardless of your monitor's refresh rate if you get what I mean.

 

So up in the air you may get 30 locked and smooth but once you approach some heavy scenery its back to 20fps and stutters . Whereas with unlimited you get maybe 60-70 fps in the air and on approach it still maintains 30fps.

Share this post


Link to post

Gerard

 

I recently found by using Nvidia Inspector to externally limit frame rate to 30 fps while running P3D internally on unlimited with vsync and tripple buffering on my blurries were dramatically reduced. Prior I was not using the external limiter and was fighting blurries no matter what I tried. By the way I run a 30Hz 4K monitor and can maintain 30+ fps so vsync is useful.

 

Can someone explain what is going on when you set unlimited in P3D but externally limit frames to 30 fps?

 

Additionally there are at least 2 sets of frame limiter numbers under the P3D profile in the latest NI options 30 fps (v1) and 30 fps (v2) does anyone know the diffrence in these choices, are they version 1 and 2 of P3D and there is no version 3 option?

 

Joe

Share this post


Link to post

 

 


Can someone explain what is going on when you set unlimited in P3D but externally limit frames to 30 fps?

 

And vise versa.

 

Thanks.

Jeff

Share this post


Link to post

I've tried all options in the past limiting the FPS using the built-in limiter, external limiters, different affinity masks, HT enabled/disabled and I always fall back to unlimited FPS, HT disabled and no affinity mask since this gives me the best FPS and still 100% smooth.

 

This is using a 980 Ti and a 6700K @ 4.5 GHz doing all my flying in the NGX with all global Orbx stuff, AS16 weather and lots of payware airports.

  • Upvote 1

Share this post


Link to post

Which is the best option?

 

Specs - GTX 980TI, i5-4460, 8gb ram

Have you checked out the AVSIM P3D Guide?  There are several pages where FPS are discussed (pages, 7, 28, 44, 45, 47-49, 70, 71, 78-80, 107, 111, 139, and most importantly, in Performance on pages 146 and 147).  The guide also discusses the FFTF tweak and its impact on FPS.  Lots of excellent ideas from users above but I would also check out the guide as it discusses fps depending on video cards too.

 

Best regards,

Jim

Share this post


Link to post

Best for me on an 60 monitor is limit to 30 in NI and set 31 in p3d . Standard vsync on 1/2 refresh in NI. No vsync or tripple buffer in p3d

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this