WW Default Skin Issue

[keithstar]

I've used luumia's Vanilla default skin for years and recently switched to lamatisse's Rosewater default skin. Unfortunately, a problem occured after the 3rd time I opened the game last month, which never happened before. lamatisse's last update for skins was in 2020, after the skin colour update. The very same applies to luumia (if I remember correctly). I've tried every possibility to find out what could be the cause and unfortunately, it had to be WW.

 

As mentioned above, this never happened before. I even tried it with new save files but the issue was still there. The Sims look fine in CAS but not in live mode. This problem only applies to female Sims, by the way. Male Sims are completely unaffected.

[xcalibar]

Had this issue back in 2020.  Try deleting WW, redownload and install it and delete resource.cfg

[Scorpio]

14 hours ago, rikammah said:

As mentioned above, this never happened before. I even tried it with new save files but the issue was still there. The Sims look fine in CAS but not in live mode. This problem only applies to female Sims, by the way. Male Sims are completely unaffected.

Looks like you might have more than one default skin installed or maybe even duplicates or 2 different versions.

 

Don't delete your resource.cfg file as it contains the path info to help the game find your Mods.

 

But you should delete your localthumbcache.pkg when removing, adding, or updating Mods/CC or the game itself. 

[keithstar]

8 hours ago, Scorpio said:

Looks like you might have more than one default skin installed or maybe even duplicates or 2 different versions.

 

Don't delete your resource.cfg file as it contains the path info to help the game find your Mods.

 

But you should delete your localthumbcache.pkg when removing, adding, or updating Mods/CC or the game itself. 

As far as I know, I only have a few other non-default skins installed. They normally don't and shouldn't cause any conflicts. I even checked it up with the Tray Importer and Mod Conflict Detector. I also tried deleting the localthumbcache.package, as per your suggestion (did it with resource.cfg a week before). Unfortunately, the problem stayed.

[Scorpio]

32 minutes ago, rikammah said:

As far as I know, I only have a few other non-default skins installed. They normally don't and shouldn't cause any conflicts. I even checked it up with the Tray Importer and Mod Conflict Detector. I also tried deleting the localthumbcache.package, as per your suggestion (did it with resource.cfg a week before). Unfortunately, the problem stayed.

Other than removing what you most recently added the only way to hunt down a mystery cc is using the 50/50 Mod/CC removal method.

[keithstar]

21 hours ago, Scorpio said:

Other than removing what you most recently added the only way to hunt down a mystery cc is using the 50/50 Mod/CC removal method.

I tried this method as well, and it worked perfectly with everything else except WW. I'll have to try it again, though. Maybe I overlooked something. But that may be impossible because I also did it with the default skin and WW left in the mods folder only, and the problem stayed the same, even when switching between other default skins. I may have to contact turbodriver at this point.

 

Nevertheless, thank you.

[Scorpio]

8 minutes ago, rikammah said:

I tried this method as well, and it worked perfectly with everything else except WW. I'll have to try it again, though. Maybe I overlooked something. But that may be impossible because I also did it with the default skin and WW left in the mods folder only, and the problem stayed the same, even when switching between other default skins. I may have to contact turbodriver at this point.

 

Nevertheless, thank you.

I suspect that particular default Skin might be broken so unless it happens with any default skin you try of course.

Best way to prove is by removing everything except Wicked + Animations and test alone.

Delete your localthumbcache.pkg after removing Mods/CC.

If it works now then it's a broken Skin and not WW.

If not then you might try an Origin/Steam Game Repair next.

 

The other thing to try is removing all Mods/CC including WW.

Clear the localthumbcache and load the game vanilla but only up to the map screen.

Then do a 'Save As' 'Cleaned' or whatever and exit.

Now add only WW + Animations back into mods and test again.

 

If you use Wild Guys Female Body Details it also includes a default skin.

It's called Wild_Guys_Female Default Nude Skin and it should be removed if/when using another default Female Skin.

 

You could try these out one at a time to see if the issue is resolved.

 

Default Skins Use Only One.zip

[keithstar]

On 4/10/2022 at 9:34 PM, Scorpio said:

I suspect that particular default Skin might be broken so unless it happens with any default skin you try of course.

Best way to prove is by removing everything except Wicked + Animations and test alone.

Delete your localthumbcache.pkg after removing Mods/CC.

If it works now then it's a broken Skin and not WW.

If not then you might try an Origin/Steam Game Repair next.

 

The other thing to try is removing all Mods/CC including WW.

Clear the localthumbcache and load the game vanilla but only up to the map screen.

Then do a 'Save As' 'Cleaned' or whatever and exit.

Now add only WW + Animations back into mods and test again.

 

If you use Wild Guys Female Body Details it also includes a default skin.

It's called Wild_Guys_Female Default Nude Skin and it should be removed if/when using another default Female Skin.

 

You could try these out one at a time to see if the issue is resolved.

 

Default Skins Use Only One.zip 22.47 MB · 2 downloads

Sorry for the late reply, I was out of the city.

 

I have tried every valid option until I figured out what exactly was wrong.

The default skin itself isn't broken, but the female skin package has two packages merged into it - the overlay and luumia's female vanilla skin.

I've unmerged the packages and tried them on their own, but the skin itself didn't show up automatically as it should in CAS.

I already contacted lamatisse about the problem and, hopefully, they will fix it.

 

Thank you once more and have a good day.

[Scorpio]

2 hours ago, rikammah said:

The default skin itself isn't broken, but the female skin package has two packages merged into it - the overlay and luumia's female vanilla skin.

Nobody in their right mind would merge default skins as they are meant to be used one at a time.

 

The original default skin file I un-merged was 7,806KB using S4S and resulted with two 1KB files which are just junk.

This means they weren't actually merged in the normal sense we're used to.

I imagine when creating them they have to use some type of merge to combine things but that isn't it.

Un-merged files should be close to equal with the original file size so the math just doesn't add up.

 

So I think your just chasing a ghost that isn't the actual problem.

 

But it's possible the skin is broken or you still have another default skin hiding elsewhere.