HDT HighHeels and MO2

[Apap]

Hey guys,

 

I have encountered a strange problem with the HDT HighHeels System in MO2:

 

After installing the mod, I noticed that MO2 puts the hdtHigHeel.esm at the very top of the load order automatically and locks it there. The problem is that when it does that, whenever I run FNIS I get an error message: ERROR(53): can't locate file 'temporary_logs\Skeleton.xml'.

 

I'm assuming this is because the XP32 MSE comes after the HighHeels, but because .esm is fixed in its place, I can't move it. I know for a fact the issue lies with the heels, because when I disable that mod FNIS runs without an issue.

 

Does anyone know how to fix or go around this? I just recently switched from NMM to MO2 so I'm not that savvy with it yet  

 

Thanks in advance! 

[Nagib]

36 minutes ago, Apap said:

Hey guys,

 

I have encountered a strange problem with the HDT HighHeels System in MO2:

 

After installing the mod, I noticed that MO2 puts the hdtHigHeel.esm at the very top of the load order automatically and locks it there. The problem is that when it does that, whenever I run FNIS I get an error message: ERROR(53): can't locate file 'temporary_logs\Skeleton.xml'.

 

I'm assuming this is because the XP32 MSE comes after the HighHeels, but because .esm is fixed in its place, I can't move it. I know for a fact the issue lies with the heels, because when I disable that mod FNIS runs without an issue.

 

Does anyone know how to fix or go around this? I just recently switched from NMM to MO2 so I'm not that savvy with it yet  

 

Thanks in advance! 

Just try to move the hdtHigHeel.esm in the right pane and it should pop it back up to other .esm files.

