Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I never mess with this setting, what are the other captures API doing?
The same thing, only different :) From the Guide:
WGC: Does not dynamically adjust the output framerate based on the in game framerate, as a result it requires a locked stable FPS and can have worse frame pacing. However it has less latency than the DXGI method and a 6-9% less overhead
GDI: Provides no benefits over WGC, its just there incase your windows version does not support any other method
But you use LS 2.9, correct? Normally it would display 60/120, if it's only one number then check that Capture API is set to DXGI, WGC and GDI only show one number.
But 165/165 is another issue that it's not done right. Maybe he didn't properly cap the fps.
It's obviously not capped. How does he cap it? Has he tried it with RTSS?
No, the first number is the base framerate, the second the displayed framerate. For framegen to work the base framerate needs to be lower than than max refresh rate. For x2 framegen cap it to 30, then the counter would show 30/60.
Thanks. Now it shows 30/60! ;-)