Think UI mods and hand-combined texture mods. Parentmod_voicepack1.esl -> parentmod_voicepack1.bsa (uncompressed)įor general use I've pretty much replaced every dummy ESP file I had with dummy ESL files to save plugin slots in cases where the assets being loaded weren't terribly load order sensitive. Parentmod_texturepack2.esl -> parentmod_texturepack2.bsa (compressed) Parentmod_texturepack1.esl -> parentmod_texturepack1.bsa (compressed) Parentmod.esp -> parentmod.bsa & parentmod - textures.bsa Since they don't have any records in them they don't really count against the FormId ceiling. I don't want to push my luck too hard so I try to stay below 2GB as a general practice.Ģ.
#Best skyrim ini file archive#
SSE seems to be OK with uncompressed archives well over 2GB, but I haven't gone over 3GB for a single archive or 4GB for a BSA pair. I end up learning a couple of things during this process that may be useful:ġ. I probably just misunderstood what he meant.
#Best skyrim ini file how to#
That gave me a faint glimmer of hope so I started googling to try to figure out how to do it to no success. What got me thinking along the INI file lines was an old post by over on the STEP forums about 圎dit's BSA loading rules.
Thank you Yes, I did a few experiments with naming conventions and even tried using "sResourceArchiveListBeta" as a bit of a last resort. To answer the question though, no, you can't use an ini fragment to load your BSAs from because you'd need to override the one in the main ini to do that.
Have you tried simply naming them the same way Skyrim names its texture files? "ModName - Textures0", "ModName - Textures1" etc? The same kind of naming exists for meshes too.
0 kommentar(er)
