Jump to content

Sexout Error: Aborting, actor is invalid, code: 1


Recommended Posts

Up until yesterday Sexout had been working reasonably okay. A few weird bugs (when I tried to have sex with girls or when girls raped me it would play "straight" sex animations instead of pussy eating animations and so on 95% of the time, actors would almost always disappear after sex/rape) but nothing that prevented me from enjoying the game. However now I have a bug where when I try to have sex I get an error saying "SexoutActRunFull: Aborting, actor is invalid, code: 1". I'm playing as a female player and I have called her Lara. Here is the rest of the debug logs from Sexout:

 

 

 

fnSAVa: Lara (00000014) Returning 1 (Reason: 7)
fnSAVA: Locktime: 71690 vs 77245
fnSAVa: Lara (00000014) Returning 1 (Reason: 7)
fnSAVA: Locktime: 71690 vs 77245
fnSAVa: Lara (00000014) Returning 1 (Reason: 7)
fnSAVA: Locktime: 71690 vs 77245
fnSAVa: Lara (00000014) Returning 1 (Reason: 7)
fnSAVA: Locktime: 71690 vs 77245
fnSAVa: Lara (00000014) Returning 1 (Reason: 7)
fnSAVA: Locktime: 71690 vs 77245
fnSAVa: Lara (00000014) Returning 1 (Reason: 7)
fnSAVA: Locktime: 71690 vs 77250
fnSAVa: Lara (00000014) Returning 1 (Reason: 7)
fnSAVA: Locktime: 71690 vs 77250
fnSAVa: Lara (00000014) Returning 1 (Reason: 7)
fnSexoutGetLocalActors: returning cached results for cell Mick & Ralph's (0010E02A)
fnSAR: Starting for 00000000
SexoutActRunFull (v2016-02-13) Called by: 0A08C33B
** Dumping Array #2949 **
Refs: 2 Owner 0A: Sexout.esm
[ actora ] : Mick (0010D8E3)
[ actorb ] : Lara (00000014)
[ IsOral ] : 1.000000
fnSAVA: Locktime: 71690 vs 77250
fnSAVa: Lara (00000014) Returning 1 (Reason: 7)
SexoutActRunFull: Aborting, actorB (Lara) is in use
SexoutActRunFull: Aborting, actor is invalid, code: 1
fnSAR: Completed for 00000000
fnSAVA: Locktime: 71690 vs 77250
fnSAVa: Lara (00000014) Returning 1 (Reason: 7)

 

 

 

I saw a thread about the same issue, but it did not help. I ran "Player.Dispel XX0397DF" (with the load order of my Sexout.esm file, which was 0A), and it didn't work. I've restarted the game and that hasn't worked. This happened after I quit the game while I still had a HUD showing up for an actor I had sex with (I think it was a bloatfly from Fertile Breeder, but I'm not entirely sure). The HUD that appears during sex and that fills to show how close another character is to climax was still visible, and I had exited the game without running "resurrect 1" on the bloatfly. When I started up the game again that HUD had disappeared, but now I can't have sex with anything! I have a mod installed which lets me ask a lot of NPCs for sex in exchange for a few caps (I think this comes from Sexout Tryout/Working Girl, but I'm not 100% sure on this), and when I try to have this exchange I'll get the caps but no sex animations will start.

 

I'm running the latest Sexout Beta and I have all of my mods up to date (NVSE 5.1b2, NX 16, etc). I am using quite a number of mods: Sexout Tryout as mentioned, Sexout Pregnancy, Sexout Offspring, Sexout Drugging, Fertile Breeder, Sexout Spunk, and SexoutSexAssult. I also have a few of the usual suspect mods installed such as Sexkey, CASM and MCM. I have no experience in making Fallout mods so I don't know if my theory on how this has happened is correct. In fact, I only bought the game in the Summer Sale and then I installed these mods a few hours in. I remember also around the same time this happened I had killed some Freeside Thugs and they had some weird Sexout token flags. I can't find these in my inventory. However I think I recall collecting these before and this issue didn't appear.

 

If I've missed out any information I'll be happy to provide more. Thanks in advance!

 

Link to comment

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. For more information, see our Privacy Policy & Terms of Use