SexoutNG - Beta (2.10.93b10) release thread

[prideslayer]

Good catch loogie. I think I might have it that way in one of the examples, or did at one point and then fixed it. Geckscript is wack!

[Odessa]

Tested that, removing the commas doesn't make any difference. I'm pretty sure the compiler just ignores commas like extra white space, I always use them to seperate arguments.

 

Glancing at the script (fnSexoutActRunFull), I am pretty sure the problem is:

 

  let arActors := ar_List("actorA", "actorB", "actorC", "actorX") ; List arrays have numeric keys!


  ; Find our target and handle getself

  foreach element <- arActors

    let sActor := element["Value"]

    let sKey := element["Key"] ; This line raises error, because sKey is string_var not number

[prideslayer]

Not all commas are ignored, this is one place where they aren't. I had the same problem when I redid the helper spell (SexoutNGDoPlayerVaginal) as an example, and it went away when I removed the commas. The key/value code you're looking at is correct, the array structure there is something like 'element["actorA"] = refActor'.

The parenthesis might also be causing the problem, try removing those. Sometimes they work (are ignored), sometimes not.

[prideslayer]

Bah the colors were hiding your comments in the script from my eyes. I'm taking a closer look, but this has been working in my testing. Maybe I edited something badly on accident.

Edit: Ok, it's showing up in the helper too, same spot. How did that slip through.. and really why the hell is the scene working with that problem. Standby for beta11

[prideslayer]

Bah that was just leftover copypasta nonsense, that's why it's not hurting anything. sKey isn't even used in that block. Serves me right. The next beta release will have that "let sKey" line removed but it's not worth a new beta release on its own.

[Odessa]

Cool.

 

Sorry if I'm stepping on your toes, but I notice you forgot to sv_Destruct the string_vars in that script.

[prideslayer]

Now, for those crosses, that's something I'm already aware of, but I don't have a good way at present to fix the issue. One cross sits at a different height above the terrain than the others, but all the alignment variables have to go on right now is the anim # -- which can be used for any cross.

There is one cross that is correctly positioned that all the anims align correctly with, and the other crosses have a bad vertical offset. Ideally the NIFs themselves need fixed but I haven't looked at just what's required to do that. It might just be something easy to adjust in nifskope on them. If not, then I need to refactor the whole refSurface thing to setup different offsets based on the combination of refSurface and anim #.

[prideslayer]

Not stepping on toes, I'll take care of that now as well.

[prideslayer]

Better?

http://git.loverslab.com/prideslayer/sexout/commit/11d50a3c557520191741fb2594dc17413da49254

[prideslayer]

2.8.91Beta11 in OP

Changes:

- Fixed a case where unlock would not happen if SAN/CSE returned an error.

[prideslayer]

For the record I have no idea why this:

      if (actorA.GetIsCreature) && (0 == actorB.GetIsCreature)        ; Creature time!        let Anim := call fnSexoutRandomizeCreatureA actorA nxKey        if (0 == Anim)          let fReason := 9.2        endif      elseif actorB.GetIsCreature        ; person fucks creature.  not in this version.        let fReason := 9.1

When called as this:

fnSNNXA: Final A:Mirelurk(0A0A7973)

fnSNNXA: Final B:Butch(00000014)

fnSNNXA: Final C:<no name>(00000000)

fnSNNXA: Final X:<no name>(00000000)

Is resulting in this:

fnSoRandAct: In randomizerfnSoRandAct: Randomizing for NGfnSoRandAct: na 2fnSoRandAct: 2 actors anim 0NGSAN (4): Returning 9.100000CSE: SES done with CSE=1 SAN=9.100000, Stage=100 SEU next.

It should be returning 9.2 unless I'm too tired to be reading this right.

A is a creature, B is not, an anim is 0.

[Vachnic]

okies, got the beta. Gonna test it now. Thanks

[prideslayer]

No, thank YOU sir. This bug has been around for a while and nobody has been able to track it down, because nobody could provide the logs from the right time frame. You did and as a result.. just a few minutes to fix.

[MidnightVT]

