Jump to content

LastException


Recommended Posts

I updated to the latest version yesterday (ver 2.1.2.093).  Since update every time I start the game I get an in game "WickedWhims Warning" message, saying that a lastException.txt was created and that it's possible that it was caused by WickedWhims.  

 

The message suggests that I should send this to you, so here it is.   Thanks!

 

Edit: noticed another file: WickedWhimsExceptions.txt.  Figured that might be helpful, also, so attaching here, too.

lastException.txt

WickedWhimsException.txt

Link to comment

I updated to the latest version yesterday (ver 2.1.2.093).  Since update every time I start the game I get an in game "WickedWhims Warning" message, saying that a lastException.txt was created and that it's possible that it was caused by WickedWhims.  

 

The message suggests that I should send this to you, so here it is.   Thanks!

 

Edit: noticed another file: WickedWhimsExceptions.txt.  Figured that might be helpful, also, so attaching here, too.

Try cleaning your save.

 

Save Clean

There is a chance that after updating or by bugs you will have issues with stuck variables. The best way to deal with them is to clean your save.

You can clean your save in two steps, but start with doing just the first step and see if that helped.

 

1. WickedWhims saves most extra data in external files that are not embedded withing game saves. Go to you 'saves' folder (Documents\Electronic Arts\The Sims 4\saves) and delete the folder called 'WickedWoohooMod'. You will lose all your settings related to WickedWhims and some extra data, but that should help with possibly stuck variables preventing using the mod.

 

2. Some extra data is saved using in-game systems. You can clean that by removing WickedWhims from your 'Mods' folder (Documents\Electronic Arts\The Sims 4\Mods), turning the game on and saving it. Saving the game without mods installed will remove any extra data that is not needed anymore. You will lose all of your WickedWhims content like skills, buffs and traits, but that should help with possibly stuck variables preventing using the mod.

Link to comment

 

Try cleaning your save.

 

Thank you for the great instruction.  I tried Save Clean, and while the game started OK without exceptions, the minute I set some WickedWhims settings I get the exceptions again. 

 

From another thread it appears that there are some issues with Azmodan22 pillory object, which might not have been updated to work with your latest version, so I will wait and see if this problem persists after those objects are updated.  I will report back if problem persists after eliminating that issue.  Thanks again!  

Link to comment

So I have started a separate thread with Azmodan22 on the exceptions regarding the devices.  However, I also did a Clean Save (full on, with both steps) and not using Azmodan22's devices and reproduced an exception.  

 

The exception happened right after the Butler quit.   However, the WickedWhims Warnings said it could be related to WW and that I should report.  So here it is.  Thanks!

lastException.txt

Link to comment

So I have started a separate thread with Azmodan22 on the exceptions regarding the devices.  However, I also did a Clean Save (full on, with both steps) and not using Azmodan22's devices and reproduced an exception.  

 

The exception happened right after the Butler quit.   However, the WickedWhims Warnings said it could be related to WW and that I should report.  So here it is.  Thanks!

It's not WW related but it's a pretty odd bug to see in the game code, it's just a missing argument and I wonder how they managed to compile the game and not notice it. It will probably be fixed in the next game update.

Link to comment

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

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

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. For more information, see our Privacy Policy & Terms of Use