Install 1.3 update or not?
Zaphod Beeblebrox:
One should ALWAYS take the "wait and see" approach with EAxis' crappy patches. You never know what they'll break next. People should have learned their lesson after the first patch further fucked up the already fucked up Launcher and caused many CTDs.
And having patience while waiting on mods to be updated (thus, not installing the patch until then) is a given.
fiberglassdolphin:
Since awesomemod is not yet updated for 1.3, I'm kind of glad that the updater failed me multiple times. But, for when I do want to install the patch, is there anything confirmed to get it to work? I took out my mods folder, restored my ini files to their backed up versions, and I never deleted the premade families. I figured my problem was my horrible, slow connection these past few days corrupting the update files.
Quote from: Zaphod Beeblebrox on 2009 July 29, 05:05:52
Oddly enough, over on Facebook (because I haven't ventured over to 3Tardland today), I noticed quite a number of people kermitflailing over the patch and how they can no longer play with mods in the game.
It's just their core mods, right? Maxoids and pigheaded EAdiots seem less than enthusiastic about custom content that isn't just recolored CAST crap, so I wouldn't be surprised if they "fixed" our ability to add real CC. I imagine the reason would be that they want this series to die a quick, humiliating death.
Shaprepenr:
I'm able to run both Awesomemod and Indiestone perfectly with the new patch. But I had to do some stuff before I got it to work. You should try these for safe measure:
1. Temporarily move the whole mods package to your desktop.
2. Delete all the *cache.package files from the Sims 3 folder found in your documents folder.
3.Run the game without any of the mods.
4. Start a new game (chose any neighborhood, I chose Sunset Valley).
5. Once the new game has loaded, go ahead and quit out of the game. You don't need to save. We just needed to rebuild the cache.
6. Navigate to your mods folder and delete the enablescripterror.package if you have it.
7. Place the mods folder back to the Sims 3 directory.
8. Run the game.
Before I did all of that my game would crash to the desktop but now I am able to run both Awesomemod and Indiestone together without any problems. Indiestone still run Story Progression (I'm still getting notifications of my horny neighbors having their 5th baby). All other custom content still works and all the features of Awesomdmod still work (like robotic hand of god)
Now. I'm not guaranteeing that this will work for you but I am sharing my experiences and I'm hoping it works as a temporary solution 'till Awesomemod and Indiestone get updated to work with 1.3.
Have fun! :)
J. M. Pescado:
AwesomeMod is now ready for public field trials in 1.3.24. IndieStone Driver will not need to be updated intrinsically for the patch because it is not Core, but if you are running pure IndieStone, they need to update their core. Of course, this is someone else's problem.
Anshin:
Quote from: J. M. Pescado on 2009 July 29, 10:20:00
AwesomeMod is now ready for public field trials in 1.3.24. IndieStone Driver will not need to be updated intrinsically for the patch because it is not Core, but if you are running pure IndieStone, they need to update their core. Of course, this is someone else's problem.
I've tried the new AwesomeMod for 1.3.24 and all the route failures are fixed.
Thank you!
Navigation
[0] Message Index
[#] Next page
[*] Previous page