安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
After a little exploring, a few tricky shortcuts strung together nearly cut my time in half, from 09:37.73 to 04:49:49 and jumped me from 46th to 2nd on the boards.
I know I can push it faster if I keep at it!
But using intentional FPS drops to intensify the broken/infected design, although a nice idea in theory, does not work. It makes it impossible to play on weaker machines and is just nullified by the massive computation power of newer high-end GPUs. (My GTX 1070 yields smooth and stable 60 FPS during the infected parts…)
Can you set a target frame rate in the editor, so that some parts are limited to like 10FPS on every machine? Then use this and keep this idea, otherwise it makes this otherwise great track unplayeble for those without a high-end GPU…