Random Crash to Desktop
J. M. Pescado:
I am not certain how that constitutes a threat.
ItchyNScratchy:
Quote from: myskaal on 2010 May 14, 01:36:32
Just my recommendation, insure that you have no corrupted files floating about: Completely uninstall. Delete everything. Run CCleaner.
Reinstall and patch.
Follow these instructions for installing the framework: http://sublimesims.net/smf/index.php?topic=1726.0
Drop awesome.package and aweconfig into C:\Program Files\Electronic Arts\The Sims 3\Mods\Packages (unless you specified a different directory for game install, then follow the path as needed).
Come back and let us know if it crashes again.
LOL Funny thing is that I've just come back from a nasty virus, thanks to one of those popups "Your system may be affected! Click to run this virus scan!", those crap malware things. So, I ended up having to wipe the PC, so Sims 3 is just newly installed, and CCleaner is one of the programs I've used in addressing issues with my PC. So, that's one step down at least! Patches are also up and running as well.
Followed Rainbow_Brite's suggestion about the Resource.cfg file. It was in both files--base and WA. That was the entire problem. The one thing I didn't try to remove! *headdesk* EA really could've made things easier for us. I hate that they've made it like pulling teeth to mod a game.
Thanks for all of your help, folks! I truly appreciate it! ;)
----------------------------------------------------------------------------------
ETA: Ok, we're back to square 1 again. After adding in aweconf to my Sims 3 WA/Mods/Packages/Hacks file, I'm back to where I started from. So, I've gone back, checked everything again with my files to make sure that everything was right where it should be, and it is. I'm not sure if I've done something wrong in putting in aweconf or what. So, here's what I did so this might be able to be fixed....
I went to the AwesomeMod Configuration, selected to generate the file, saved it to my desktop then moved it to my WA/Mods/Packages/Hacks file along with awesome package file. Rebooting the game makes it stick to about 1/3 of the way loading and doesn't go any further.
bluetank:
Are you people sure this CTD only happens to windows 7 users? I get the same type of crash and I'm running windows Vista 64bit with an nvidia card (GTX 295).
jezzer:
64-bit Vista has its own problems with running Sims 3 that result in a CTD. I've seen them discussing it on here. Try Search.
Rainbow_Brite:
Quote from: ItchyNScratchy on 2010 May 14, 11:30:08
ETA: Ok, we're back to square 1 again. After adding in aweconf to my Sims 3 WA/Mods/Packages/Hacks file, I'm back to where I started from. So, I've gone back, checked everything again with my files to make sure that everything was right where it should be, and it is. I'm not sure if I've done something wrong in putting in aweconf or what. So, here's what I did so this might be able to be fixed....
I went to the AwesomeMod Configuration, selected to generate the file, saved it to my desktop then moved it to my WA/Mods/Packages/Hacks file along with awesome package file. Rebooting the game makes it stick to about 1/3 of the way loading and doesn't go any further.
Do you have an updated version of the Resource.cfg file? I see that you made another file within the Packages folder so that's why I'm asking. If you are using a Resource.cfg file that you downloaded when the game first came out, it might not be coded to recognize multiple files within your Mods/Packages folder. If you're not sure, open up your Resource.cfg file in Notepad at paste:
Priority 500
DirectoryFiles Mods/Packages/... autoupdate
PackedFile Mods/Packages/*.package
PackedFile Mods/Packages/*/*.package
PackedFile Mods/Packages/*/*/*.package
PackedFile Mods/Packages/*/*/*/*.package
PackedFile Mods/Packages/*/*/*/*/*.package
PackedFile Mods/Packages/*.dbc
PackedFile Mods/Packages/*/*.dbc
This will also allow you to have .dbc files within your Mods/Packages folder. Anach has a tutorial on how to do that if you want to learn how to compile all of your CC. Usually when the game doesn't load all the way it is a framework fail. Obviously, you said it was working earlier so that's why I'm assuming it's your Resource.cfg file and not your framework. I could be wrong but that's the first thing that comes to mind. Make sure you have Awesome.package and Aweconfig.package in the SAME folder and you have the most recent version of AM.
Navigation
[0] Message Index
[#] Next page
[*] Previous page