So to update to the beta I just download the Sexout.esm file from the OP and overwrite that in my data folder? 

 

IM having issues with Spunk it says i need verison 2.8.9b1 or greater so im trying to fix that but its not working. 

[prideslayer]

I think your problem is your NVSE install. Everything else in your screenshot in the spunk thread looks right, so you probably didn't install NVSE properly -- or didn't launch the game with NVSE. It's not like Skyrim, just having it in the directory isn't enough, you need to launch the game with the nvse launcher.

[MidnightVT]

I think your problem is your NVSE install. Everything else in your screenshot in the spunk thread looks right, so you probably didn't install NVSE properly -- or didn't launch the game with NVSE. It's not like Skyrim, just having it in the directory isn't enough, you need to launch the game with the nvse launcher.

 

Ok so I downloaded the zip file. Opened it and extracted it all to the SteamLibrary/SteamApps/Common/FalloutNewVegas folder (where i see the exe files)

 

I then launch nvse.loader.exe to run the game. Iv also tried clicking launch NVSE from FOMM. Both get the same error

 

 

 

I think the biggest issue is that it is asking for 2.8.90b1+ and FOMM only shows 2.8.90 the official. I did download the new sexout.esm from the OP here and overwrite but not sure if that is enough?

[MidnightVT]

I think i have the beta working right now? it shows this when i load the game.. spunk still crashes but thats not your problem i guess.

 

[Vachnic]

Ok, so I did the, by now, usual playthrough: sex in megaton, afterwards off to the mirelurks in Anchorage Memorial, then back to Megaton.

 

This time the mirelurks were stalkers and no sex act happened (as usual), HOWEVER... when I went back to Megaton I initiated sex, which worked! and right after I was assaulted, which also worked! *does a little happy dance*

 

Below is the debug file. I had a look at it, but strangely I am not seeing anything registered there about the mirelurks or even before that. If I read it correctly, the log starts after I went back to Megaton and initiated a sex act with the nearest NPC (Lucas Simms). I did have logging running for the whole playthrough. Kinda weird.

If you need me to, I can always do the playthrough again.

debugnewbeta.txt

[prideslayer]

I don't need the debug, it's working as intended if mirelurks did not work but the rest did. We don't have any mirelurk anims and for some reason they are failing that creature check or whatever anyway.

Midnight your install looks good to me.

[prideslayer]

I'm rolling this up and releasing it as the first in the 2.9 branch unless there are major objections within the next few minutes. This latest fix is a big enough deal that the more players that have it, the better.

[prideslayer]

2.9.92Beta1 in OP

Changes:

- A smarter InUse check that can clear (most) invalid locks.

- The sound token script no longer checks InUse.

GOOD NEWS for players! This beta, and the release to come, SHOULD allow actors to automatically "unlock" when held by invalid locks, without having to make a clean save.

WARNING to modders: This new inuse has some "extra" debugging in it for the beta. If sexout is in "debug mode" and your mod repeatedly calls fnSexoutActorInuse in a rapid loop, it's going to spam the hell out of the debug log. If this is you, do yourself and everyone else a favor and put a short delay between each call.

This new inuse check goes a few steps further and will check for some other spells and NX vars when the lock flag is on. In many cases it can tell immediately if the lock is valid, clear it, and proceed. In cases where the lock might actually be valid, but it cannot determine this, it puts a timestamp on the actor.

If the next time inuse is checked on that actor, if the actor hasn't unlocked and the timestamp is still present, the actor is automatically unlocked if 5 seconds or more has elapsed since the flag was placed on them. Any successful act clears the timestamp.

[Loogie]

I'll try this with that issue I was having with Bittercup and report back.

[ljacquard]

Thank you for the new version (especially the bug fix).

[prideslayer]

2.9.92Beta2 in OP

Changes:

- Additional logging related to undress delay.

- Fixed a logging error.

- Simplified player undress determination code.

[ritualclarity]

It has been awhile. Now I have a nice base 2.9.91 install and with MO can run some test and fooling around. The Betas are just patches of the main stable release correct? Just need to be installed over the main files.