Like jeromycraig states, it's them annoying brats that keep bringing friends home. Come to think of it, I've never seen my adults do it (though they did in S2). Here I am, trying to create socially awkward kids, and they just keep making friends.

Got it, thanks. In that case, could I interest someone into making a sim-with-tommygun animation whenever they enter a rabbithole (raincoat and fedora optional)? That way, I can feel like a real mobster.

All the new NPCs created by the game have a -100 hygiene and won't stick around. When I rummage through their trash, they immediately run out of the house and sprint away. When I invite them over, I have to call them several times before they show up, and then immediately get back into their car and drive off.
One of them is marked in blue on the map, all the others in orange. I assume Awesome is marking them on the map, but what is causing their inability to interact?

EDIT: For some reason, I'm also good friends with my car according to the relationship panel. Talk about taking vehicle enthusiast to a new level.

Still, one would expect it to get better after a while. Makes the thought of Sims 4 scary. Very scary.


As for my feature requests, there are two things that bug the bleep out of me.
1. I just despise it when sims take people home with them without asking me. I'd like a prompt to request my permission.
2. It takes hours to collect all the income from real estate. If we can check, purchase and sell real estate, why didn't EAxis allow us to collect all income from the computer as well?

Haven't been able to find mods for that in Sims 3, although I imagine they exist...

Well, it's been working for about two days now. Only 4 people in the entire neighborhood, so Charisma is a bit hard to raise. I assume the longer pauses at 4am and 9am are due to one of Awesome's processes. Going to add WA into the mix now.

So, will I have to do a ritualistic purification on a regular basis? There's no command to run through the neighborhood and fix only what EAxis fracked up? Is there a chance that my own sims get corrupted?

Alright, I'll delete my savegames, start a new game in Sunset Valley, create a new sim in CAS, make only that sim sacred, then send everyone else to the bottom of the ocean.

Yup, 1.26 did the same. I started out with 1.26 a few days ago. And they're not really saves. I can start a game, never save it at all, and the Analyzer will call the crash-dump a Corrupt Save. When I asked the author, he concluded it was custom content. You can read it in the Analyzer's comments thread should you feel so inclined.

Same crash location every time:
1.26 - Crash Address: 0x00d0edef "C:\Games\Sims\The Sims 3\Game\Bin\TS3W.exe":0x0001:0x0090ddef
1.29 - Crash Address: 0x00d22aef "C:\Games\Sims\The Sims 3\Game\Bin\TS3W.exe":0x0001:0x00921aef

Rapturing is dropping a neutron bomb on the neighborhood right? Complete genocide of all living things, while leaving the structures intact? Will the game repopulate with random weird looking sims afterwards?

Well, I am running on a relatively older system, an nForce 570 with an Athlon II X4, HD4850 and a first generation X-Fi. Has kept up with me so far. So how can I explain this then (got it from the crash-dumps)?

Memory load: 53%
Total physical memory: 6142 Mb
Available physical memory: 2849 Mb
Total page file memory: 8188 Mb
Available page file memory: 4239 Mb
Total virtual memory: 4095 Mb
Free virtual memory: 2945 Mb

Every single crash-log, never goes over 60%. And I've had the game running without Awesomemod for hours on one screen while playing a TV series and web browsing on another screen. But as soon as I put Awesomemod back in... 

Also, I did run them through the Analyzer. Same thing every single time, 'Corrupt Save Crash' at the same address. So, I asked the author for help, posted the logs, and he also pointed at Awesome as the cause.

Anything else I can do, or will I have to accept life a little less Awesome?

Okay, I have a save that crashes within 3-10 seconds of loading, slightly different every time. Speed is at 4, you don't need to actually do anything, but you're welcome to move the mouse if you want. I installed the base game, patched it to 1.26 first, later to 1.29. The only content installed is Riverview and Awesomemod. Best I can do, hope it helps.

http://oron.com/19wug8qdsaw8

EDIT:
I don't know if it's related in any way, but the Law of Conservation of Mass is not working for me either. Doesn't bug me that much, but I figured I'd mention it. A kid that starts out fat and never touches that burger again will still regain all the weight if he doesn't work out daily.

A few seconds?! It takes nearly 10 seconds to save!

Well, I do like a challenge for the sake of progress. Risking public humiliation, but when you say 'send', where exactly is it you want me to send it? And what files do you need? The 5 files in the "savename.sims3" directory only (neatly compressed of course)?

Runs off to annoy the heck out of the game.

Sorry...

[Exception info]
date: 2011-12-19
time: 16.45.54
type: ACCESS_VIOLATION reading address 0x00000030
address: 0x00d22aef "C:\Games\Sims\The Sims 3\Game\Bin\TS3W.exe":0x0001:0x00921aef

Worked for almost 20 minutes though.

The strange thing is, when I started playing about 3 days ago, I was running a game in Bridgeport with everything installed. It ran for nearly a day without a crash. By then the Speed 4 had slowed to a crawl. I attributed it to a CPU which kept maxing out. So I bought a new one. Now my CPU doesn't go over 80%, my RAM doesn't go higher than 60%, my FPS stays above 60, but these crashes have started happening (and Speed 4 still slows down to a crawl after a while unfortunately).
Why didn't the game crash that first day? Nothing changed except my CPU.

Sometimes the Sims reminds me of Windows. When it started, it was small, fast and efficient. Then they kept adding stuff onto it, until now it is a huge blob of code that has to be compiled in its entirety every time something needs to be tested.

So it's either a Bohrbug or a Mandelbug.

I have experienced this behavior on 1.26 with the December 9 package, and on 1.29 with the December 16 package. Those were/are the most recent packages for those versions, right?
Last time I played was during Ambitions. Didn't have a problem then, so it must have happened with one of the patches (since it's now also happening in the base game). If I'm not mistaken, all patch content is now neatly stored in delta-packages, so one of them probably contains the bug. Since my game crashes quite reliably, I could test any new versions if you want. At any patch level.

By the way, thanks for all the hard work and time you put into the mod.

I'm experiencing a series of crashes that I've been able to relate to AwesomeMod. In order to exclude as many options as possible, I was able to reproduce the crash by just installing the base game (updated to 1.26+) and AwesomeMod. Then starting a new game on an empty lot in Riverview. It still crashes within 15 minutes.

Always the same:
type: ACCESS_VIOLATION reading address 0x00000030
address: 0x00d0edef "C:\Games\Sims\The Sims 3\Game\Bin\TS3W.exe":0x0001:0x0090ddef

I'm now playing without AwesomeMod, but I'm definitely missing something. Anything I can do to help, let me know.