Установить 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…