Cap your fps people (battlenonsense)

Everything about latency. Tips, testing methods, mouse lag, display lag, game engine lag, network lag, whole input lag chain, VSYNC OFF vs VSYNC ON, and more! Input Lag Articles on Blur Busters.
ATi7500
Posts: 3
Joined: 07 Nov 2019, 09:44

Re: Cap your fps people (battlenonsense)

Post by ATi7500 » 07 Nov 2019, 09:52

Hello guys, new joiner here!

I've got a 60Hz IPS monitor, and I like to play almost exclusively with Vsync ON as I hate tearing.

Onto my questions:
  • Is the Unreal Engine "Framerate smoothing" an efficient framecap?
  • With Vsync ON, does it make any sense to keep it above refresh rate (as default for maxsmoothedframerate is 62)?
  • How come default maxsmoothedframerate isn't 60? What's the reasoning of keeping it 2 frames above?
  • I know that setting a framerate cap below refresh rate at a fixed value (59 with 60Hz) induces stutter every second. Does this happen in both on double buffered and triple buffered vsync?
Thanks in advance!

User avatar
jorimt
Posts: 2481
Joined: 04 Nov 2016, 10:44
Location: USA

Re: Cap your fps people (battlenonsense)

Post by jorimt » 07 Nov 2019, 14:26

ATi7500 wrote:Is the Unreal Engine "Framerate smoothing" an efficient framecap?
In my experience, the Unreal Engine's in-game FPS limiting solution is a good one.
ATi7500 wrote:With Vsync ON, does it make any sense to keep it above refresh rate (as default for maxsmoothedframerate is 62)?
If your purpose is to avoid V-SYNC input lag, no.
ATi7500 wrote:How come default maxsmoothedframerate isn't 60? What's the reasoning of keeping it 2 frames above?
You'd have to ask the devs "why" on that.

But my assumption is when the limiter was originally created, and that value was initially decided on, 60Hz was predominate, and less was known/prioritized regarding V-SYNC input lag.
ATi7500 wrote:I know that setting a framerate cap below refresh rate at a fixed value (59 with 60Hz) induces stutter every second. Does this happen in both on double buffered and triple buffered vsync?
Yes.

So even though UE has a decent in-game limiter, if you're using standalone V-SYNC and want to prevent V-SYNC input lag while avoiding as much recurring stutter from this as possible, you're better off using an RTSS FPS at the decimal level, or some such other V-SYNC-only low lag method over an in-game limiter:
https://www.blurbusters.com/howto-low-lag-vsync-on/
(jorimt: /jor-uhm-tee/)
Author: Blur Busters "G-SYNC 101" Series

Displays: ASUS PG27AQN, LG 48CX VR: Beyond, Quest 3, Reverb G2, Index OS: Windows 11 Pro Case: Fractal Design Torrent PSU: Seasonic PRIME TX-1000 MB: ASUS Z790 Hero CPU: Intel i9-13900k w/Noctua NH-U12A GPU: GIGABYTE RTX 4090 GAMING OC RAM: 32GB G.SKILL Trident Z5 DDR5 6400MHz CL32 SSDs: 2TB WD_BLACK SN850 (OS), 4TB WD_BLACK SN850X (Games) Keyboards: Wooting 60HE, Logitech G915 TKL Mice: Razer Viper Mini SE, Razer Viper 8kHz Sound: Creative Sound Blaster Katana V2 (speakers/amp/DAC), AFUL Performer 8 (IEMs)

ATi7500
Posts: 3
Joined: 07 Nov 2019, 09:44

Re: Cap your fps people (battlenonsense)

Post by ATi7500 » 07 Nov 2019, 15:23

Thanks. Let's say I don't want to achieve the least possible amount of input lag, but settle with a low, constant input lag.
Does it make any difference to set a frame limiter to 60 (refresh rate being 59.9xx) with vsync on, compared not to having any frame limiter at all?

User avatar
jorimt
Posts: 2481
Joined: 04 Nov 2016, 10:44
Location: USA

Re: Cap your fps people (battlenonsense)

Post by jorimt » 07 Nov 2019, 16:19

You'll get a little less input lag with a 60 FPS limit @60Hz, but you won't completely eliminate it like you would with 59 or 59.xx FPS.

The below image has scenarios depicting G-SYNC use, but the first three scenarios (starting from the top) apply to standalone V-SYNC as well in this respect:

Image
(jorimt: /jor-uhm-tee/)
Author: Blur Busters "G-SYNC 101" Series

Displays: ASUS PG27AQN, LG 48CX VR: Beyond, Quest 3, Reverb G2, Index OS: Windows 11 Pro Case: Fractal Design Torrent PSU: Seasonic PRIME TX-1000 MB: ASUS Z790 Hero CPU: Intel i9-13900k w/Noctua NH-U12A GPU: GIGABYTE RTX 4090 GAMING OC RAM: 32GB G.SKILL Trident Z5 DDR5 6400MHz CL32 SSDs: 2TB WD_BLACK SN850 (OS), 4TB WD_BLACK SN850X (Games) Keyboards: Wooting 60HE, Logitech G915 TKL Mice: Razer Viper Mini SE, Razer Viper 8kHz Sound: Creative Sound Blaster Katana V2 (speakers/amp/DAC), AFUL Performer 8 (IEMs)

ATi7500
Posts: 3
Joined: 07 Nov 2019, 09:44

Re: Cap your fps people (battlenonsense)

Post by ATi7500 » 07 Nov 2019, 17:49

Well guess what, just found this in the Engine.ini of a UE3 game

Code: Select all

MaxSmoothedFrameRate=59.990000
Which accepts decimals!

Measured the refresh rate of my Dell U2212HM to be 60.00x Hz, I guess I'm good to go :)

