NMM Links aren't reliable?

[Casuallycryptic]

I'm not sure if this was an expected consequence of the new architecture or what, but when you choose the NMM option to dowload mods, sometimes they don't work as intended. I've noticed this a couple of times, most recently with Seranaholic. If I download the NMM version of the mod I get a version of the character with no hair textures and an unusually wide face. If I download the manual download, move it to the Vortex download directory, restart vortex and install from there it works perfectly.

[maverikch]

and that didn't hpepen when you use NMM?

And are you talking about the Button at the top of the mod page or within the files seciton? because the button on the top of the mod page will download the last uploaded main file. not the obvious one.

 

for example: Sim Settlements FO4 Mod has now the ususal Main File and a 3in1 MainFile. The latter was uploaded later. Thus when i click the mod page NMM button it downloaded the 3in1 version.

[Casuallycryptic]

I always download from the files section. These are mostly mods I've used before as I went on a fairly large modding hiatus and only got back into it about a month or so before Vortex's release, so I'm fairly sure the problem did not happen with NMM.

 

I know I downloaded the correct mod for Sarenaholic in particular, because every version of that mod utilizes a different hairstyle, and while the textures for the hairstyle from the NMM link did not show correctly, the meshes did.

[Casuallycryptic]

Well, a few days later and Vortex doesn't seem to have been the problem with Seranaholic at least.

 

Basically, what was happening was that another mod, Realistic Teeth, doesn't play well with followers with custom faces, and even if you overwrite it (or don't, really regardless of what you do other than disable it), it still causes issues. When I would reinstall Seranaholic it would work for a time, then snap back to the above issues so long as Realistic Teeth was also enabled, giving the illusion that I had fixed the conflict by moving to the manual link rather than the MM link when in reality, it was the re-installation itself which (temporarily) resolved the issue.