Cài đặt Steam
Đăng nhập
|
Ngôn ngữ
简体中文 (Hán giản thể)
繁體中文 (Hán phồn thể)
日本語 (Nhật)
한국어 (Hàn Quốc)
ไทย (Thái)
Български (Bungari)
Čeština (CH Séc)
Dansk (Đan Mạch)
Deutsch (Đức)
English (Anh)
Español - España (Tây Ban Nha - TBN)
Español - Latinoamérica (Tây Ban Nha cho Mỹ Latin)
Ελληνικά (Hy Lạp)
Français (Pháp)
Italiano (Ý)
Bahasa Indonesia (tiếng Indonesia)
Magyar (Hungary)
Nederlands (Hà Lan)
Norsk (Na Uy)
Polski (Ba Lan)
Português (Tiếng Bồ Đào Nha - BĐN)
Português - Brasil (Bồ Đào Nha - Brazil)
Română (Rumani)
Русский (Nga)
Suomi (Phần Lan)
Svenska (Thụy Điển)
Türkçe (Thổ Nhĩ Kỳ)
Українська (Ukraine)
Báo cáo lỗi dịch thuậ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…