安裝 Steam
登入
|
語言
簡體中文
日本語(日文)
한국어(韓文)
ไทย(泰文)
Български(保加利亞文)
Čeština(捷克文)
Dansk(丹麥文)
Deutsch(德文)
English(英文)
Español - España(西班牙文 - 西班牙)
Español - Latinoamérica(西班牙文 - 拉丁美洲)
Ελληνικά(希臘文)
Français(法文)
Italiano(義大利文)
Bahasa Indonesia(印尼語)
Magyar(匈牙利文)
Nederlands(荷蘭文)
Norsk(挪威文)
Polski(波蘭文)
Português(葡萄牙文 - 葡萄牙)
Português - Brasil(葡萄牙文 - 巴西)
Română(羅馬尼亞文)
Русский(俄文)
Suomi(芬蘭文)
Svenska(瑞典文)
Türkçe(土耳其文)
tiếng Việt(越南文)
Українська(烏克蘭文)
回報翻譯問題
Note that any save that's used Prop Anarchy (or more specifically the EML library it uses) at any point is unstable and subject to corruption. Starting with a new city without Prop Anarchy is recommended over converting an existing city, but if you want to try you can try to use ' Remove EML ' to recover as much data as possible.
'Minimum distance' only takes effect if the automatic LOD calculation comes up with a lower value than your minimum. This is usually (but not always) for smaller assets, or assets with unusual shapes.
In this case, if the calculated LOD distance was 200, but you have a minimum LOD distance of 500, then 500 will be used.
'Minimum distance' is just that - a hardcoded minimum. If the calculation ends up with a smaller distance than that figure, then it'll be clamped to the minimum instead.
So, in your example, let's say the game calculates the LOD distance as 3000 (note the actual calculation is done on a per-asset basis and is based on the physical size of the asset model, so there's no set distance and no "rule-of-thumb" - it's truly unique for each asset).
Setting the minimum distance to anything under 3000 will thus have no effect on that asset (but may on others, ofc).
If you set the distance multplier to 150%, then the LOD distance for that asset will now be 4500. Now any minimum distance under 4500 will have no effect.