Quick Reply
Search this Thread
Test Subject
Original Poster
#1 Old 24th Sep 2025 at 4:19 PM
Default Base Game sofa throws error when trying to sit on it?
One day I was playing with the Goth's and wanted Mortimer to study cooking, so I sent him to the bookcase, where it then threw an error. It was a cc bookcase I sent him to, so I thought it was just bad cc, and sent him to a normal vanilla bookcase instead. It threw an error again. I figured it was some sort of mod conflict, maybe something that messes with a studying interaction.

I run the error log through 'What Caused This?' but it comes up with nothing. I create a test hood and use a test sim to interact with the bookcase, but no error pops up. Strange. I then remember that the error log mentioned something about a sofa. I buy the same sofa Mortimer had in his house and trying and make her sit on it. The error pops up. I pull out other sofas, vanilla and cc, but the error doesn't appear for them, just this one sofa, and it's a base game vanilla sofa. I figure maybe a cc object is messing with this sofa, so I exit the game and remove my entire downloads folder to a temp location and reload the test hood. The error still pops up. She can play on it, react to it, but she can't sit on it.

I am now very confused and distressed, it's not cc causing the problem, I have no idea what the issue could be. I've included a picture of the sofa in question, it's the fancy red one in the middle.

I would like to mention I have recently reinstalled the sims 2 into a different drive, and I have already had to reinstall it twice because freetime didn't install properly. I am prepared to do it again, but I wanted to ask in case anyone had a solution.
Screenshots
Mad Poster
#2 Old 24th Sep 2025 at 4:36 PM
Chances are it could be a GUID conflict, where a CC sofa shares (at least) one of the GUIDs with that couch, but not the main one. It can cause errors while in use, problems with placing one or both items, or similar issues.

.SimPE has a GUID scanner, and I think at least one of the more recent programs has this as well. Other than that you could try the 50/50 method (no errors = likely found problem item).
Mad Poster
#3 Old 24th Sep 2025 at 4:48 PM
Quote: Originally posted by simmer22
Chances are it could be a GUID conflict, where a CC sofa shares (at least) one of the GUIDs with that couch, but not the main one. It can cause errors while in use, problems with placing one or both items, or similar issues.

.SimPE has a GUID scanner, and I think at least one of the more recent programs has this as well. Other than that you could try the 50/50 method (no errors = likely found problem item).


Except they said that the error persisted with no CC.
Mad Poster
#4 Old 24th Sep 2025 at 4:50 PM Last edited by simmer22 : 24th Sep 2025 at 5:02 PM.
Could be the error is persistent in the presence of old cache files - try removing the cache files if you haven't done so, as they can retain some information from CC even when the CC item is gone from the Downloads folder.

If you're using the CEP, keep the "_EnableColorOptionsGMND" file in the Downloads folder while testing - I don't think removing it causes errors (can cause some trouble with recoloring in SimPE), but suddenly you're also dealing with missing swatches and the like.
Mad Poster
#5 Old 24th Sep 2025 at 9:30 PM
Test Subject
Original Poster
#6 Old 24th Sep 2025 at 10:06 PM
Quote: Originally posted by simmer22
Could be the error is persistent in the presence of old cache files - try removing the cache files if you haven't done so, as they can retain some information from CC even when the CC item is gone from the Downloads folder.

If you're using the CEP, keep the "_EnableColorOptionsGMND" file in the Downloads folder while testing - I don't think removing it causes errors (can cause some trouble with recoloring in SimPE), but suddenly you're also dealing with missing swatches and the like.


Ok, i'll remove cc again while keeping deleting the cache and keeping the enablecolouroptionsdmnd in while doing it and see if anything changes. I'll see about using SimPE to check GUID as well.
Test Subject
Original Poster
#7 Old 24th Sep 2025 at 11:21 PM
Quote: Originally posted by kestrellyn
Post the error log.


Build: 1.17.0.66
at Oct 11 2008,15:12:07

