Facegen is required regardless, and in that case you definitely will need to keep it. 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 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.
0 kommentar(er)
