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…