dubiousintent Posted October 16, 2018 Share Posted October 16, 2018 I see your problem. It's a not-uncommon packaging mistake by the author. Per the instructions on that mod's description page: The file includes the following:Data\Meshes\Characters\_male\skeleton.nifData\Meshes\Characters\_1stperson\skeleton.nifWhen installing this skeleton, PLEASE make a backup of your original skeleton.nif files inBOTH locations, _male and _1stperson.Install the "skeleton.nif" files to those locations. The archive includes them in the proper "Data" folders, but you can't just install it with your current mod manager. As the archive contains a "top level" folder consisting of the mod name (which is not an EXPECTED game folder), you need to unpack the archive manually, but with only everything under the archive "Data" folder into the game "Data" folder. (Those nifs are the only files in it, so you don't need to worry about it replacing anything else.) Edit: FYI - When a mod manager encounters a folder name that is not an "expected" game folder, it gets placed as a "new" folder under "Data". That creates a path the game engine simply ignores, so it never sees the expected paths lying under it. This is worth knowing, as many mod authors simply package their mods by selecting their working folder (instead of all the files and folders under it), which is what creates the new "unexpected" top level folder name. All the mod managers are expecting to see folders that belong under "Data", and some of them recognize that "Data" may be present as the top level as well. But they expect every package's contents to be placed under "Data". Which is why packages that install starting elsewhere (such as NVSE) have to be manually installed. Personally, I repackage such archives so the extraneous "mod name" folder is removed so I can use my mod manager properly with it thereafter. -Dubious- Link to comment Share on other sites More sharing options...
Recommended Posts