Patch-related issue

[CharlieChomper]

I just thought to warn anyone either with the patch or considering installing it (such as anyone with Generations) that it "breaks" photography-related interactions (ie actually taking photos).

The irony was that when the patch was originally "leaked" prior to Generations' release, the problem was discovered and EA supposedly had pulled the patch to resolve it.

Instead, it appears they haven't. I just had a sim whose lot suffered a major fire (a meteor landed on her lot and caused it) and tried to get her to take a photo of it only for her to get "frozen". I had to resort to using the reset cheat to get her back. However, the first photo she took I had no problems--it was the second time I tried it that caused it.

For those of you do have the patch installed, the workaround reset cheat is "resetSim <first name> <last name>".

Here's hoping it doesn't take until the next stuff pack for them to resolve this...

On a semi-related note, does anyone know if the old issue of dig sites becoming inaccessible has finally been resolved or not? It was introduced with Ambitions and I still remember it being a problem through Late Night, but am not sure about now.

[Felicity]

Thanks for the info CC! The only patch update I have seen is the one for players on Mac. Is that the one you are referring to?

I had to uninstall my complete Sims3 and re-install again. It automatically updated when I installed Generations. So far have had a wonderful time playing.

Felicity

[Jessica]

Thanks for the heads-up, CC. The game does seem full of glitches since the Generations' patch.

No idea about the digging sites though, sorry. I seem to recall a mod to fix that, maybe at MTS?

[Theachen7]

Thanks for the heads up! I wondered why Donna was unable to take photographs, which is a shame for her as she's a photographer. Lucky for her she's got savings

[CharlieChomper]

Felicity, this issue actually ties into all platforms--not just Macs. I play on a PC with Windows installed, but have since read some Mac users who were able to get the patch working for them are experiencing the same problem.

The Mac issue is separate and seems somehow tied into the fact that the patch was released in increments (although, no confirmation on that yet as I believe they're still supposedly looking into the issue).