安裝 Steam
登入
|
語言
簡體中文
日本語（日文）
한국어（韓文）
ไทย（泰文）
Български（保加利亞文）
Čeština（捷克文）
Dansk（丹麥文）
Deutsch（德文）
English（英文）
Español - España（西班牙文 - 西班牙）
Español - Latinoamérica（西班牙文 - 拉丁美洲）
Ελληνικά（希臘文）
Français（法文）
Italiano（義大利文）
Bahasa Indonesia（印尼語）
Magyar（匈牙利文）
Nederlands（荷蘭文）
Norsk（挪威文）
Polski（波蘭文）
Português（葡萄牙文 - 葡萄牙）
Português - Brasil（葡萄牙文 - 巴西）
Română（羅馬尼亞文）
Русский（俄文）
Suomi（芬蘭文）
Svenska（瑞典文）
Türkçe（土耳其文）
tiếng Việt（越南文）
Українська（烏克蘭文）
回報翻譯問題
討論區規矩與守則
檢舉此篇文章
Np.
Ya know what. I was wondering about that. I never paid too much attention but when messing with the setting I knew something was off in that but thought it was just me but now you just confirmed it. Ill give that also a try and see what I experience.
Don't do this as it's no longer relevant. When Lossless Scaling only had LSFG beta is when I posted that. It's no longer a wise idea to use ULL with lossless scaling since MANY updates ago. Follow official guides etc in the stickied here and on Lossless Scaling discord.
Also the way it was changed after pre LSFG 1.1 Fsync no longer works since the favourable DXGI method.. and you should only be not using DXGI if you're on such an old rig that it isn't supported or there are issues with it: Fsync only works with DX11 or lower and typically it's fine but since LSFG 2.0+ with DXGI it can cause instabilities so it's not a good idea to bother with it.
You're best off using Async or if your monitor has VESA VRR which is essentially the same thing un emulated. This will reduce tearing to the 1/99% ratio if properly setup and allow for very very low input latency(it's important to setup an VRR correctly). Most guides will tell you to set your max fps to 95% of your refresh rate but this is wrong and has been tested to be an unnecessary fps cap in most situations.
You can get 90% of the same effectiveness without capping your fps so drastically. For example in most cases 60fps VRR/Async only needs to be capped at 58.2 fps where as following the rule would state that a 57fps cap would be necessary. 58.2fps is the exact value.. don't punch that into RTSS, exactly 58 is fine. A further example would be the more extreme end of this equation: 240hz and 360hz gsync panels.
The rule for these high refresh rate panels would be 342fps for the 360hz panel and 228fps panel but this isn't necessary at all. {Pretty much after 165hz you only need to cap 5 less for anything in the 240 range. 360+ it's wise to do a full 6 fps less. The actual value for 165hz+ is capping 5.68 less but rounding up is only important when you get to extreme refresh rates with Gsync Ultimate/Freesync Premium Pro. So only then is a full 6 more necessary as some input latency/tearing can occur in rare situations.
This has been tested several times by hardware unboxed and several other testers.
ah yes, thx. that makes sense now.
Because this setting with a G/Freesync monitor allows a capping of the framerate to avoid V-sync latency issues + sets a soft Reflex implementation to further reduce latency so it's really nice to have it ON (more details here: https://blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/14/ ).