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









I personally prefer the large "dump" of assets myself because it's sort of the "legacy" standard thing for TTS workshop mods for models - though mostly in way smaller quantity (like Vess, JustJohn, ScreamInVain). I think I'll just try to place things on the table a little less haphazardly in the future.
*Cheers to @Phantastic for mentioning the 'Expand' function. Didn't know you could do that and it saves soooo much time. xD
@Chro On the example builds, that's my line of thinking. I wanted to give people a good idea of how to make use of the assets.
@Sixstring & @Ðrim I think that's doable on a per-person thing by saving bags or moving everything into your own save. Personally the way I do this is how Phantastic mentions, with the "Expand" function, but I can see how people might want categories (sectioned bags).
@Phantastic Yeah these are exactly my same sentiments.
If you bag them all, then we can't use the 'Expand' function on the mod to find an asset whilst on another table.
If they're in a dump like they are now, it can take a long time to load and tanks FPS.
If they're in smaller more intuitively categorised mods... then that's a lot of mods you would need to maintain / update.
Mayhaps the best way to approach this is to give people the means to sort out their own solution.