[Just Don't]

esm go before esp in your loadorder. That's the default behavior, not something in particular to MO.

 

You may have leftover files from running FNIS before. Check the Overwrite folder and make sure you've delete these files before running FNIS again. And for future uses, after you run FNIS and generate the files, right click on the Overwrite entry (left panel) and select "Create mod", name it something like "Generated FNIS" and place it at the bottom of your modlist (again, the left panel). Next time you want to run FNIS, delete your "Generated FNIS" on the left panel and make a new one. if this does not solve your issue try:

• set MO and FNIS to run as admin
• check if your FNIS/hdt HH are correctly installed, a re-install should be a quick and safe process

[Apap]

Strange, I launched MO2 this morning and FNIS managed to run without the error. I will have to observe this some more. 

 

On another note, my guess is that the issue occured because I installed HDT HHS after XPMS was already there, so maybe the latter does not overwrite the bones in the former for some reason? I guess one way of finding out would be to reinstall both but now with the new order? 

 

Also, could maybe LOOT be responsible somehow as well? I remember running LOOT after having installed HDT HHS and then FNIS directly after that.

[Just Don't]

3 hours ago, Apap said:

On another note, my guess is that the issue occured because I installed HDT HHS after XPMS was already there, so maybe the latter does not overwrite the bones in the former for some reason? I guess one way of finding out would be to reinstall both but now with the new order? 

As you're using MO you don't need to worry about the install order of your mods. You can change that on the fly, just move the mods in the left panel up and down, it's like a loadorder but for all mod files (mods near the top of the list may be overwrited by mods loaded below in the list). I doubt it has any impact tho, hdt HH shouldn't conflict with the skeleton.

 

3 hours ago, Apap said:

Also, could maybe LOOT be responsible somehow as well? I remember running LOOT after having installed HDT HHS and then FNIS directly after that.

As I said, esm go before esp files by default. Sorting your loadorder (aka using LOOT) would have little impact if any at all.

 

I think you had residual files from a previous use of FNIS (in your overwrite folder or mixed in one of your mods on the left panel). That's why I recommend to keep a clean overwrite entry and make your own "mod" with the generated FNIS files. That way you can remove it entirely if needed. Sometimes, a simple restart may help too (I'm not sure if it has to do with temporary files on the way or other OS magic barriers, but I've been there and a simple restart does wonders).

[Apap]

Ok, I think I actually might have messed something up with the installations: when in-game, the physics for hair and boobs are kind of wild - both tend to either freeze for a second in strange positions or stretch unnaturally when I stand still and then try to readjust when I move again. Also, after exiting, MO generates files in the overwrite folder: some config files for fuz roh d'oh and smart souls, and text files for HDT HHS and HDT PE - I was making some adjustments in the menus in-game so maybe that's why some of those files get generated. Now the question is whether I should move those files to their respective mod folders, or does this mean that something is wrong with those particular mods and I should reinstal them?

 

Also, if reinstalling of these mods is necessary, should I also reinstal the ones that depend on them (HDT armors, hair packs etc.)? Man, dealing with mods in MO seems like handling a nuclear reactor - make one mistake and suddenly you have a meltdown on your hands lol

[Just Don't]

1 hour ago, Apap said:

Also, after exiting, MO generates files in the overwrite folder: some config files for fuz roh d'oh and smart souls, and text files for HDT HHS and HDT PE - I was making some adjustments in the menus in-game so maybe that's why some of those files get generated. Now the question is whether I should move those files to their respective mod folders, or does this mean that something is wrong with those particular mods and I should reinstal them?

This is totally normal, as you setup your mods, or even use them for the first time, new files will be generated. Fuz Ro Doh generates its ini file, HDT generates a txt log, other mods generate a json file with your settings and so on. You can do 2 things with these files

• Create a new "mod"  with all these files to keep them outside of the overwrite folder (right click in "Overwrite" and select "Create Mod..."). This new mod could be called "Logs & settings" or something alike.
• Move each file to its own mod folder.

I personally move them to each mod folder. This should be done only once per mod/file generated (or until you choose "replace" when updating these mods).

 

1 hour ago, Apap said:

Also, if reinstalling of these mods is necessary, should I also reinstal the ones that depend on them (HDT armors, hair packs etc.)?

If the other mods are properly installed you shouldn't need to reinstall anything. Reinstall is not a required step to make things work, its just the easiest way to replace a wrong installation with a good one. The most common cause of bad installs in MO is when you add a mod, the mod has no installer so you just click "Ok" in the Quick Install window, but the mod had extra folders and you didn't check.

 

For example, we'll see FNIS. a good install path should look like this:

Quote

Mod Organizer 2\mods\Fores New Idles in Skyrim - FNIS

But the file you download comes with two additional folders, a quick install where the user didn't pay attention to the folder structure will give you something like this:

Quote

Mod Organizer 2\mods\FNIS Behavior 7.5\Data\Fores New Idles in Skyrim - FNIS

Which leaves the user with a GenerateFNISForUsers.exe that is useless.

 

The best advice I can give you is to always check if your mods have the right folder structure (no additional "Data" or "name of the mod" folders in between). If you select "Manual" when installing a new mod that doesn't come with an installer, you should see a window to explore the folder structure of the mod and MO will tell you if something looks wrong or not.

 

It may seems like a lot to grasp at first, but once you're familiar with MO it will be your best ally.

[isanae]

23 hours ago, dontknowdontcaredontask said:

right click on the Overwrite entry (left panel) and select "Create mod", name it something like "Generated FNIS" and place it at the bottom of your modlist (again, the left panel). Next time you want to run FNIS, delete your "Generated FNIS" on the left panel and make a new one.

You can also change the settings in the FNIS executable, check the "Create Files in Mod instead of Overwrite" and select that dummy "Generated FNIS" mod. When you run FNIS again, any files it generates will go in that mod instead of in overwrite.

[Just Don't]

8 minutes ago, isanae said:

You can also change the settings in the FNIS executable, check the "Create Files in Mod instead of Overwrite" and select that dummy "Generated FNIS" mod. When you run FNIS again, any files it generates will go in that mod instead of in overwrite.

True, but my old vuduu rituals make me think its just better to delete the previous files and make the new ones from scratch.