Creature Anims break when i run SLAL

[unit098]

Im running into a weird issue, in my save I had working creature anims awhile ago but recently the game would behave as if there were no creature anims in the SL registry. To try and fix it I did the full clean from the sexlab MCM. After the clean I could re enable creature animations and the base animations would work fine. But when I went in SLAL and registerd all my addon animations every creature animation (including the base SL ones) would break and behave as if I never ran FNIS with the creature and npc standing in eachother and not moving.

Any advice on what might be causing this would be apreciated

[1whirled]

Wish I could help with a more solid grounding, but I have no idea even though I've had this happen before a few times. Maybe can help narrow it down though. Not hopeful, I searched this extensively and never found a solution. Only others complaining of, and nothing of real use suggested. Also, following to see if someone responds with a valid answer.

 

 

I do know it's related to an animation pack. Which one, I have no clue. And the reason behind my positioning is it didn't cease to be a prob until I rebuilt my SLAL anim composition removing a bunch of packs and suddenly creature anims worked again. SLAL gives no warnings related either. It's also an old pack, happened first time on OG in 2014 or 15, I think it was (yes, I know this is the LE sub). Whichever it is, it's been ported to SSE too and it's occurred post me swapping over to SSE in 2019, so...

 

I'll put forth my conjecturing, since there are so few taking umbrage my gut feeling is that it's not, or at least not exclusively a creature anim pack, or you'd see a lot more posts to the effect of.

Edited February 2, 2025 by 1whirled

[unit098]

From my tests it seems you are right, I just tried only a single packs animations and they worked fine. Im gona try registering the rest of them and trying again. If that doesnt work its a safe bet to assume one of my packs has an animation that is bricking the whole creature side. That or it is an issue with the number of animations.

[unit098]

Its looking like its more specifically the matchmaker mod that broke. Anims with sexlab tools queue system work

[1whirled]

18 hours ago, unit098 said:

Its looking like its more specifically the matchmaker mod that broke. Anims with sexlab tools queue system work

 

 

That Sexlife? That one's particularly picky about everything being just so, and any errors whatsoever will out. I am having an issue with it picking the wrong anims and cancelling the event for creatures, and creatures only. Random Sex works fine at the same time. Dunno any other matchmaker that's as peculiarly retentive about.

 

To make things more clear, am running SL with original animations purged, this may be causing ^ that. Idk, haven't deep dived logs bc time constraints.

 

Doubt it's an .hkx being the root issue, but something in the SLAL .json or FNIS lists more likely. Whenever that scenario in my first post occurred, I've checked all the animations repeatedly to no avail. Reasoning is a bad anim would only affect that one instance being called and wouldn't brick all of that genre, for me, it was every single creature anim which failed to play at all regardless of which matchmaker.  

 

Were it an animation either file corrupted or with bad bones, you'd know, would be an instant ctd when it was selected.

 

Edited February 3, 2025 by 1whirled

[unit098]

Im fairly certain the issue lies in whatever mod is being used to start the scene. Using the spells from MatchMaker breaks things but starting scenes with the SLtools qeue system runs every animation fine. My best guess is that since I had te clean out my SL something in the MatchMaker code is looking in the old place for the animation as its still expecting the specifics from before I full reset my SL.

 

[1whirled]

You might want to nudge Osmel and see if he can help discern why, programming strictly isn't my thing, and we have parallel issues going on with two diff matchmakers both having the same errors. Either way, I'm interested to know myself.

[unit098]

Im gona try drastic measures first and uninstall the mod resave and reinstall