Jump to content

WW Tuning error. Better Exceptions states it's broken.


Recommended Posts

Posted

Hi.

 

Better Exceptions keeps telling me I am getting this error via WickedWhims_tuning.package Can someone tell me what the issue is and how to fix it. It doesn't appear to cause any harm but the amount of errors and requesters I get is driving me nuts!

 

I am using the latest version of WW and Nisa's Perversions and this mostly occurs at the strip club my sim owns and runs.   I have tried to replace the files in case they where corrupted but this didn't make a difference.

---a

 

Exception Date: 2024-10-08 21:16:52 Game Version: 1.109.207.1020-1.300.000.191.Release Category ID: si_state.py:952
Recommended Action No mods were listed in the exception but you do have mods installed.
Close your game, try removing handfuls of mods from your Mods folder and retry what you did when you received the exception.
If the exception does not occur then the problem is likely with that mod.
Check the mod download for any recent updates.
Possible Cause
(Confidence: 10%)
\WickedWhimsMod\TURBODRIVER_WickedWhims_Tuning.package
Reason Exception in Sim Timeline: Exception resuming Element (AttributeError: 'NoneType' object has no attribute 'si_state')
MCCC Version 2024.6.0
WickedWhims Version v181d
Mod Count 1924 packages, 43 scripts

 

 

Under broken mods it says:

 

Each section contains a list of broken mods, if there are any. Check for updates for each. If no update is available or the update doesn't fix the exception, remove the mod.
If any mod file is part of a multi-part mod, you should update or remove all of it.
All paths are relative to the Mods folder.

Invalid Tuning Mods
Package File
\WickedWhimsMod\TURBODRIVER_WickedWhims_Tuning.packageShow Tuning
Invalid Tuning
None running TURBODRIVER:WickedWhims_AffSuper_StripClub_Animation_Default:8110 on None
Posted

Pretty sure this is not caused by WW, but rather caught by its built-in error handling. Look at the confidence score given where it says "Possible Cause", it's at 10% (which is basically no confidence at all).

 

From my personal experience, when Better Exceptions reports a mod as the possible cause for an error, it's usually correct when confidence is at 80% or more, a solid lead at or above 60%, and pretty much no better than a random guess below that. I've had BE report WW as the possible cause with a confidence of up to 40% a few times and it was never WW that caused the issue. That's actually why I don't use BE anymore.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

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