安装 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(越南语)
Українська(乌克兰语)
报告翻译问题






https://imgur.com/a/CqC57ws
Any idea how I can get a brush with the smaller alders to give me more density?
@Kago This was already mentioned indirectly, but remember also that texture size is a one-time cost per asset (or per-texture, with LSM) -- not a cost per placed instance. So texture size is somewhat less important for a tree set that you're probably going to use a bunch of all over the place. (Compare that to unique buildings -- if you have 100 unique buildings that you're only going to use once, they can have relatively more triangles, but if they're not sharing textures with LSM then you probably want them to have small textures to keep the total RAM use down.)
Tri count, on the other hand, is basically always relevant.
I've found balancing performance for Skylines to be very difficult though, because a lot of performance issues are caused by strange issues under the hood. The game also seems to struggle with overlapping entities in particular, so a few large trees on screen typically perform better than a bunch of little trees, even if the little trees have more total tris.
TL;DR: tri count xD
I wonder: whats is most demanding to the game, tri count or texture size? I have way too many trees and I should start unsubscribing from those that arent balanced between tris and texture size.
Thank you for these :D
@Señor Mustacho - Yes :) https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=2244341705