Asenna Steam
kirjaudu sisään
|
kieli
简体中文 (yksinkertaistettu kiina)
繁體中文 (perinteinen kiina)
日本語 (japani)
한국어 (korea)
ไทย (thai)
български (bulgaria)
Čeština (tšekki)
Dansk (tanska)
Deutsch (saksa)
English (englanti)
Español – España (espanja – Espanja)
Español – Latinoamérica (espanja – Lat. Am.)
Ελληνικά (kreikka)
Français (ranska)
Italiano (italia)
Bahasa Indonesia (indonesia)
Magyar (unkari)
Nederlands (hollanti)
Norsk (norja)
Polski (puola)
Português (portugali – Portugali)
Português – Brasil (portugali – Brasilia)
Română (romania)
Русский (venäjä)
Svenska (ruotsi)
Türkçe (turkki)
Tiếng Việt (vietnam)
Українська (ukraina)
Ilmoita käännösongelmasta
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.