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
if the server values are lower than client, it shows the server settings. If the server is higher, it shows client.
Basically it always chooses the lowest setting.
sceneComplexity=1000000;
shadowZDistance=250;
viewDistance=3800;
preferredObjectViewDistance=3200;
terrainGrid=3.125;
preferredObjectViewDistance=1300;
is all you need kind off :D
Players and Zeds dont render beyond ~1100 meters anyways^^
results in
(could also be I'm just imagining things, though ;))
desync is more connected to network bubbles, not necessarily just view distance. Your largest issue is likely too many mods.
large amounts of mods, or small amount of certain mods absolutely destroys server FPS/tick rate. low tick rate = desync and disconnects/crashes.
Also big bases are going to cause latency isues while flying/driving. No avoiding that unless the server has base/item/storage restrictions. Some mods have known conflicts with vehicle latency like Party On! and others like it. IF the server refuses to remove mods that conflict, yer stuck with the desync.