User avatar
jorimt
Posts: 2481
Joined: 04 Nov 2016, 10:44
Location: USA

Re: Cap your fps people (battlenonsense)

Post by jorimt » 07 Nov 2019, 19:29

There's no guarantee it's as stable as RTSS at the decimal level, but you can give it a shot.
(jorimt: /jor-uhm-tee/)
Author: Blur Busters "G-SYNC 101" Series

Displays: ASUS PG27AQN, LG 48CX VR: Beyond, Quest 3, Reverb G2, Index OS: Windows 11 Pro Case: Fractal Design Torrent PSU: Seasonic PRIME TX-1000 MB: ASUS Z790 Hero CPU: Intel i9-13900k w/Noctua NH-U12A GPU: GIGABYTE RTX 4090 GAMING OC RAM: 32GB G.SKILL Trident Z5 DDR5 6400MHz CL32 SSDs: 2TB WD_BLACK SN850 (OS), 4TB WD_BLACK SN850X (Games) Keyboards: Wooting 60HE, Logitech G915 TKL Mice: Razer Viper Mini SE, Razer Viper 8kHz Sound: Creative Sound Blaster Katana V2 (speakers/amp/DAC), AFUL Performer 8 (IEMs)

felic
Posts: 6
Joined: 20 Sep 2019, 12:11

Re: Cap your fps people (battlenonsense)

Post by felic » 22 Dec 2019, 07:17

to what i should set nvidia low latency mode for csgo or games that doesnt use gpu to max with fps uncapped.
ultra seems like it adds more latency in this kind of situation?,should i then use off or on mode?

User avatar
jorimt
Posts: 2481
Joined: 04 Nov 2016, 10:44
Location: USA

Re: Cap your fps people (battlenonsense)

Post by jorimt » 22 Dec 2019, 09:13

felic wrote:
22 Dec 2019, 07:17
should i then use off or on mode?
LLM "On" (MPRF "1") is safe to use in non-GPU-bound situations.
(jorimt: /jor-uhm-tee/)
Author: Blur Busters "G-SYNC 101" Series

Displays: ASUS PG27AQN, LG 48CX VR: Beyond, Quest 3, Reverb G2, Index OS: Windows 11 Pro Case: Fractal Design Torrent PSU: Seasonic PRIME TX-1000 MB: ASUS Z790 Hero CPU: Intel i9-13900k w/Noctua NH-U12A GPU: GIGABYTE RTX 4090 GAMING OC RAM: 32GB G.SKILL Trident Z5 DDR5 6400MHz CL32 SSDs: 2TB WD_BLACK SN850 (OS), 4TB WD_BLACK SN850X (Games) Keyboards: Wooting 60HE, Logitech G915 TKL Mice: Razer Viper Mini SE, Razer Viper 8kHz Sound: Creative Sound Blaster Katana V2 (speakers/amp/DAC), AFUL Performer 8 (IEMs)

User avatar
hleV
Posts: 105
Joined: 27 May 2017, 10:31

Re: Cap your fps people (battlenonsense)

Post by hleV » 23 Dec 2019, 03:01

jorimt wrote:
22 Dec 2019, 09:13
LLM "On" (MPRF "1") is safe to use in non-GPU-bound situations.
Do you know if On is better than Ultra when non-GPU-bound?
BenQ XL2546K @ 240Hz (DyAC+) • ROCCAT Kone Pro Air @ 1000Hz • HyperX Alloy Origins • CORSAIR MM350 PRO Premium • HyperX Cloud Revolver • NVIDIA GeForce RTX 3070 @ 2130MHz/8000MHz • Intel Core i7-8700K @ 4.8GHz • G.SKILL RipjawsV 16GB (2x8GB) 3000MHz CL15

User avatar
jorimt
Posts: 2481
Joined: 04 Nov 2016, 10:44
Location: USA

Re: Cap your fps people (battlenonsense)

Post by jorimt » 23 Dec 2019, 08:46

hleV wrote:
23 Dec 2019, 03:01
jorimt wrote:
22 Dec 2019, 09:13
LLM "On" (MPRF "1") is safe to use in non-GPU-bound situations.
Do you know if On is better than Ultra when non-GPU-bound?
I only know that from Battle(non)sense's test video, it appears "Ultra" may have slightly higher input lag than "On" in non-GPU-bound-situations. But that's in situations without G-SYNC.

Nvidia states that "Ultra" works as a "just-in-time" frame delivery mechanism, at least for non-G-SYNC scenarios. If we're talking about G-SYNC, it already delivers frames "just-in-time," as the display syncs itself to the GPU, so "Ultra" is basically then MPRF "1" + auto FPS limiter instead of MPRF "1" + some sort of non-VRR "just-in-time" frame deliverer (which may create the added input lag in non-G-SYNC, non-GPU-bound situation due to the possible occasional skipped/repeated frame).
(jorimt: /jor-uhm-tee/)
Author: Blur Busters "G-SYNC 101" Series

Displays: ASUS PG27AQN, LG 48CX VR: Beyond, Quest 3, Reverb G2, Index OS: Windows 11 Pro Case: Fractal Design Torrent PSU: Seasonic PRIME TX-1000 MB: ASUS Z790 Hero CPU: Intel i9-13900k w/Noctua NH-U12A GPU: GIGABYTE RTX 4090 GAMING OC RAM: 32GB G.SKILL Trident Z5 DDR5 6400MHz CL32 SSDs: 2TB WD_BLACK SN850 (OS), 4TB WD_BLACK SN850X (Games) Keyboards: Wooting 60HE, Logitech G915 TKL Mice: Razer Viper Mini SE, Razer Viper 8kHz Sound: Creative Sound Blaster Katana V2 (speakers/amp/DAC), AFUL Performer 8 (IEMs)

Post Reply