More Awesome Than You!

Build: 1.13.0.161
at Jun  9 2008,23:40:30

Object id: 375
name: Phone - Base - Wall - Atomic
Stack size: 5
Error: Hit Break Point Primitive.
Iterations: 42
  Frame 4:
    Stack Object id: 375
    Stack Object name: Phone - Base - Wall - Atomic
    Node: 0
    Tree: id 732 name 'CT - Object Error' version -32761
    from global
    Prim state: 0
    Params:    Locals:
  Frame 3:
    Stack Object id: 0
    Node: 0
    Tree: id -1 name 'No behavior' version 0
    from
    Prim state: 1
    Params:    Locals:
  Frame 2:
    Stack Object id: 375
    Stack Object name: Phone - Base - Wall - Atomic
    Node: 0
    Tree: id 280 name 'Idle' version 2
    from global
    Prim state: 0
    Params: 20000    Locals:
  Frame 1:
    Stack Object id: 375
    Stack Object name: Phone - Base - Wall - Atomic
    Node: 2
    Tree: id 8264 name 'Function - Main - Base - Wall' version -32758
    from PhoneGlobals
    Prim state: 0
    Params:    Locals: 375 293 0 0
  Frame 0:
    Stack Object id: 0
    Node: 0
    Tree: id 4097 name 'Function - Main' version 58
    from Phone_Base_Wall_Atomic
    Prim state: 0
    Params:    Locals: 0 0 0 0


Global Simulator Variables
 = 21
 = 18
 = 0
 = 514
 = 2
 = 48
 = 56
 = 6
 = 1997
 = 10
 = 259
 = 0
 = 0
 = 9817
 = 2
 = 1
 = 2
 = 1
 = -1
 = 0
 = -1
 = 0
 = 1

You probably just need to turn boolprop off while you're playing. 

Queenbrat:  Please read the FAQ regarding how to post an error message.  In short, save as a text file and attach to the post.

It sounds like you have a hack conflict.  You could try a binary search: take out half your hacks at a time and test to see if the problem continues.  If it does, you know the problem is in that half.  Take out half of the remaining hacks and test, etc.  Rinse, repeat until you narrow it down to one hack.

Also check to see that your hacks are up-to-date - old versions of hacks can play merry hell with game operation.

@Hellyes:  turning off debug mode (what you call "boolprop") would be the wrong thing to do.  That would be simply ignoring errors and pretending they don't exist.  Running with debug mode on does not affect gameplay and enables one to actually get an error message which might be helpful if someone is to help solve this problem.

Um-- shot in the dark here but-- is the Atomic phone one that came with Freetime? Because you might have an outdated CEP if that is the case.

I will refrain from mocking the noobs as I could be wrong about this because I never use phones in my hoods.

If not, search your downloads for anything with 'phone' in the name and yank them all.
Also, please edit your post to attach the error file to the post and give us a few words of content. If you don't, I will be forced to take the extreme measure of chastising you with my mad language skillz.

Hellyes, I find it hard to believe that after this game has been out so many years, someone can still be so ignorant. Because, you know, it's so much better to watch your Sims reset randomly than to know the cause so that you can fix it.  ::)

The only error I see is the one you forced to begin with.

Forced what JM ?How did I force the error exactly I just want the Sims to be able to use a phone.I attached 2 of the errors assuming I did that correctly since I dont know what I'm doing.Ive tried many different phones and Sims and cell phones and I always get an error message.Invalid Constant error or Hit Break Point Primitive are the 2 I usually get.I checked my hacks nothing with the word phone in them.TY anyone who can help.

Error code does not match either Phonehack or listed FTp3 code, so once again, I point the blame squarely at tight pants.

I copied exactly the errors in my Sim logs so I dont know what else you need to see.I can keep copying error logs since I have many of them now.

Nice try at a jab. Always a good idea to piss off a site owner when you want help.

"Tight pants" means that your error is caused by a hack/cc that is not from this site, or having two versions of the same hack in your game. Usually it's that you have an outdated hack from somewhere else that isn't updated, or is conflicting in a bad way with something else you have. Do binary search (removing half of hacks, then testing, removing/putting back in half as needed) until you can locate the culprit. I recommend doing this on a test account with no other cc if you have 2.5 gigs of cc like I do.

I dont have that much yet and obviously dont know what I am doing (sorry JM).Couldn't figure out how my pants were relevant.lol ty all I will try it

Since this person only has two posts, I can't know if they are being serious or not. So I'll just pretend they are because it makes me lol.