XPMSSE Missing male Skeleton?

[Nimius]

Hi there!

 

I can't get XPMSSE to work. At least for males!

After a fresh install of Skyrim and mods I tested everything with a female character. Everything worked fine. But when I wanted to start a new playthrough with a male character, I noticed that the XPMSE Skeleton is not recognised. I use SOS and MNC.

 

Can somebody tell me what went wrong?

 

 

This is what it tells me for male character

Spoiler

 

 

And that's for a female character

Spoiler

 

 

[srayesmanll]

You didn't say whether you install using a mod manager or not, but more than likely the skeleton included in SOS is overwriting the skeleton in XPMSE.  If using MO2, make sure the XPMSE install is a higher priority in the left hand pane than SOS (the left-hand pane for MO2 is basically the install order so higher priority mods overwrite lower priority mods when dealing with loose files like skeletons - you can sort by priority in that pane).

[Nimius]

17 minutes ago, srayesmanll said:

You didn't say whether you install using a mod manager or not, but more than likely the skeleton included in SOS is overwriting the skeleton in XPMSE.  If using MO2, make sure the XPMSE install is a higher priority in the left hand pane than SOS (the left-hand pane for MO2 is basically the install order so higher priority mods overwrite lower priority mods when dealing with loose files like skeletons - you can sort by priority in that pane).

Sorry forgot to mention that I use MO2.

And LOOT! ?

 

 

Edit: Double checked. XPMSE has higher priority.

[Just Don't]

Check that SOS isn't overwriting XPMSE. MNC should overwrite XPMSE tho, otherwise you might experience issues with creatures. You need to check the left panel in MO, not the loadorder.

[Nimius]

I have to admit that I'm new to MO2...

 

This is what it tells me

Spoiler

Spoiler

 

 

 

 

Edit: Alright, I got it... I moved XPMSE below SOS and now it works. MO2 has a learning curve... ?

[Just Don't]

Yeah, you did it.

 

In this case you need to check the Conflict column, see these little lighting bolts with + and - signs?

• The + means the mod (for example SOS) is overwriting another mod.
• The - means the mod is being overwritten by another mod.
• You can select (one click) a certain mod and all the related conflicts will be highlighted.
• You can also double click to see the mod information, there is a Conflict window that will show you every file and mod that is conflicting. 

For your particular case the fix is indeed move XPMSE below SOS in the left panel. Another solution would be re-install SOS and disable the skeleton install. SOS skeleton is obsolete really and shouldn't be needed under any circumstance. And remember to place MNC even lower in your left panel, so it can overwrite XPMSE as per the install instruction for MNC.

[Nimius]

7 minutes ago, dontknowdontcaredontask said:

Yeah, you did it.

 

In this case you need to check the Conflict column, see these little lighting bolts with + and - signs?

• The + means the mod (for example SOS) is overwriting another mod.
• The - means the mod is being overwritten by another mod.
• You can select (one click) a certain mod and all the related conflicts will be highlighted.
• You can also double click to see the mod information, there is a Conflict window that will show you every file and mod that is conflicting. 

For your particular case the fix is indeed move XPMSE below SOS in the left panel. Another solution would be re-install SOS and disable the skeleton install. SOS skeleton is obsolete really and shouldn't be needed under any circumstance. And remember to place MNC even lower in your left panel, so it can overwrite XPMSE as per the install instruction for MNC.

Didn't know that about SOS skeleton...

I got everything else from the link in your signature ?