No Sexual Animations, but has Sound

[PapaPhantom7]

I am able to initiate sex with npcs but have no animations. My character and the npc will go to the spot, remove clothes, and even have the sounds for the animations. However, it takes a while to get into position and there is no animations happening.

I use MO2 and this is my setup: https://modwat.ch/u/PapaPhantom7

I have looked around to try and find a solution, but can't seem to find anything and can't figure it out myself. Is there an obvious problem that I don't see?

[Just Don't]

That usually means there is an incompatible mod providing animation/behavior files not made for Skyrim SE. You can check the text FNIS gives you after using GenerateFNISforUsers to be sure (if you enable the "HKX file compatibility check" FNIS will scan every animation for incompatibilities). Just keep an eye for any warning or error messages and the mods related to these warning/error lines.

[anjenthedog]

it taking time to assemble animations (for me anyway) always means there's script lag. You can check by enabling debug mode in SL (and leaving it on, I do) . Then when an animation is initiated, if you detect a sluggishness in the actual initialization, open console (~) and you may/should see something in the echoed console text like "lagtimer = (some value)".

 

I can't say exactly why you can run into script lag. there are many potential causes. to many environmental scripts, (for instance, Birds of Skyirim hung my scripting early on and a I dumped it right after), too many scripts that have gone to some sort of a dead spin condition (they never properly terminate) , maybe too many resources, etc.

 

IME... Not animating at all (while groans and ooh ahs are heard)  can be caused by 

 

• no registered animation corresponding to the one SL thinks is registered (usually a misconfig caused by the user installing and uninstalling and registering and unregistered animations) ... been there done that. That is, the animation is listed as available, but there is no registered animation corresponding to that entry any more.
• LE animations (although as I recall from when I did mistakenly load some , there were generally more catastrophic results)
• What Just Don't said. or more generally, FNIS just not being run properly.
• skeleton issues

 

For me, as a Vortex user, FNIS is set as shown below:

 

1) afaik needed for females

2) not sure anymore but I keep it checked

3) for older animations, afaik primarily creature related but I;m not exactly sure

4) I install quite a few mods from Nexus, which is why that fourth entry is set

5) if you have Tk Dodge or Ultimate combat installed (obviously I don't have either installed) 

[Just Don't]

1 hour ago, anjenthedog said:

For me, as a Vortex user, FNIS is set as shown below:

You should check the FNIS description to clarify what each patch does. Basically

1. Gender Specific Animation is for mods providing animations with the following folder structure ...\meshes\actors\character\animations\male or ...\animations\female. It's harmless to have it enabled even if you don't use such mods. So keeping it enabled is fine, but it has nothing to do with female characters or NPCs in particular.

2. Skeleton Arm Fix adjust the skeleton to avoid weird looking arms in certain animations. Recommended when using custom skeletons such as XPMSSE (so always enabled=good idea).

3. HKX File Compatibility Check will scan all the animations detected by FNIS and report any incompatibilities. By default FNIS only warns the user if there are behavior files (...meshes\actors\character\behaviors\...) incompatible, with this check the warnings will appear for individual animation files too (...meshes\actors\character\animations\...).

4. File Redirection is there to change the default FNIS output in case you're using mod managers such as MO or Vortex. It has nothing to do with how many Nexus mods you have.

[anjenthedog]

Quote

It has nothing to do with how many Nexus mods you have.

I never said it had anything to do with *how many* nexus sourced mods I have. I was implying that I use Nexus a lot. AFAIK it's automatically set by vortex if the vortex download link is used from a nexus page, because when I install a locally downloaded mod and uncheck it (probably not necessary, but whatever) to remove the warning, it is set back to true (checked) the next time I download a mod from nexus using the vortex link. 

[Just Don't]

33 minutes ago, anjenthedog said:

I never said it had anything to do with *how many* nexus sourced mods I have. I was implying that I use Nexus a lot. AFAIK it's automatically set by vortex if the vortex download link is used from a nexus page, because when I install a locally downloaded mod and uncheck it (probably not necessary, but whatever) to remove the warning, it is set back to true (checked) the next time I download a mod from nexus using the vortex link. 

Still doesn't make any sense. The purpose of that patch is to change the file path of the files FNIS generates from the default ...\Data\... to the file structure you find in mod managers like MO/Vortex. It shouldn't enable or disable itself depending on the source of the mod. Vortex is likely enabling it automatically because it's a patch made for MO/Vortex (and Vortex likes to do things automatically). So whenever you use Vortex after disabling that patch (why?) Vortex enables it again.