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
But as people have said, it would be a huge memory waste if it tried to load the terrain in its range when you're loading the game -- especially if you have lots of scanner rooms around the map.
The best way is to not use the scanner when you first load the game. Do something else. Then when you come back to your base, turn on the scanner. That way you only use it after you've gone out and loaded chunks for it.
Not really. It doesn't have to actually render anything, just fetch basic terrain math and item arrays.
Sure, sometimes you'll tell it to scan for something that's not there, and there might be some lag when you turn it on and chunks start loading, but that's ok.
https://steamcommunity.com/sharedfiles/filedetails/?id=1731690659