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
Whenever the dinos are not in render distance, to reduce memory usage a lot of the data that makes them visable to you, and tells them when to do something is put on halt. Reduced if not illiminated to a few calculations and data in the background. Whenever they render in distance to you again they either pick up and calculate where and how they should be in the time you were gone. Or it is picked up right where it is left off. Depending how it is coded.
I'm not a coder so this is just my limited understanding of how it works. Someone can correct me or explain it better if they wish.
But basicly if everything going on in the game had to be kept up all at once at all times it would have a much more sever impact on your system and game perfomance especially on singleplayer where the data is stored on your computer and not a server. Stasis is when the information for them is halted or slowed to a crawl. This is usually when they are not in render distance, especially in singleplayer.