More Awesome Than You!

DELETEACCOUNT

Hybrid; Reloaded patched to Razor with Witch's Bin with both Official patched.
Frankengame.

The legal version, although the first time I installed it the game wouldn't run due to some registry issue which made my computer think it was a pirated copy.

I'm inclined to suspect all the patch issues are based purely on incompetence, because I have never had any problems that I didn't cause in some way.

I completely agree. I have not experienced ANY problems except for the stupid NPCs standing around doing nothing on community lots. Stupid lying patch notes...I risked my working game just for that one glitch and it didn't make a difference. At least my game works. People shouldn't blame the patch(es) or EA for their problems. It's possibly their computer or conflicting mods and stuff.

Legal, no problems besides my own stupidity.

Same here.
Didn't have any issues patching, and the game itself (so far as I can tell right now) is showing no signs of any problems.. (Well, nothing I didn't cause myself anyway.)

I own a legal copy of the game, and had no problems installing the patch, and have had no problems using the latest version of Awesomemod. Before patching, I'd made sure to replace altered files with the originals from my backup drive. Everything ran smoothly.

Most of 'em, yup. I'm just ticked that EAxis required us to have the dumb library families, still. That's the only issue I had. I have the Razor version.

Same here
Problems: caused by me (by deleting several MBs of foreign language shit) but initially caused by EAs anal retentive ways to crc check unnecessary files.

Legal. Able to get it going after removing old script files. It was my fault.

Legal. I had Razor when I patched the first one, but once I found instructions to do it properly, I had no problems.

Wow, I assumed that more people here had a downloaded version.

I have the legal version, and as soon as I remembered that I replaced the camera ini it was fine.

Legal copy here, too.  Once I restored my modified *.*ini's, all of my woes vanished.  It works well with all of my mods, including core.

Legal here.  Patch and latest version of AM with ISM worked fine after replacing the families.

Considering there's A LOT of people on the Exchange forums bitching about it and you need to have a legal valid key to post there I think that pretty much shoots your theory down. Nice try though. :P

Legal copy. I fiddled with the game afterward until it stopped spazzing out, when I realized I had not purged the cache files. Took out AwesomeMod, deleted caches, reinstalled the updated AwesomeMod.  When I opened a game it all worked fine, if a little choppier than originally, but as I played it seemed to level out.

The patcher will just error on anything that's missing or altered, it doesn't matter if it actually changes that file or not it simply halts on anything that it construes as "abnormal." Mine halted on "VideoCamera.ini" for example.. I was using Aikea's camera tweak and it freaked out over the file being different. (Which is ridiculous of course, both because it is nothing more than a simple INI file that's designed to be tweaked anyway.. and also because the patch never updated this file or touched it in any way.)

So yea, I agree, it's dumb.

compare md5
patch data

More than likely there are no complete files in the patch, but just what needs to change between the files. So if the file is different, patching to destroy quite a bit.

<-- Captain Obvious

In my case, I changed the "Shaders_Win32.precomp" in ...Sims3/Game/Bin. (because I want them NAKED!)

The Patch did not work.

While I left the original as "oShaders_Win32.precomp" in the same folder instead of replacing it for real, it was easy to get back:

I turned the name of the modified file in "xShaders_Win32.precomp" and renamed the original to its original name.

Then the patch3 did work.

Especially when juggeling with cracked and original .exes in Sims2 I got used to keep the original files in their places, but renamed them.

The cracked .exe are always renamed by me to something like "crackedExeOfGame" to keep the original one for patching. You can start by that .exe the same way...

I have a legal version of the game.. and all problems I encountered installing the patch were my own fault for not remembering file changes. 

Hybrid, all patches worked ok. I did fiddle around for the first patch, but haven't had any problems for the second one.

Pirated from a Legal copy  :D, I just screwed the gameplay.package, but after I recovered the original one it went all fine

My two hitches were the library families and the video ini file. Then I booted with CD as per JM's instructions. Now running awesomemod alpha no problems. Legal copy.

Legal copy on one of my Pc's and a hybrid on the other one I use.  Any problems I had were fine once I replaced the tampered files such as shaders and silly default families in the bin.

Razor, installed both patches and many mods, no problems at all.

I have a legal version. I had to put in a copy of Rick's scripterror to get the patched game to load. (I have a Vista x64.)

