SOLVED - Not Finishing

[Yazour]

I have three mods (That I have so far identified) that seem to have trouble ending an AAF scene: RSEII: Shenanigans, Sexual Harassment & Hardship.  All three mods sometimes trigger scenes that don't end.  Forcing the scenes to end via the 'End' key does not fix the problem as their follow up scripts fail to trigger.  What could be causing this?  I get no new error messages from AAF while debugging is active.

 

The only workaround I have so far is using Sex'Em'Up's masturbation feature to trigger the others mods to update.  This of course only works on the player.

 

I am not even sure where to start figuring this one out.  Any help would be appreciated.

UPDATE: Cleaning the AAF directory out and doing a new install of each AAF mod seems to have fixed it.

[Indarello]

I had some problems like this with "tree" animations, where you need to press left/right to change poses, so I removed this "tree" system in my patch

But I still not sure that it fizes the problem for 100% Try check what animations have problems

[Yazour]

Maybe it is certain animations.  I have noticed that none of the other animations trigger the HA (happiness) counter.  It is hard to test as the problem seems to be intermittent, so many animations... I will try removing as many as I can.

[mashup47]

1 hour ago, Yazour said:

Maybe it is certain animations.  I have noticed that none of the other animations trigger the HA (happiness) counter.  It is hard to test as the problem seems to be intermittent, so many animations... I will try removing as many as I can.

Have RSEII: Shenanigans Set to settlements Only or change it's scan time in the MCM to be larger (animation length + 15 sec) then the Scan time for Sexual Harassment Or vice versa. This mite lower the chances of this happening.

[Yazour]

I have uninstalled the animations, patches and AAF itself, then cleaned out the Data/AAF directory of all files.  Reinstalled AAF, as per the latest recommended thread, with only Leito's and Atomic installed.  Seems to be working fine now.  I suspect the problem was an old AAF compatibility patch that had become redundant, or perhaps old xml's that didn't get properly updated. Either way the fix is clean install of AAF.