Oniki's Kinky World Build 453 v0.9.9 - LoversLab Edition [BiterBit's QoL]

[magdalenesophia]

 

Does it work in your game?

 

On 8/4/2026 at 7:49 PM, Gentlelovely said:

Yes.

[Dustercoat0321]

On 8/11/2026 at 1:50 AM, Ulrich Rence said:

[Bug Report / Help] SacsErrorException on every WooHoo attempt — KW v0.9.9 (453)

Hi everyone,

I've been dealing with a persistent bug for a couple of weeks now and I've run out of ideas, so I'm hoping someone here  can point me in the right direction.

The symptom: When I ask two Sims to WooHoo, they walk to the location, undress, stand there for about a second doing the "undress" animation, and then just get dressed again — no actual sex animation plays, and the interaction silently cancels.

The error (from ScriptError logs, happens every single time):

Oniki.KinkyMod v0.9.9 (453)
Sims3.SimIFace.SacsErrorException:
#0: throw in Sims3.SimIFace.StateMachineClient:CheckForException()
#1: call in Sims3.SimIFace.StateMachineClient:SetActor(string, ObjectGuid, BridgeOrigin)
#2: call in Sims3.SimIFace.StateMachineClient:SetActor(string, IHasScriptProxy)
#3: callvirt in Oniki.Gameplay.WooHooInstanceNonSync:SetSMCActors()
#4: callvirt in Oniki.Gameplay.WooHooInstance:Loop()
#5: callvirt in Oniki.Interactions.WooHooLoop:Run()
#6: in Sims3.Gameplay.Interactions.InteractionInstance:RunInteractionWithoutCleanup()
#7: in Sims3.Gameplay.ActorSystems.InteractionQueue:ProcessOneInteraction()
#8: in Sims3.Gameplay.Actors.Sim:DoInteraction()
#9: in Sims3.Gameplay.Actors.Sim:Simulate()
#10: in ScriptCore.ScriptProxy:Simulate()

What I've already ruled out (tested one at a time, cache cleared and game restarted between each test):

• Not a specific animation pack — happens even with all optional animation packs removed, and I already found/removed two genuinely broken packs along the way (one had a corrupted XML, one referenced an undefined "Tease" category), neither fixed this.
• Not NRaas Woohooer — removed it entirely, still happens.
• Not any other script mod — removed every other script mod (all NRaas modules except Traveler, LazyDuchess Smooth Patch + other LazyDuchess mods, cmarXmods MorphingPenis, CEN_S3_Poledance, Dan_MSCMod, and several smaller ones), leaving only the KinkyWorld Core + animation packs loaded. Still happens.
• Not a specific Sim — tested with many different Sims, male and female, custom and pre-made.
• Not a specific location/object — happens on every object I've tried (bed, floor, sofa, etc.).
• Not save-specific — happens on a brand new save/world with freshly created Sims too.
• Not a corrupted install — fully reinstalled the base game and redownloaded the entire KinkyWorld Core fresh, matching versions. Still happens.
• Not a Windows/driver issue as far as I can tell — tried disabling Core Isolation/Memory Integrity, checked Windows Defender exclusions/quarantine history. Still happens.

One thing I can't rule out myself: the bug started at the end of July, after not having any issues before that. I'm not aware of anything I changed on my end around that time other than a routine Windows update, so it's possible something upstream (Windows update, or coincidentally a mod update) changed something KW relies on — but I have no way to confirm this from my side.

My setup:

• KinkyWorld Core v0.9.9 (453)
• Windows, Intel i3-12100F, AMD Radeon RX 6500 XT
• Full expansion/stuff pack collection (BaseGame through EP11)
• I do use body/skin CC (default replacements) — happy to test without it if that's a likely lead

Has anyone seen this exact SacsErrorException in SetSMCActors before? Any idea what could cause the actor-to-animation binding to fail at the state machine level like this, given it's completely consistent regardless of Sim, location, or other mods? Any pointers on further diagnostics I could run would be hugely appreciated. Thanks in advance!

In case you haven't done the Alder Lake patch, it might be worth checking out.

[Gentlelovely]

15 hours ago, magdalenesophia said:

 

Does it work in your game?

 

Yep, works perfectly fine.

[BiterBit]

On 8/9/2026 at 11:58 PM, sugarcakerun said:

Hi BiterBit, first of all thank you for your KW fixes! I only recently upgraded from an older version and the experience is so much better now. Really appreciate this! 

 

I do have a problem with whoring: my sim never gained any whore title nor got any call girl or escort jobs despite meeting the requirement of the sims serviced. I tried "register as professional" and using nraas MC to get the "professional whore" job but still nothing. Sex skill is at level 10. Any insight into this would be super helpful! 

 

Hi sugarcakerun!

 

Actually, checking the code, I see no actual bug or errors, but there are many criterias to reach for that kind of titles.

 

The title is recalculated each time by WooHooSkill.Title. The point is probably that the requirements aren’t just “Sims serviced.” For each title, the following are required together:

 

Skill level
Customers number
Earnings

 

On default tuning, these should be the requirements:

Slums: skill 2, 2 customers, 500 earnings
Downtown: skill 4, 6 customers, 2,000 earnings
Callgirl: skill 6, 18 customers, 6,000 earnings
Escort: skill 8, 36 customers, 15,000 earnings
 