RLD, running smoothly now. Only problem was with the families, replaced them, the patch installed without error. Then I had the not aging problem and the route failures with the first compatible AM - Pescado admitted the not aging was AM's fault and corrected it - but with the newest AM the route failures went away, too.

Oh, and I had a brief problem with AM not working at all and game asking for CD, but I somehow managed to put another core mod in override... ::)

I'm inclined to agree with him that most all the errors are user created. 

I had to do the unthinkable and download the EA manager to get the patch to install on a nice fresh clean install of the game , otherwise it was bullshit.

Legal and the only problems I had were my own Brain Cheese getting the better of me. I had forgotten I had a camera hack in. Once I had the new version of awesome mod things went swimmingly

Legal: didn't have any problems installing the patch but did think something had gone wrong when I fired up the game having forgotten to remove the old copy of Awesome mod but it took .00001 seconds to realise and 2 seconds to fix.

Razor. I had problems after the patch and it absolutely was not due to incompetence. I solved it because of competence. It was the game that screwed itself up.

Legally bought.  Booted fine after I removed the old incompatible mods.  Did not run well with the ISM/Awesome hybrid, and no wonder, because ISM wasn't updated yet.  Got two small errors* running just the AwesomeMod, and surprise surprise, they're still there in the unmodded story mode with AwesomeMod removed.  I'm lucky that the patch only broke two such minor things as far as I can tell.


*Sims that were seated upon saving, are standing and interpenetrating the seat they were in upon reloading, but escape just fine when told to move; and the little Opportunity notification tune sounds weird.  I am sure that others have found and reported these errors already, and have yet to look for any solutions, since I have bigger fish to fry at the moment.

I originally had reloaded, but when I tried to patch up to 1.27 (or whatever it was called), it failed, no matter what I did, so I backed up my saves and CC and uninstalled it, replacing it with the Razor final version. From that I had no problem patching, but then again, the only mod I have in my game is Awesomemod, along with a little CC.

jwaas, the Awesome-compatible Indie Stone mod shouldn't have been affected by the patch, because it's not a core mod. It was probably just the usual voodoo that caused your game to run better after taking it out.

Legal now (because before 1.2.7, I figured any potential patches might cause a BFBVFS situation with Reloaded, so I caved in and bought it).  I initially had problems because of my own stupidity, yes; I'd forgotten about a few altered ini files, but after replacing with the original files, I still had to uninstall and reinstall because the bastard kept hanging on the Launcher for whatever reason.  No big deal; I hadn't had to uninstall and reinstall a game because of corruption since the days of TS1, so it was just minor aggravation.  I've yet to see any of the freakish problems that people are reporting after patching.  Everything runs as smoothly as a baby's bottom.

Razor.   Had no problems... I was lucky since I had previously replaced my changed files to the originals when tuning mods came out to get rid of the blur and awesomemod got rid of the cd check.

Razor. I had deleted the EA library sims, and had to return them to the library before the patch installed. Immediately after patching, I had to reset a batch of sims that were stuck in some kind of work/home limbo.  After that, no problems, *no issues, no pathing problems, no lag, no invisible sims, no obvious changes, other than the fact that random sims now visit the sims I'm playing.  I didn't necessarily want this, but whatever.

*Well, I wasn't having any issues, until tonight when I ran CCleaner, finally got around to letting some Vista updates install after putting it off for months, and upgraded my video drivers, which I had purposely not been updating because the older drivers worked better with TS2. I didn't add or delete anything from the game itself.  NOW I have what Pescado referred to as the "Old Car Syndrome" crash, after not having had that problem in weeks. The peculiarities of this game amaze me. 

It's amazing what a little competence will do. It doesn't necessarily take incompetence to cause a problem but it almost always takes competence to solve it.

I finally applied the patch tonight.  It worked fine.  I'm using the retail box version (arred), and the patch version that goes directly from base to 1.3 without the intermediate 1.2.7.

Legal bought from legal shop. Installed on a computer without internet connection and I have to wait for downloadable versions from another computer. Never had problems.
All my claims are on the game self.

Razor with booty!!. Problems not with patching, but with playing the patched version.

Legal Copy here!!
Patch installed without any problems.  I did have one problem with the game hanging after the intro movie...but deleting all the cache files and (ironically) installing the updated enablescripterror.package solved it (Voodoo Debugging FTW)!  :D

I'd been dreading patching my game, but this thread gave me the courage to finally give it a try this morning.  My razor copy patched just fine and is playing okay so far.  Even have a resurgence of wants on a couple of sims.  (Just running awesomemod/indi combo with a few CC items.)

