Sexout animations stopped playing? Possible solution here!

[ButchDiavolo]

Hi guys,

 

I have had it happen several times that for no apparent reason the Sexout animations stopped playing. All the dialog e.d. were still available, but  no animation would start. Since I could not find a satisfactory solution to this problem on the forum/ google and I didn't know when exactly the animations stopped working (therefore I couldn't go back to a previous save where they did), I reininstalled F:NV completely. At the time this was not a major issue, since I had only just started a playthrough.

 

However, yesterday it happened again and this time I had about 80 hours invested in the playthrough, so a reinstall would have been... um... frustrating.

So I searched the forum anew and found this reply by Prideslayer on a similar issue.

 

Taking the information that it may be caused by a NVSE Extender (NX) variable, I uninstalled NVSE Extender (NOT NVSE itself), Sexout Core and Data and all Sexout based mods. Then I started up my last save, waited a few minutes and made a new ("clean") save. Then I reinstalled NVSE Extender, Sexout Core and Data and all Sexout based mods. And lo and behold, the animations worked again!

 

So, if your animations stop working and other fixes don't work, try the above method. It worked for me, so hopefully it will work for you as well.

 

 

[nightsyde]

Aside from 1) reloading to a previous saves and hoping I find one prior to the glitch occurring; 2) starting a new game and losing the hours of play time with the current character; 3) reinstalling SO and losing all of the 'experience' my character has had during the aforementioned hours of play time; or 4) giving up on SO and just playing through the game in hopes of the glitch fixing itself; is there any other ideas on how to fix the glitch?

 

The post you referenced mentioned an NX variable being flipped and the character being 'locked'. Not having a clue on modding, but being a bit of a programmer myself, I suspected that there was a recurring glitch where a scene started but "got lost" before it could actually initiate, so the "end loop" never happened (long layman's version of a locked NX variable). Is there a way to check for the variable and do a 'set.env' or some such to correct the issue without the rather tedious- and unreliable- work arounds?

 

//ns

[ButchDiavolo]

Aside from 1) reloading to a previous saves and hoping I find one prior to the glitch occurring; 2) starting a new game and losing the hours of play time with the current character; 3) reinstalling SO and losing all of the 'experience' my character has had during the aforementioned hours of play time; or 4) giving up on SO and just playing through the game in hopes of the glitch fixing itself; is there any other ideas on how to fix the glitch?

 

The post you referenced mentioned an NX variable being flipped and the character being 'locked'. Not having a clue on modding, but being a bit of a programmer myself, I suspected that there was a recurring glitch where a scene started but "got lost" before it could actually initiate, so the "end loop" never happened (long layman's version of a locked NX variable). Is there a way to check for the variable and do a 'set.env' or some such to correct the issue without the rather tedious- and unreliable- work arounds?

 

//ns

 

Alas, I have no idea about the NX issue. You would have to ask the creator of NX (good luck with that). I only posted this "fix" because I was tipped off by the referenced mention of a NX variable, and after reinstalling NVSE Extender SO worked again without the need for all the other work arounds. And, it STILL works. I haven't had the problem happen again *knocks wood*.

 

<start whine>

I am new to F:NV modding, but not new to modding other games. Compared to, for example, the Skyrim section of this forum, I found the F:NV community is a lot less helpful in troubleshooting issues. Quite possibly because F:NV is an older game. <end whine>

 

Whatever the reason may be, I posted this "fix" in the hope that it would help others.

 

[Molevalence]

Hmm I have invested about 40 hours into my current game and starting over is not an option to me. I will try your solution and see if this works.

[nightsyde]

FOUND IT!

 

Being an old school "keyboard jockey" and familiar with digging through the console of the TES games, I decided to do some playing. Doing so, I found two commands.

 

player.NX_ClrEVFl

player.NX_ClrEVFo

 

now, to my eyes, those say, "NX Clear Event Variable Float" and "... Focus"... maybe not what they really do, but when I ran them both, encounters started working again. Without a reload.

[Azmodan 102]

Not sure what all the effect of them could be but found this decription of the two commands.

 

http://www.gribbleshnibit.com/projects/NVSEDocs/#NX_ClrEVFl

 

Usage: (nothing) reference.NX_ClrEVFl key:String match:Integer

Parameters: 2
key:String
match:Integer

Return Type: Nothing

Condition Function: No

Introduced In: 9

Calling Convention: R

Description:

Clears an EV entry or the whole array.

Match is optional. If set to 2, clears all keys starting with the one you specify, e.g. "mymod" will clear all keys starting with the string "mymod".

 

 

http://www.gribbleshnibit.com/projects/NVSEDocs/#NX_ClrEVFo

Usage: (nothing) reference.NX_ClrEVFo key:String match:Integer

Parameters: 2
key:String
match:Integer

Return Type: Nothing

Condition Function: No

Introduced In: 9

Calling Convention: R

Description:

Clears an EV entry or the whole array.

 

[prideslayer]

FOUND IT!

 

Being an old school "keyboard jockey" and familiar with digging through the console of the TES games, I decided to do some playing. Doing so, I found two commands.

 

player.NX_ClrEVFl

player.NX_ClrEVFo

 

now, to my eyes, those say, "NX Clear Event Variable Float" and "... Focus"... maybe not what they really do, but when I ran them both, encounters started working again. Without a reload.

You're close.. they're Clear "Extended (actor) Variable" for "Float" and "Form".

 

They are documented in the NVSE Extender thread.

 

Clearing them will definitely clear any lock accidentally left behind, but it will clear everything else too, if you call them that way (without a param).

 

If you JUST want to clear the lock, you can:

player.NX_ClrEVFl "Sexout:Flags:InUse"
; or
player.NX_SetEVFl "Sexout:Flags:InUse" 0

The correct way to unlock (futureproof) is to

call fnSexoutActorUnlock player

But that's a UDF so you need to use the refID.

[MongkeQaan]

So I'm having the problem that the Sexout animations won't start, and I tried to use the commands you mentioned, but it kept on getting errors.

[Keldorn]

FOUND IT!

 

Being an old school "keyboard jockey" and familiar with digging through the console of the TES games, I decided to do some playing. Doing so, I found two commands.

 

player.NX_ClrEVFl

player.NX_ClrEVFo

 

now, to my eyes, those say, "NX Clear Event Variable Float" and "... Focus"... maybe not what they really do, but when I ran them both, encounters started working again. Without a reload.

 

 

Thx, i had the same problem and it worked like a charm.