How to keep skyrim from crashing with mods

HOW TO KEEP SKYRIM FROM CRASHING WITH MODS HOW TO

I don't know how SWIFT supposedly got away without generating it, but it definitely needs it if they've created all new NPCs of their own.

If the mod you're porting doesn't require facegen then you can throw out whatever facegen files are autogenerated by the CK. The 1b method you're listing will generate unnecessary ITMs in the process which is something you don't want. Then exit the CK.Дo keep in mine you'll still need to poke around in ењЋdit to make sure the water data from Update.esm is carried over, and it may still be necessary to do additional work on the mod after it's been ported to make sure it's not conflicting with any of the new vegetation that was added. Once it's done loading, without doing anything else, click save. Can there be another possible outcome?ДЄll you have to do is make sure the. Ingame testing results in no black-face bug without facegen (if original mod doesn't had those). Or mods like SWIFTВ (Oldrim)В which has bunch of new non-templated NPC and had no facegen files and still worked like a charm, without any face-related problems (while ported SWIFTВ have facegen for those NPCs for whatever reason). Should facegen files autogenerated by CK 64 on save be used with ported mod, if original LE mod had no facegen files (and was working nice, without black-face and stuff)?ДЇor example, mods which doesn't touch appearance of vanilla NPCs. ItВ sounds dangerous, considering that different guides tend to have either first or secondВ methodВ and, as a result, we have a lot of ported mods created in different ways.Дў.

HOW TO KEEP SKYRIM FROM CRASHING WITH MODS HOW TO

How to properly save mods in the CK 64 when porting?Д«) Active > Change something from plugin (ex: add '1' to book's name) > Save > Revert change (remove '1') > SaveДЄsking because the result of these methods is different files (by hash and by size) while in ењЋdit both files are identical.

How to keep skyrim from crashing with mods