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
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.