Zainstaluj Steam
zaloguj się
|
język
简体中文 (chiński uproszczony)
繁體中文 (chiński tradycyjny)
日本語 (japoński)
한국어 (koreański)
ไทย (tajski)
български (bułgarski)
Čeština (czeski)
Dansk (duński)
Deutsch (niemiecki)
English (angielski)
Español – España (hiszpański)
Español – Latinoamérica (hiszpański latynoamerykański)
Ελληνικά (grecki)
Français (francuski)
Italiano (włoski)
Bahasa Indonesia (indonezyjski)
Magyar (węgierski)
Nederlands (niderlandzki)
Norsk (norweski)
Português (portugalski – Portugalia)
Português – Brasil (portugalski brazylijski)
Română (rumuński)
Русский (rosyjski)
Suomi (fiński)
Svenska (szwedzki)
Türkçe (turecki)
Tiếng Việt (wietnamski)
Українська (ukraiński)
Zgłoś problem z tłumaczeniem










I have had no complaints about load times or memory usage since this mod launched apart from that last guy and I suspect that he was having other problems.
From my own understanding, yes, but also not really in any way super convenient. The game doesn't know when a mod's been updated, so you'd have to recache it basically every single time. Also, even if you cache it, it doesn't really solve the issue.
Sure, it reduces the number of file opening/closing, but in any scenario where it's worth potentially curbing loading times, now it has to read a really large file, which reduces the gain that would've been gotten by reducing the number of files that have to happen.
I genuinely don't know what you mean by randomness and I've had exactly zero reports of this consuming excessive RAM (which I know that it doesn't, it appends a couple of letters to the end of a description).
If scanning patches is taking too long (although I doubt it very much, it takes only a second with a huge mod pack) there is a setting to disable it.