Legal. Haven't encountered any problems yet.

I have a legal version of SIMs 3 on two different computers. My original that my husband built played the game fine with all the patches and all of my CC. It lagged a little with settings on high when I played for many hours, not a big deal.

My husband built me a new system that looks like a tower full of fans. He built it with gaming in mind for me for my SIMs game. I have had a lot of problems getting it set up. It kept crashing and I went back to my old system while he worked on the new one again. Last week I installed it on the new system again. It worked fine with the first patch, but when I tried to add the second patch the game crashed before it would even load. I tried everything to remedy it but nothing worked. I did a reinstall - it would load until I tried to add the framework, then I got a red city. Again I tried everything other than throwing the kitchen sink at it - nothing worked and I reinstalled the game over and over yesterday (spent my entire day). I found out that my problems started with the framework, so I manually added the necessary files. The download Monkey works with my setup, so that's no problem. I loved the Awesome mod, it works wonderful on my other computer but it does nothing, and changes nothing on my new system. I wanted to try that IndieStone I have been reading about, but same thing. It's like my computer just ignores that it is there. The files were put in the right place. I'm too tired to see if the second patch will work, and I have no intention of messing with it as of now. I would like to actually play my game. I have had to start my legacy family over for the 3rd time now. I have had to reinstall it every time she finally was able to buy a toilet, a bed and a tub.

I don't understand it, because this system was built to play the Sims.  My old system met the requirements but my processor and graphics card are not nearly as good as my new one is suppose to be.

It's my wanting certain CC in my game that has caused my problems, not the patches themselves. My problems were done by me.

Legal copy - no core mods, several non core mods.  Never replaced any of the original game files, just .package files in my Mods folder.

Left my mods folder where it was- patch installed just fine.  

Only issue to report is now my music is hit or miss.  Before the patch, music would play in buy/build mode and the stero would play music.  Now its random.  One game load I had no music from the stereos or buy/build, I exited and reentered the game and this time I can hear the stero music but still no buy/build music.    

Hybrid.  Played the game for two weeks pre-release using one of the pirated versions, then replaced it with the legal version once it was released and I was assured SecuROM wouldn't get its sticky fingers in my hard drive.

I had two issues with patching, both were due to my own actions.
- The patch stalled on the missing Baker family so I had to unzip the library families.  I'd zipped them up when I removed them, in case they were needed when patching.
- I had to remove an outdated file to fix the "CTD upon attempt to load household" issue.  My fault - I should have removed enablescripterror before attempting to patch, as by the time I got around to patching I already knew it was outdated (and that there is an updated version should I still require the file).

Given the number of people who are reporting no problems or only user-caused problems, I would say that if people are having problems patching or running the game post-patch, then their problems are most likely caused by user error, and not by mods, EA, or the possible use of pirated versions.

Legal - No problems.  I just moved any altered files off to my desktop and replaced them right from the disk.  Patch installed fine and I just plopped everything that would still work back where I wanted it.

Legal, put all modified/removed files back before patching, went nice and smooth and have had no problems whatsoever to date.

I see, I was thinking that maybe the non-core part of Indie Stone also needed updating.  Either way, I still see no problems to date besides the two extremely minor problems I mentioned earlier, and the occasional graphical glitch that occasionally happens anyway.  I have yet to run the patched game completely vanilla and see how that works.

I forgot to mention that the best bug that I got when running Awesome and IS together was when my family's 6 met himself at school.  Apparently something interpreted "Make genetic offspring from bin Sims and sometimes use them to populate the hood" as "Take the exact Sims in the bin and plop them in the hood as often as possible, multiple times, including copies of the playable Sims."

Not wanting my computer to turn into the fabled BFBVFS, I deleted that hood in a hurry and started over with Awesome alone, then with the unmodded story mode.

Finally, I had to respond to your post because it's the first time in months, maybe years, that I've seen both affected and it's spelled and used correctly in the same sentence on an internet forum.  I guess the high standards kept here, and the P&L engaged in when said standards aren't met, really do make a difference for the better.  :)

I removed the ISM for the same reason you did. My 'hood wound up with multiples of the bin families that were exact clones of each other, both in houses and in the homeless bin. My game lagged like ass. Something had to go, so I deleted the clones and uninstalled ISM. Problem solved!

[/off-topic tangent]