Sexlab not playing animations

[nhentii]

Got a fresh install of 1.6.1170 and have been double checking to make sure everything is compatible and installed correctly, but Sexlab is being really stubborn and not playing any animations. Actors just stand inside each other and don't do anything. Everything was registered in SLAL and OAR is not at it's animation limit. I use the latest version of Pandora Plus, but even reverting to FNIS and/or Nemesis doesn't change anything or show me any errors. No matter what I try, Sexlab animations are the only thing that refuse to play.

[traison]

The answer to your question may be in the Papyrus log.

[nhentii]

Well this was my last log but I'm not sure what I'm looking at

Papyrus.0.log

[jfraser]

is this on a brand new game or are  you trying it on a previous save?

[traison]

1. SL is fine.
2. fnis_aa is missing a function called GetInstallationCRC, so there's something wrong with your FNIS scripts.
3. If you have issues in the future, consider disabling MMX452_AS7. It seems to want to have its fingers in everything.

So, regarding animations not working:

1. You tried to play a creature animation. Since you're using Nemesis, make sure you run it in the correct order with FNIS, as Nemesis has no support for creatures.
2. Every version of Pandora seems to invent a new issue. Consider trying a different version.
3. Make sure there's no warnings in the FNIS output, or post it here if uncertain.

[nhentii]

15 hours ago, jfraser said:

is this on a brand new game or are  you trying it on a previous save?

I haven't even made a proper save yet. I'm using Alternate Start and haven't left the prison to test the mods I'm installing before I play. I got to the point of installing Sexlab and summoning a werewolf to see if it was working and came here when it wasn't.

Anyway, FNIS by itself isn't giving me any trouble, and Nemesis wasn't either when paired with it. Nemesis started giving me errors when updating the engine referencing files from BFCO, Precision, and POISE.

Ex.
ERROR(2003): Invalid file name. File name must only be #<modcode>$<id> or #<id>. Please contact the mod author
File: mod\(bfco,colis,Precision)\animationdatasinglefile\DefaultFemale.txt

When I went to check those locations, those files weren't even there. I ended up disabling the mods and deleting those folders since they were empty and Nemesis had no problems playing animations afterward. Then with the same mods still disabled I ran it on the latest Pandora engine and everything worked fine there too. What's confusing is that those 3 mods had no issues before I installed Sexlab so I can't guess why it's doing that now. I might just have to play without them which kinda sucks.

[jfraser]

What mod did you use to try to have sex with the werewolf?

[nhentii]

15 minutes ago, jfraser said:

What mod did you use to try to have sex with the werewolf?

Just Aroused and Matchmaker since it forces 2 actors to start a scene.

[Grey Cloud]

Hard to figure out what combo of animation mods you are actually using but:

6 hours ago, nhentii said:

File: mod\(bfco,colis,Precision)\animationdatasinglefile\DefaultFemale.txt

This seems to be from Precision although on my machine the path is: -  Precision\Nemesis_Engine\mod\colis\animationdatasinglefile\DefaultFemale.txt (I only have 1 Precision animation)

 

I use Pandora v2.6.0, no FNIS or Nemesis. Also use OAR and Precision.

[nhentii]

Was clearing some files and managed to find Pandora Engine v2.3.0 which i used on an older version of Skyrim. I got curious and tossed it in with everything enabled this time and it worked like a charm. It could be caused by pathing, but like traison said it could just be newer versions of the engine making new issues. The version I tried using before was v2.7.0.

Edited April 6, 2025 by nhentii

[traison]

4 hours ago, nhentii said:

Was clearing some files and managed to find Pandora Engine v2.3.0 which i used on an older version of Skyrim. I got curious and tossed it in with everything enabled this time and it worked like a charm. It could be caused by pathing, but like traison said it could just be newer versions of the engine making new issues. The version I tried using before was v2.7.0.

 

This is why I'm still staying away from Pandora. Stuff like this tends to lead to spaghetti code, I'm just hoping they can keep the code together so that eventually we will have a replacement for FNIS. Not that FNIS really needs a replacement if you ask me, but then again, I'm not the right person to ask for an opinion on that.

 

I'm just occasionally archiving Pandora versions, despite their potential flaws, and hoping for a bright future. 👍

Edited April 6, 2025 by traison