Inside Miscellaneous, you can find "Kinky Tuning" that also allows you to edit these parameters individually - you may try with that as a chance to customize your experience.

[BiterBit]

On 8/10/2026 at 6:50 PM, Ulrich Rence said:

[Bug Report / Help] SacsErrorException on every WooHoo attempt — KW v0.9.9 (453)

Hi everyone,

I've been dealing with a persistent bug for a couple of weeks now and I've run out of ideas, so I'm hoping someone here  can point me in the right direction.

The symptom: When I ask two Sims to WooHoo, they walk to the location, undress, stand there for about a second doing the "undress" animation, and then just get dressed again — no actual sex animation plays, and the interaction silently cancels.

The error (from ScriptError logs, happens every single time):

Oniki.KinkyMod v0.9.9 (453)
Sims3.SimIFace.SacsErrorException:
#0: throw in Sims3.SimIFace.StateMachineClient:CheckForException()
#1: call in Sims3.SimIFace.StateMachineClient:SetActor(string, ObjectGuid, BridgeOrigin)
#2: call in Sims3.SimIFace.StateMachineClient:SetActor(string, IHasScriptProxy)
#3: callvirt in Oniki.Gameplay.WooHooInstanceNonSync:SetSMCActors()
#4: callvirt in Oniki.Gameplay.WooHooInstance:Loop()
#5: callvirt in Oniki.Interactions.WooHooLoop:Run()
#6: in Sims3.Gameplay.Interactions.InteractionInstance:RunInteractionWithoutCleanup()
#7: in Sims3.Gameplay.ActorSystems.InteractionQueue:ProcessOneInteraction()
#8: in Sims3.Gameplay.Actors.Sim:DoInteraction()
#9: in Sims3.Gameplay.Actors.Sim:Simulate()
#10: in ScriptCore.ScriptProxy:Simulate()

What I've already ruled out (tested one at a time, cache cleared and game restarted between each test):

• Not a specific animation pack — happens even with all optional animation packs removed, and I already found/removed two genuinely broken packs along the way (one had a corrupted XML, one referenced an undefined "Tease" category), neither fixed this.
• Not NRaas Woohooer — removed it entirely, still happens.
• Not any other script mod — removed every other script mod (all NRaas modules except Traveler, LazyDuchess Smooth Patch + other LazyDuchess mods, cmarXmods MorphingPenis, CEN_S3_Poledance, Dan_MSCMod, and several smaller ones), leaving only the KinkyWorld Core + animation packs loaded. Still happens.
• Not a specific Sim — tested with many different Sims, male and female, custom and pre-made.
• Not a specific location/object — happens on every object I've tried (bed, floor, sofa, etc.).
• Not save-specific — happens on a brand new save/world with freshly created Sims too.
• Not a corrupted install — fully reinstalled the base game and redownloaded the entire KinkyWorld Core fresh, matching versions. Still happens.
• Not a Windows/driver issue as far as I can tell — tried disabling Core Isolation/Memory Integrity, checked Windows Defender exclusions/quarantine history. Still happens.

One thing I can't rule out myself: the bug started at the end of July, after not having any issues before that. I'm not aware of anything I changed on my end around that time other than a routine Windows update, so it's possible something upstream (Windows update, or coincidentally a mod update) changed something KW relies on — but I have no way to confirm this from my side.

My setup:

• KinkyWorld Core v0.9.9 (453)
• Windows, Intel i3-12100F, AMD Radeon RX 6500 XT
• Full expansion/stuff pack collection (BaseGame through EP11)
• I do use body/skin CC (default replacements) — happy to test without it if that's a likely lead

Has anyone seen this exact SacsErrorException in SetSMCActors before? Any idea what could cause the actor-to-animation binding to fail at the state machine level like this, given it's completely consistent regardless of Sim, location, or other mods? Any pointers on further diagnostics I could run would be hugely appreciated. Thanks in advance!

 

Hi Ulrich.

 

This is a pretty legacy bug I think, but as well, I think there's a way to solve it.

 

The stack trace you reported doesn’t seem to indicate an issue with a single animation pack, NRaas, or a specific Sim/object, rather than the use of "WooHooInstanceNonSync:SetSMCActors()".

 

In the code, WooHooInstanceNonSync is only used when the WooHooNonSync option is enabled: that option is in the animations menu and is set to false by default, so the first practical troubleshooting step would be to disable WooHooNonSync. In the menu it should be something like:

Kinky World -> Sex & Animations -> Animation Settings -> Non-Synched Animations = OFF. Then, I would save and reload the game/savefile.

 

Everything comes back, in theory: in the normal path, KW acquires the woohooinstance state machine, while in the NonSync path, it creates a separate state machine, (kw_social_generic), for each Sim and calls "SetActor(“x”, sim)".

 

The error occurs right there, before KW actually gets around to playing the sex clip. This explains why it happens with any pack, Sim, and location, I think.

 

It's a pretty old setting and I've personally never used it - let's just say that at this point it could also be deleted from the mod or made "no-op".

 

Let me know if you get to solve this.

[BiterBit]

Thanks a lot for your support and appreciation @Max Rock, @Gentlelovely , @Phocan and everyone else.

 

I'm really trying to get better.

 

I'll keep on working at least on the KW Settings explorer for anyone to use.

 

Thanks again and be safe and happy everyone ❤️