Object id: 476
name: N001_User00000 - ghju
Stack size: 9
Error: Too many iterations.
Iterations: 1000000
Frame 8:
Stack Object id: 355
Stack Object name: Sofa - Colonial 1 (2,0)
Node: 5
Tree: id 8263 name 'Get in Temp 0 & 1 & 2 - Sofa Tile IDs' version -32758
from SofaGlobals
Prim state: 0
Params: Locals: 327 0 0 256 0
Frame 7:
Stack Object id: 355
Stack Object name: Sofa - Colonial 1 (2,0)
Node: 5
Tree: id 8264 name 'Sit - Try Route' version -32758
from SofaGlobals
Prim state: 0
Params: Locals: 355 0 0 0 0 0
Frame 6:
Stack Object id: 355
Stack Object name: Sofa - Colonial 1 (2,0)
Node: 12
Tree: id 8192 name 'Function - Sit' version -32738
from SofaGlobals
Prim state: 0
Params: 19 Locals: 355
Frame 5:
Stack Object id: 355
Stack Object name: Sofa - Colonial 1 (2,0)
Node: 2
Tree: id 8194 name 'Interaction - Sit' version -32733
from SofaGlobals
Prim state: 0
Params: Locals: 0 0 0
Frame 4:
Stack Object id: 476
Stack Object name: N001_User00000 - ghju
Node: 5
Tree: id 281 name 'Wait For Notify' version 8
from global
Prim state: 1
Params: 0 1 Locals:
Frame 3:
Stack Object id: 476
Stack Object name: N001_User00000 - ghju
Node: 1
Tree: id 8282 name 'Function - Main - Check Queue' version 50
from PersonGlobals
Prim state: 0
Params: Locals: 355
Frame 2:
Stack Object id: 476
Stack Object name: N001_User00000 - ghju
Node: 2
Tree: id 8283 name 'Function - Main - Loop' version 96
from PersonGlobals
Prim state: 0
Params: 5 20 1 Locals: 0
Frame 1:
Stack Object id: 476
Stack Object name: N001_User00000 - ghju
Node: 6
Tree: id 8193 name 'Function - Main' version 118
from PersonGlobals
Prim state: 0
Params: Locals: 5 20 0
Frame 0:
Stack Object id: 476
Stack Object name: N001_User00000 - ghju
Node: 1
Tree: id 4096 name 'Function - Main' version 2
from TemplatePerson
Prim state: 0
Params: Locals:
Mad Poster
#8 Old 25th Sep 2025 at 2:17 AM
It appears the sofa doesn't have any tiles with a certain multi-tile subindex. I can't find any listing of what that subindex indicates, but I suspect that if you just delete the sofa and buy a new one it will have the right data.
Test Subject
Original Poster
#9 Old 25th Sep 2025 at 3:08 AM
Quote: Originally posted by kestrellyn
It appears the sofa doesn't have any tiles with a certain multi-tile subindex. I can't find any listing of what that subindex indicates, but I suspect that if you just delete the sofa and buy a new one it will have the right data.


I already did that and it still showed an error
Test Subject
Original Poster
#10 Old 25th Sep 2025 at 8:56 PM
I've figured out the solution. I took my sims 2 folder to the desktop to allow the game to regenerate a new folder and when I loaded into a lot in Belladonna Cove and put down the sofa, It didn't error, so I figure it's something wrong with the folder itself. So I start experimenting by taking things out and putting things in.

Eventually, I swap out my Test hood and Belladonna cove with each other. There is an error in the test hood, but not in belladonna cove. I am a little stressed thinking there is something wrong with the hoods. But then I get an idea. I go into the test hood, move the test sim out and then back into the lot. Bingo, the error is gone.

So if anyone else has this problem. Just move the sim family in and out.
Test Subject
Original Poster
#11 Old 25th Sep 2025 at 10:55 PM
Nevermind, it doesn't work with the goth's, their sofa is still throwing errors, I am just going to have to replace the sofa with a different one
Mad Poster
#12 Old 26th Sep 2025 at 5:06 PM
Quote: Originally posted by ToastedGhost88
Nevermind, it doesn't work with the goth's, their sofa is still throwing errors, I am just going to have to replace the sofa with a different one


Have you tried running Hoodchecker? It might pick it up if there's a problem in the hood.
Test Subject
Original Poster
#13 Old 28th Sep 2025 at 11:46 PM
Quote: Originally posted by Charity
Have you tried running Hoodchecker? It might pick it up if there's a problem in the hood.


I'll try it
Back to top