A few lingering questions

"igazor;c-16280078" wrote:
Back Porches: Those can be locked up too, or some combination of locks and gated fences can be used. But I think we've already established on a different thread that our preferred methods of child rearing are a bit different from each other. ;)

That's definitely true. Maybe I should just say that I have an "alternative parenting style" from most simmers, or that I like to raise "free-range children." Would that stop the looks I keep getting on the street? I'd really appreciate that.

"igazor;c-16280078" wrote:
We don't even know what half of the DE commands do, some should be avoided entirely, but the ones we are familiar with can be very helpful.

Hang on, did you just say... that you don't know something? About TS3? That's... now I'm really confused. And I think I need to sit down for a minute. ::deep breaths:: The world is spinning. Why is the world spinning? This doesn't make any sense...

Okay, I'm back. I think. I've used MC>go to work before, when my musician (rock star branch) got promoted to level 8 or 9 and wasn't going to go to work for four days (the game skipped assigning the next day's shift). The sim was at work for the entire shift length minus the time between the top of the hour and when I used the MC command, something like 8:40 to 12:00 for a job level with a four hour shift. I'm going to try that when it next comes up, as my sims tend to get promoted every day and I don't want them losing the next night's shift every time. Whenever there isn't a promotion, the game corrects the problem by the next day.

With the virtual memory problem, I was just wondering if it was weird that all three crash logs listed the total as exactly 2,047 Mb. The last time it crashed, I was careless and having fun redoing all my teens in CAS, and I kind of knew it could be a problem, but I thought I was about to quit, so I let myself be lazy and didn't purge RAM. It actually crashed a bit later, when I quit after saving (btw I successfully quit, and once at desktop it just said "an exception was raised" and asked if I wanted to debug), so I went back to a save from a few RL hours before. I've known for a long time that Edit Town is also an issue (surprisingly, I figured this one out myself—there was a noticeable increase in lag every time I returned to my current game), so whenever I'm redecorating another house in anticipation of moving out a child, I save the completed house to the bin, quit without saving, and then just replace the original house with my upgraded version the next time I load the game. And then I make a fresh save after the move, just in case.

Side not about purging RAM: When I was using the Ambitions alias to launch my game, it really really didn't like being put in windowed mode. Every time I quit (never "save and quit," of course), I ended up having to force quit the game, even when I had just loaded so that I could see if I knew how to purge. But force-quitting wasn't all that uncommon with Ambitions in general, even with a relatively fresh game session, and I didn't usually see any signs of corruption in the save that had to be force quit, even on my old computer. I could have missed the corruption, obviously, but I came to see needing to force quit as just the game being difficult. Now, however, I have a new (for me) SP that's more recent than Ambitions, so that alias launches the game, and I haven't had to force quit once, even the time it crashed. I know that Ambitions causes a few problems of its own, but I'd never read anything about windowed mode being one of them. Any thoughts?