Can't get sex to start

[caseymac1]

I am not sure what is wrong? It is probably something simple but I can find it. I am not getting a last-exception error. No crashes. No notifications. In fact this latest patch is very smooth running for all other areas of play; especially smoother in CAS.

No other problems, I already found all the other peoples script files that were causing 'script call errors' with the new sims4 patch. All of those problematic script files have been isolated. I was hopeful with this WW update...v165h [2021-07-24]. 

 

I get the same result. Try to start sex...the two talk, and then I can see that an X appears over the sex dialog icon, like it was canceled. WW sees all of my animations and they are all available until this...

I am calling this the auto- sex cancel before it starts bug. Once it happens, no sex options will appear ever again until game reload.

[Scorpio]

18 hours ago, caseymac1 said:

I was hopeful with this WW update...v165h [2021-07-24].

First thing is to update WW to 1.65g

Then delete your localthumbcache.pkg in your TS4 folder.

 

Kick start WW action using: WW Settings/Sex Settings/Autonomy Settings/Autonomy Intensity: Extreme

[Husk]

1 hour ago, Scorpio said:

First thing is to update WW to 1.65g

165h is the newest release tho ?

[Scorpio]

15 minutes ago, Husk said:

165h is the newest release tho ?

Oops, my bad, lol.

Updates so fast it's hard to remember...

[caseymac1]

I appreciate the try. I did all of that previously to include deleting my localthumbcache.pkg.  Also verified the SIMS4 software.

 

I did notice this:

In WW settings there are several unlabeled options. Not good... something is not lining up!

 

I didn't mention this earlier. I did test without any other mods present for an absolute clean run.  Just WW and animations. Same result.

 

One thing good about all of this. It forced me to clean up my mods folder.

[caseymac1]

Update. Finally, I am fixed. Turns out that I had 1 bad package file sitting in a stack of 5500 files. Took hours to find since the sims4 mod conflict detector missed it. For whatever reason, the older game version and older WW version didn't fail earlier with the culprit.

[Scorpio]

19 minutes ago, caseymac1 said:

Update. Finally, I am fixed. Turns out that I had 1 bad package file sitting in a stack of 5500 files. Took hours to find since the sims4 mod conflict detector missed it. For whatever reason, the older game version and older WW version didn't fail earlier with the culprit.

Good Job, those are the hardest to find.

Not all broken mods cause errors and some just cause trouble at random times.

Then of course some just prevent other mods from working right.

The last game patch was quite hard on mods.

 

I don't use conflict detector because it doesn't catch everything and sometimes detects conflicts when there isn't any.

It's just not reliable enough for me to trust it.

 

It helps to post the bad mods name here so it might help others with the same problem. 

[caseymac1]

15 hours ago, Scorpio said:

Good Job, those are the hardest to find.

Not all broken mods cause errors and some just cause trouble at random times.

Then of course some just prevent other mods from working right.

The last game patch was quite hard on mods.

 

I don't use conflict detector because it doesn't catch everything and sometimes detects conflicts when there isn't any.

It's just not reliable enough for me to trust it.

 

It helps to post the bad mods name here so it might help others with the same problem. 

 

This is the package file which will not work with the latest Sims4 patch 7-27-21 and WW v165h. 

I have quite a few sims3melancholic files. It was just this one for whatever reason?

[Scorpio]

6 hours ago, caseymac1 said:

 

This is the package file which will not work with the latest Sims4 patch 7-27-21 and WW v165h. 

I have quite a few sims3melancholic files. It was just this one for whatever reason?

Thanks, is that like cc makeup of some kind?

It's quite odd that CC would affect WW menus and it's not that old either.

 

I always get worried when I see sims3 in the name but most are just converted for sims4 anyway.

[caseymac1]

On 7/29/2021 at 6:07 AM, Scorpio said:

Thanks, is that like cc makeup of some kind?

It's quite odd that CC would affect WW menus and it's not that old either.

 

I always get worried when I see sims3 in the name but most are just converted for sims4 anyway.

Yes, me too when I see sims3 in title. It is just a make-up which file which I got with someone's sim download. I probably didn't even use it. 

I also found it very odd that a plain package file; just sitting in the mods folder, could affect Turbo's script file.

I did my testing with vanilla sims, so it wasn't like it was being used. Since I eliminated it from the mods folder, no issues at all!

The weird part is...see when it was downloaded...May. It was working just prior to the big cottage patch and the corresponding Turbo version. So, it is not like someone passed on a known buggy file. 

This was the hardest troubleshoot I ever went through on this game. Reminded me of Skyrim -SE issues with 200 or 300 mods on board. Everything is fine, then you get that one bad file which crashes the game hard.