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
The client <-> server connection may time out if the server takes too long to do something (without sending a keep-alive message). This may happen when generating big maps. The solution is to wait for the server to finish its work, then try loading the newly created map (use Load Game).
Turf 2 will have an integrated server (vtclient.exe and vtserver.exe will be in the same .exe) to prevent this
Vtserver also tends to be laggy when dealing with a freshly generated large map (like 8km or larger on my machines) for reasons unknown to me. Restarting the game will fix this.
Also see:
https://wiki.voxelturf.net/wiki/Troubleshooting#Connection_To_Server_has_Timed_Out_.28Singleplayer.29
And unless the cities actually overlap, they'll still be disconnected from each other.
Also, are cities still disconnected or nah? If not, I can just manually connect them. Not a big issue.