安装 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 suggest just sticking to a collections, believe me I tried to manage my own 100+ mod list and about 10+ hours in I get consistent crashes from a mod conflict that I have no idea how to even start troubleshooting. Now I have 200+ mods enabled and no crashes and run as smooth as butter.
I used the second highest rated collection, the first one runs like ass on my PC. I also added about 10+ mods that are not present in that collection followed the general rule of mod organization [1 animation & performance, 2 animations, 3 Races, etc etc ] and so far so good.
For example in the mod manager
[1] Mod Organizer [UI, grfx, performance] = AKA this mod
UI Mod number 1
UI Mod number 2
Graphics Mod
Performance Mod
[2] Mod Organizer [ Animation] = AKA this mod
Ultimate Animation Overhaul
More animation mod
Etc animation mod
[3] Mod org races = AKA this mod
RPG races
Cat girl races
demon girl races
etc. races
And so on.