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
- 1 for UI/rendering
- 1 for simulation
- X for pre-processing matrix data for rendering (mesh threads), where X is the 2 you reference in your post.
If your CPU has 4 or less cores, then there's no point increasing the number as you are already utilising all of your cores.
If your CPU has more than 4 cores then increasing X may increase performance in very, very large aquariums, fully zoomed out*. However, I suspect the bottleneck at that point will already be one of the first 2 threads.
You can always try it but I suspect you won't see a difference.
PS mesh threads are only used when you turn on "multithreaded rendering" in the options.
EDIT: * If you are running mods with a lot of vertices then it might make more of a difference compared to vanilla.