What needs to go where to make AM work
coconnor:
I was just wondering if the fact that Sanscript listed them in his Sims 3 and World Adventures folders could be messing up his framework installation. If they're not serving any purpose, perhaps he should try removing them.
Silent Dreamer:
I had the text file in there for awhile back when I wasn't too aware of the inner workings of the mods folders for TS3 (more or less back in the first weeks of custom content) and it worked fine. The config file doesn't even look for non-package files so that shouldn't be an issue, really.
Edit: Oh wow, my brain went kaput there. I scrolled up to the original problem post. I need to stop replying to stuff before I am fully awake. Seriously.
Sanscript, your problem is the mods>files folder. Resource.cfg should be outside of the mods folder, in the "The Sims 3" folder within the application contents, and not in there.
Though my earlier suggestion of wiping the documents folder is still a good idea anyway since it'll probably take care of most of any other bug you may have read about.
sanscript:
I'm a female, for the record ;)
Thanks Silent Dreamer, I'll try your suggestions as soon as EA fixes this latest incarnation of their stupidity. Right now I'm working with a blank (reinstalled) base game without any mods or framework and it still won't even open the game launcher now that I've patched, hooray!
Silent Dreamer:
The launcher not opening problem can usually be fixed by wiping those cache files (which also happens by removing the documents folder) if you want to give it a try. Sometimes I have to open the game 3-4 times to get it to load properly but then its good to go after. I think that has more to do with how OSX is accessing the game, since EA in all their infinite wisdom decided to give us an emulator instead of an actual mac-structured game. Which, I guess, is both a blessing and a curse.
sanscript:
I gave that a try and the game still refused to open. I'm going to reinstall the base game and WA, refuse to patch for the moment, and uncheck my custom content box as the customer service people on EA's forums have suggested. That should at the very least get my game to open. It's ridiculous that I have to do that, but whatever. I'll take what I can get at this point. I'll deal with Awesome Mod when I know that my game is at least functioning.
Edit:
I figure I should update you guys, since you've been kind enough to give me several tips and suggestions. I reinstalled the base game and WA again, then refused to update. I unchecked the custom content box in the launcher. The game ran fine. I've now just installed the latest EA patch and it looks like my game is going to launch correctly. If it does, I'm going to try to install Awesome Mod again.
Second update: Ok, the patch installed correctly. I'm about to add in framework and Awesome Mod. Just to clarify, should I have the DDFMap.txt in Mods>Files? Or should I not even Have a Mods>Files folder at all? Nevermind, figured it out. I deleted the Mods>Files folder.
Third Update: YAY! Awesome Mod is installed and working. Now I'm just terrified of putting my custom content from EA back in the game, since that is apparently what was causing my game to fail at life. In case anyone is curious, this is my folder setup:
In my The Sims 3 Directory:
Resource.cfg
Mods>Packages>awesome.package
Mods>Packages>rtfm.txt (this is OPTIONAL; it's just the manual, I keep it here so I don't lose track of it. Will not affect your game in any way)
Game>Bin>d3dx9_31.dll
In my The Sims 3 World Adventures Directory:
Resource.cfg
Game>Bin>d3dx9_31.dll
I guess the silver lining to this is that I'm now intimately familiar with my Sims files, so I should never have a problem installing Awesome Mod again :P
Navigation
[0] Message Index
[#] Next page
[*] Previous page