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
This is because the game folder has 1 large 22GB PAK file and one large 40GB PAK file, which means every time it starts the file decompression with one of them, it has to 'open' a gigantic archive and read it to find the files needed.
After it's finished retrieving the file it might 'close' the archive, and then open the archive again to grab files.
Because it takes way too long to retrieve files, the game code might think the game is 'frozen' and throws a exception and reacts with closing the game (hence a game crash).
Used process lasso to deselect E cores just for remnant 2
I hope this will be fix in future
Even then, windows has an option to limit the process to specific threads as well. Not sure if it's better than dedicated process lasso program.