Установить 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 (вьетнамский)
Українська (украинский)
Сообщить о проблеме с переводом
You *can* get used to the input lag, but it’s really best you don’t. I wouldn’t want anyone else playing with that input lag, that’s why I made the guide. Load times on an SD card are fine, but none of this is relevant to the guide. If you want more info on how the game runs, just go to protondb.
I don’t have anything to test input lag, but when I tried to use the quick access menu frame limiter, I’d say the input lag is around 0.5 sec/ 500ms. That’s more of a guess though. If you use the code, there shouldn’t be any input lag. I was able to complete the game docked at 30FPS and all my movement felt fluid. Screen tearing with and without the code, I saw no difference.