Problems since Island Paradise patch came out
Hello everyone! I want to tell you that during this time, after the game update 1.55, my game has gone very wrong, several problems that are caused by using custom content from this page. I want to clarify, I'm not saying that the content of TSR is corrupt, I think the CC from here are excellent!. Unfortunately I can not use them again, several users of The Sims 3, included me, that bought our copy of Island Paradise could not play anymore because this errors:
- When choosing a household, and click the checkmark icon, it turns gray and does not load the game, therefore, it is impossible to play.
- I can't share creations, OF ANY KIND, get a window saying "FAILED TO SHARE (name of the creation)"
Really damn tired of these two errors, I tried all kinds of solutions, (I will not list them all because it's toooo long, just know that I got terrible headaches), I looked for help on the official forums and I was relieved to know I was not the only one who had these problems, EA is aware of this and they said they are working on these bugs.
So it's not a problem caused by corrupt CC, since before the 1.55 update, my game and of many users ran well. I just hope a solution, as it is sad not to be able to use CC in the game or in building houses as I do.
Sometimes I think that EA creates many updates to make incompatible to all content that is not from their store, The official EA support clarifies that "the use of unofficial custom content can lead to problems". So in my case I can not do anything else, just to play with the basic content of The Sims 3 and its expansions, plus the contents of the store.
I do not know if anyone here has the same problem as me, I "envy" those who do not have problems playing with CC, since these problems do not affect everyone, so my next creation will have only store content and base game and expansion stuff, it is sad, very sad, I was so happy with my content and houses from the amazing artists from TSR and now I can not use anymore!
I hope all this is fixed with the next update, with nothing more to say, I say goodbye.
Alan.