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
It is what it is. I personally don't find these builds "unplayable" at all, but either way, there's little to be done about it - that hasn't been done already; it's better than in the past - because ND is heavily CPU-bound; you're not seeing GPU lag at all. The game is written in a high-level language (GML), which is then interpreted by the GameMaker engine.
My suggestion to you, is to learn how to *exploit* lag.
But it did return to normal performance after the projectiles cleared, so if something is leading to accumulating lag that doesn't go away after the source leaves/dies, that should be reported as a bug to look into.