Installa Steam
Accedi
|
Lingua
简体中文 (cinese semplificato)
繁體中文 (cinese tradizionale)
日本語 (giapponese)
한국어 (coreano)
ไทย (tailandese)
Български (bulgaro)
Čeština (ceco)
Dansk (danese)
Deutsch (tedesco)
English (inglese)
Español - España (spagnolo - Spagna)
Español - Latinoamérica (spagnolo dell'America Latina)
Ελληνικά (greco)
Français (francese)
Indonesiano
Magyar (ungherese)
Nederlands (olandese)
Norsk (norvegese)
Polski (polacco)
Português (portoghese - Portogallo)
Português - Brasil (portoghese brasiliano)
Română (rumeno)
Русский (russo)
Suomi (finlandese)
Svenska (svedese)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraino)
Segnala un problema nella traduzione
As far as overwrite folder, you can simply drag and drop that stuff manually by going to your MO installation directory and to your overwrite folder and then finding the relevent mod folder as well, and doing it like normal file management if the in program system isnt working
I am not even far enough along with this to know what you are saying. I really can't start this process untill I know with 100% certainty that MO is going to support everything I need it to support. Once I take this load order down, there is no going back.
Well my comment was designed for the person who has the problem and who should know MOs various systems
MO supports multiple types of installers, from the normal FMOD installer, the BAIN installer and a few others so one of those other types might be able to install SMIM without an issue.
You can also download the archive unpack it and manually pick which files you want via manual selection and then load that into MO
I personally have never had a problem with MO not installing SMIM properly, but then instead of just picking the complete pack in the installer I select all my options manually so that might also be a potential fix.
And as far as MO not installing it properly, so far as I understand, it would be less the fault of MO, and more the fault of the way the installer is written, which makes it the mod authors problem, especially as NMM has trouble properly installing all the files as well at times with various mods too
Generally leave them on. The reason you would have them disabled if if there is information in there in the form of patches etc that isnt compatable with your given profile. You can set this up by having a 'mod folder' that contains a bashed patch, merged patch (if you have one) and esps for your skyproc patchers for each profile so you just have to swap the mod files to get the relevent esps to load instead of regenning them every time like you would have to do otherwise.
Hope that makes sense, im a little tired at the moment XD
I can move data form Overwrite content as usual, by selecting them all and dragging them over another mod. I tried this in both Priority and Mod Name views, without experiencing any problems.
Installing full SMIM is not recommended. It is much better to select options manually from installer - that runs well with MO. The data about SMIM not being supported by MO - or another way around - is misleading, because SMIM author apparently does not understand how left panel works. He is stuck in thinking the order of installation, but left panel in MO actually mimics just that.
I honestly find that SMIM is even easier to use with MO, because we can activate/disable Bethesda plugins trough left panel Mod List, withou affecting to load order. Thus we can test how different options from SMIM affect to game performance, withou reinstalling the whole order again - as NMM would require.
I've been doing that with the bashed patches (each in a mod named "Bashed Patch - <profile-name>"). When I look at the mod's Filetree (in the Information dialog) the modified date is wrong, it shows the date when I first created the mod for the bashed patch; but if I run Wrye Bash and check what masters the bashed patch requires it lists everything expected.
Ultimately I had to re-verify the cache and had 6 missing/corrupted files. I've managed to save the game for now (it's still not right) but if I had it to do over again I would have spent much more time on learning the system. It is an easy enough program until something goes wrong, which is a matter of if, not when.
I'm not dogging the program, only saying: Be Prepared.
As far as if MO caused the problem, MO doesnt touch any of your base game files in any way at all, and in fact never touches the data folder so it certainly shouldnt be causing problems with the offical bethesda files.
As far as with mods, some mod authors either don't know how to use MO, and don't understand the systems it impliments which results in some problems with a very very small amount of installers, such as with SMIM, but SMIM as it has been said, doesnt have a problem is you use the custom installation option. I have yet to see another installer that doesnt work with MO, except if mod authors have packaged their mods in a horrible data structure in which case it would cause problems with NMM as well.