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
Unfortunately, games tend to be single-threaded... and Enshrouded is no exception. What this means is, you're running your local game and your network host on the same thread (ie, CPU core), because they're both running inside the same parent process... which means you've got a single core trying to do all of everything.
Run the dedicated server instead of just hosting your game from the process you're playing on; spreading the workload to additional threads (ie processes, ie CPU cores) should solve your problem.
Reddit thread on transferring existing world to server:
https://www.reddit.com/r/Enshrouded/comments/19exr9d/transferring_coop_world_save_from_local_game_to/
Steam thread on joining your own dedicated server:
https://steamcommunity.com/app/1203620/discussions/0/4142816460194199012/
This one will definitely be helpful:
Reddit thread on running Enshrouded dedicated server:
https://www.reddit.com/r/Enshrouded/comments/19eqwdp/dedicated_server_setup_windows_steamcmd/