Jump to content

shouldn't we make a glossary page for capping fps?


Recommended Posts

We should have a glossary page about capping / limiting FPS for games, and IMO should be done like http://pcgamingwiki.com/wiki/H1Z1:_King_of_the_Kill#Cap_FPS

 

Motivation: we all know that for most games (except games like CS:GO) achieving a FPS over 60fps (60hz monitor in this case ofc) will make NO difference than having it capped at 60, and causes computers to render frames that never gets used, also causing computers to run hotter and more. I know that v-sync does the job but sometimes you just don't wanna use it.

Link to post
Share on other sites

we all know that for most games achieving a FPS over 60fps (60hz monitor in this case ofc) will make NO difference than having it capped at 60

 

That isn't entirely true. When rendering at a framerate higher than the monitor's refresh rate, the monitor will present frames that are newer at every update than if there was only a single frame rendered every 1/60th (for 60Hz) of a second.

At any rate, http://pcgamingwiki.com/wiki/Glossary:Frame_rate_(FPS) already provides info on capping framerate.

Link to post
Share on other sites

In some cases directly capping the framerate can make the game run worse, sometimes VSync should be used as an alternative method if the game is running worse. (check the frametimes with something like MSI Afterburner to see if they game has micro stuttering)

Link to post
Share on other sites

More frames = more updates = less input lag = less tearing.

Less input lag. But less tearing just isn't true. You will get noticeable tearing somewhere on the screen no matter what if you aren't using Vsync in FSE.

 

Borderless windowed will increase your input lag while still running at an unlocked framerate. DWM will just toss what it wants wherever. So if you run at a very high framerate in BW, you might be able to counter the lag added from DWM Vsync, but the visuals will not be completely smooth.

 

 

The only way to get no tearing with super low latency and high framerates is Freesync/Gsync. A consistent fixed update is still better IMO. Which you can use both to achieve. Cap the framerate with one of them, and you get a consistent smooth and even paced image with all the benefits of not using Vsync at all.

 

You can also try fast sync with a capped framerate of 90,120,150,180,240. Some games it works very well with.

 

 

 

In some cases directly capping the framerate can make the game run worse, sometimes VSync should be used as an alternative method if the game is running worse. (check the frametimes with something like MSI Afterburner to see if they game has micro stuttering)

I'd love to see actual examples of this.

I have never encountered it.

 

 

 

 

Link to post
Share on other sites

Less input lag. But less tearing just isn't true. You will get noticeable tearing somewhere on the screen no matter what if you aren't using Vsync in FSE.

In a broad sense I guess it isn't true that a randomly around 60 FPS game has more tearing than, say 45 or 70 (on a 60Hz screen).

 

But (in particular if we are talking about such a light game as CS) if we have hundreds and hundreds of frames per second, the difference between out-of-refresh frames and the actually on screen image will lower and lower.

And in this way I'm assuming after a certain point one should even stop to mind.

Link to post
Share on other sites

Capping FPS ofc gives the GPU less frames to pick from - introducing input lag.

 

 

 

In some cases directly capping the framerate can make the game run worse, sometimes VSync should be used as an alternative method if the game is running worse. (check the frametimes with something like MSI Afterburner to see if they game has micro stuttering)

 

True, afaik capping FPS using 3rd party software is not any good. I use vsync on games that has no option to set a fps cap.

 

 

That isn't entirely true. When rendering at a framerate higher than the monitor's refresh rate, the monitor will present frames that are newer at every update than if there was only a single frame rendered every 1/60th (for 60Hz) of a second.

At any rate, http://pcgamingwiki.com/wiki/Glossary:Frame_rate_(FPS) already provides info on capping framerate.

 

Yes, expained good in https://www.youtube.com/watch?v=hjWSRTYV8e0

Link to post
Share on other sites

True, afaik capping FPS using 3rd party software is not any good. I use vsync on games that has no option to set a fps cap.

Source?

Even because it seems odd you avoid an issue with one even worser.

 

Besides, you should check this, since not every cap is made equal.

Link to post
Share on other sites
  • 3 weeks later...
Guest
This topic is now closed to further replies.
  • Found PCGamingWiki useful? Please consider making a Donation or visiting our Patreon.
  • Similar Content

    • By MarshallRawR
      L.A Noire FPS Unlocker is a tool made to unlock the framerate to 60FPS. This tool contains parts of Cheat Engine and may be detected by some AVs. Add it to the exclusion of your AV if this happens.
      The tool scans for memory values, patches them and shuts off automatically. This tool should work on any version of the game.
      Instructions:
      Open up the tool Start the game Press F10 to activate the tool. You will hear one beep when it starts, and a different beep when it's done Archive password: pcgw
      --
      Original thread on Steam forums
      Link to the tool's Steam L.A Noire Guide page
    • By Wolfinston
      This is simply a patched .exe from the Steam version of the game that resolves the performances issues, it saves you having to do the hex edit yourself.
      I don't believe it works for the GOG version, but you're welcome to try it out for yourself.
       
    • By tracerhd
      So I've been trying to get this game running at a stable 60 fps but none of my solutions are working. Running it at 130Hz is really bad, at 60Hz it's better but there are still big stutters in free roam. I remember that this game ran fine like 5 years ago. The strange this is that the game wont use my processors power at all.... It's like using one and a half core. I have 6 cores and setting the affinity to even real time is not helping. Tried processor lasso, no luck. Does anyone know a secret solution for this problem? I just want a stable 60 fps nothing more.
    • By Wolfinston
      All credit goes to drennan a gog user I'm simply sharing the mod for preservation purposes.
       
      Drennan made the following mod and said this about it:  
      This mod hides certain elements of the XIII user interface.
      To install, copy HUDFree.u and HUDFree.int into the System subfolder of your 
      XIII folder. In the same folder, edit XIII.ini:
      Replace the value of the DefaultGame key with HUDFree.XIIIHUDFreeGameInfo in 
      the Engine.Engine section of XIII.ini, like this:
      [Engine.Engine]
      DefaultGame=HUDFree.XIIIHUDFreeGameInfo
      Add the following section to XIII.ini to fine-tune what exactly is hidden:
      [HUDFree.XIIIHUDFreeHUD]
      bShowHealth=False
      bShowWeaponsItems=False
      bShowObjective=False
      bShowDialog=True
      bShowEndMessage=False
      bShowSave=False
      bShowPickup=False
      bShowOthers=False
      XIII-HUD-Free-Mod-1.0.1.zip
    • By Keith
      Split/Second patch that removes the 30 FPS limiter and enables the game to run at 60 Hz; it also fixes physics to ensure physics and power plays work. Created by ducon2016.
      Run NoobPatcher.exe Select the unpatched (original) .exe Select "SplitSecond.NoobDiff" Wait for the file to get patched Run the newly created patched .exe
  • Who's Online   0 Members, 0 Anonymous, 396 Guests (See full list)

    There are no registered users currently online

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Forum Statistics

    1,507
    Total Topics
    8,151
    Total Posts
×
×
  • Create New...