More Awesome Than You!

Howdy. I've lurked this place for some time, but a recurrent error in my game has persuaded me to join and stick my head in the forums. Maybe something worthwhile will come of it.

The error is this: http://img.photobucket.com/albums/v37/zeean/ohdear.png

I have received this type of error before, this is arguably the shortest one as the other errors have extended well beyond my screen dimensions. I've encountered this error in both Riverview and Sunset Valley. This particular error coincided with with two of my sims leaving work, which makes sense compared to what I can decipher from the dialogue box. It's infrequent, I'd say I've had it about five times since installing Awesome in December or so.

I'm running base game, legal copy, patched up to 1.8.25.003002. I have the latest AM which functions just fine, I have no other mods. I can do a screencap of the CC in my folder if anyone thinks it's relevant. I also run Windows 7 on a system that is more than adequate for the game's system requirements. If I get the error again whilst playing tonight, I'll be sure to post screencaps of them also.

Finally, to be as clear as possible: however much I wish otherwise, I have no experience in modding or scripting or things that involve tampering with the files given to me by the game. On the other hand, I follow directions very well.

Anyway - if anyone has appropriate solutions or explanations, that would be rad. Thanks.

It looks like some kind of EAxis bug. You should update to the latest patch.

Around here, when Pescado updates, WE UPDATE!

Duly noted, I'll prod that in the morn.

I also have a sim in the criminal career track who, on two occasions on levels 6 and 7, did not have a carpool turn up. The hours counted down normally, but after the carpool hadn't turned up by the time work started, the count clocked over to "23 hours" or whatever it's meant to be. So, although they did not receive a penalty, they had to wait until the following work day to go to work again. Neither resetsim nor backtowork changed it, I didn't expect them to but thought it was worth a shot.

Would that be related to the flagrant system error, and/or something else hopefully resolved by patching?

No idea, never seen anything like that.

I'll try and grab screenies of that too, then, should it happen again. Thanks, though.