FOREIGN TRANSLATIONS





Why is my Patch-Level so Important ?


Patch-Levels dictate the state of the Core scripting modules being used by your game. Scripting mods, such as the ones provided in this suite, rely on the Core being at a certain level in order to operate properly.

If the Patch-Level is incorrect, a scripting mod can produce bizarre and unexpected results, or simply crash your game outright.

EA updates everyone, regardless of which Expansion Packs they have installed, to the highest level Patch-Level whenever they release a new Patch
  • So provided you keep up-to-date, you can always use the newest available version of a mod.

The Patch Level shown for the Expansion Packs is completely irrelevant, and can be ignored.
  • Only the Patch Level of the Base-Game matters.

To determine your base-game Patch-Level, open the Game Launcher and hover your mouse over the base-game icon in the lower left corner.
Anchor: [[Patch Level Compatibility#PatchLevel|Check Patch Level]]
BaseGameVersion.JPG

MAC NOTE:



Okay, so say I am not actually up-to-date on my EA Patch ?

anchor : [[Patch Level Compatibility#Current]]

Whenever a EA Patch breaks one of the suite's mods, a new Phase is released to provide compatibility. If you are lucky, the earlier Phase of the mod will still be hosted somewhere, allowing you to download and install it.

Unfortunately, earlier versions are not permanently hosted by myself, and tend to vanish whenever the hosting site is changed, or when space is required for newer versions. It is advised that you do not rely on the continued hosting of compatible obsolete mods.

If an older Phase is being hosted here, it will be listed on the mod page, available via the links on the left-hand menu.



Where do I find the latest Patch ?

anchor: [[Patch Level Compatibility#Where]]

Usually your Game Launcher will keep you up to date regarding patch, provided you allow it access to the internet, and everything is working properly.

However if you want to download the Patch manually, it is available on the Official Forums here : http://forum.thesims3.com/jforum/posts/list/175477.page

The Super Patcher and You


A lot of problems in the game seem to be related to the game not being patched correctly.
  • The patches you install using the launcher may sometimes glitch, this may not always be reported with an error.
  • Sometimes you may have a problem where a patch even just refuses to install.

For difficult situations EA has a solution in the form of the Super Patch, which basically is a roll-up of ALL the patches you may need.
  • This is a standalone program, in other words, you can download and just run it, and it will indiscriminately patch any game file.
  • It works for any patch level you have, any language, and any distribution (except for Steam -- needs checking!!).
  • The downside of that is that it requires you to download a file over 1GB in size.

It may be that the Super Patch tells you your game is already up-to-date, in that case it offers you a choice to "Patch Anyway".
  • Selecting that choice is highly recommended, it bypasses the cursory checks and makes sure every file indeed IS up to date after running.

For PC, the latest Super Patch can be found on this page in EA help:

For Mac, the latest Super Patch can be found on this page in EA help:

For older patches your best bet is to look here:




How do I update my mods when I Patch ?

anchor: [[Patch Level Compatibility#HowToUpdate]]

Whenever you update the game, you run the risk of one of the mods you have installed being broken by an EA change.
  • It is not EA's prerogative to maintain backwards compatibility with third-party mods, so it is very possible for a new EA Patch to render a mod unusable

The steps:
  1. Remove any changes made to files in the installation folders
    • For most users, this is a non-issue, since most mods do not alter files in the install directory.
  2. Install the EA Patch
    • You do not need to remove your mods prior to patching
    • Nor do you need to reset your save-game to stop running interactions. Doing so was only necessary to workaround an old EA bug, that has since been corrected.
  3. Now go through your mods folder and move all your mods to a different location.
    • Many users suggest moving them to your desktop for simplicity
  4. Verify each mod for compatibility with your new Patch Level
    • If you have knowledge in modding, you can verify compatibility for tuning mods pretty easily.
    • If you are unfamiliar with modding, or have scripting mods installed, you must return to the creator of that mod and wait for them to verify compatibility.
  5. DO NOT..reinstall a mod that has not been verified as compatible by its creator
    • Incompatible scripting mods will crash your game, or produce incredibly nasty side-effects
    • Incompatible tuning mods may appear to work properly, but can bounce the game in bizarre ways, rendering the game unplayable
  6. Once all mods have been verified or replaced with new copies, you can start your game
    • Note you can remove scripting mods that have not been updated, and run the game without them installed.
      • However, you will lose any in-game settings for that mod.
      • This is only an issue with pre-existing saves, so if you do not open any of those saves while the mod is uninstalled you will not encounter the issue.
      • Most users will simply start a brand new game and play that game while they wait, and then return to the older game once all the mods are available.



What are the various Patch Levels ?

anchor: [[Patch Level Compatibility#Packs]]

Expansion and Stuff pack Patch Levels have an equivalent base-game Patch to which they are compatible

The release of each Pack has a corresponding Patch-Level:
  • EP1 : World Adventures Patch 2.0 is equivalent to base-game Patch 1.5
    • Released: Nov 17, 2009
  • SP1 : High End Loft Patch 3.0 is equivalent to base-game Patch 1.9
    • Released: February 2, 2010
  • EP2 : Ambitions Patch 4.0 is equivalent to base-game Patch 1.12
    • Released: June 1, 2010
  • SP2 : Fast Lane Patch 5.0 is equivalent to base-game Patch 1.15
    • Released: September 7, 2010
  • EP3 : Late Night Patch 6.0 is equivalent to base-game Patch 1.17
    • Released: Oct 26, 2010
  • SP3 : Outdoor Living Patch 7.0 is equivalent to base-game Patch 1.19
    • Released: February 1, 2011
  • EP4 : Generations Patch 8.0 is equivalent to base-game Patch 1.22
    • Released: May 31, 2011
  • SP4 : Town Life Patch 9.0 is equivalent to base-game Patch 1.23
    • Released: July 26, 2011
  • EP5 : Pets Patch 10.0 is equivalent to base-game Patch 1.25
    • Released: Oct 18, 2011
  • SP5 : Master Suite Patch 11.0 is equivalent to base-game Patch 1.28
    • Released: January 24, 2012
  • EP6 : Showtime Patch 12.0 is equivalent to base-game Patch 1.31
    • Released: March 6, 2012
  • SP6 : Katy Perry Patch 13.0 is equivalent to base-game Patch 1.34
    • Release: June 8, 2012
  • SP7 : Diesel Patch 14.0 is equivalent to base-game Patch 1.36
    • Released: July 10, 2012
  • EP7 : Supernatural Patch 15.0 is equivalent to base-game Patch 1.37
    • Released : September 4, 2012
  • EP8 : Seasons Patch 16.0 is equivalent to base-game Patch 1.41
    • Released : October 29, 2012 (Patch release)
  • SP8 : Decades Patch 17.0 is equivalent to base-game Patch 1.47
    • Released: January 22, 2013
  • EP9 : University Patch 18.0 is equivalent to base-game Patch 1.49
    • Released: February 19, 2013 (Patch release)
  • EP10 : Island Paradise Patch 19.0 is equivalent to base-game Patch 1.55
    • Released: June 18, 2013 (Patch release)
  • SP9 : Movie Patch 20.0 is equivalent to base-game Patch 1.57
    • Released: September 4, 2013 (Patch release)
  • EP11 : Into The Future Patch 21.0 is equivalent to base-game Patch 1.62
    • Released: October 17, 2013 (Patch release)
  • Patches After EP11




There is no Phase for my Current Patch-Level, what do I do ?

anchor: [[Patch Level Compatibility#Missing]]

Obsolete Phases list their most recent compatible Patch Level.

For many mods, it is possible to run them on an earlier Patch:

(The following does NOT apply to ErrorTrap or UntranslatedKey, which are Core, and only compatible with a single Patch Level)
  • Mods listed as Patch 1.4 *may* work on Patch 1.0 to 1.4
  • Mods listed as Patch 1.11 *may* work on Patch 1.5 to 1.11
  • Mods listed as Patch 1.16 *may* work on Patch 1.12 to 1.16
  • Mods listed as Patch 1.17 *may* work on Patch 1.17 to 1.19
  • Mods listed as Patch 1.24 *may* work on Patch 1.20 to 1.24
  • Mods listed as Patch 1.29 *may* work on Patch 1.25 to 1.29
  • Mods listed as Patch 1.36 *may* work on Patch 1.31 to 1.36
  • Mods listed as Patch 1.39 *may* work on Patch 1.37 to 1.39



Build Versions

anchor: [[Patch Level Compatibility#Build Version|Core Mod Build Version]]

The <BuildVersion> mentioned in script error and Crash-To-Desktop logs specifies the version used by the EA Core files for the Patch-Level you are running.
  • This is important when reading other user's logs, as it provdes a means to determine which Patch-Level they are running, and whether the mods they have installed are compatible.
  • It is also useful to the developer, as it defines which version to set any Core-mods that are created.
    • Both ErrorTrap and UntranslatedKey need to have their versions updated to stop a warning message from appearing when the game starts.
    • This is the reason why there are two versions of ErrorTrap, as the <BuildVersion> between the Steam and Origin versions are different, even though the code itself is the same.
  • To determine the BuildVersion you are running, do the following:
    1. Install DebugEnabler
    2. Load the game
    3. Click on the active sim, and navigate the menu : "NRaas \ Debug Enabler \ Options: Sim \ Object \ Force Error"
    4. Unpause the game and wait 10 sim-minutes
    5. A script log will be created in your "My Documents" folder containing the <BuildVersion> value

Patch 1.69

  • Origin: 0.0.0.0 (don't ask)
  • Origin v2: 0.2.0.31
  • Origin v3: 0.2.0.32

Patch 1.67

  • Origin: 0.2.0.209
  • Steam: 0.0.0.32

Patch 1.66

  • Origin: 0.2.0.207
  • Steam: 0.0.0.31

Patch 1.63

  • Origin: 0.2.0.205
  • Steam: 0.0.0.30

Patch 1.62

  • Origin: 0.2.0.199
  • Steam: None
  • Note: Should not be used, patch up to 1.63 or higher

Patch 1.57

  • Origin: 0.2.0.196
  • Steam: 0.0.0.23

Patch 1.55

  • Origin: 0.2.0.210
  • Steam: 0.0.0.19

Patch 1.50

  • Origin: 0.2.0.188
  • Steam: 0.0.0.22

Patch 1.48

  • Origin: 0.2.0.195
  • Steam: 0.0.0.17

Patch 1.42

  • Origin: 0.2.0.190
  • Steam: 0.0.0.16

Patch 1.39

  • Origin: 0.2.0.169
  • Steam: 0.0.0.19

Patch 1.38

  • Origin: 0.2.0.165
  • Steam: 0.0.0.17

Patch 1.36

  • Origin: 0.2.0.177
  • Steam: 0.0.0.15

Patch 1.34

  • Origin: 0.2.0.173
  • Steam: 0.0.0.14

Patch 1.33

  • Origin: 0.1.0.34
  • Steam: 0.0.0.20

Patch 1.32

  • Origin: 0.1.0.33
  • Steam : 0.0.0.18

Patch 1.31

  • Origin: 0.1.0.27
  • Steam : 0.0.0.15

Patch 1.29

  • Origin : 0.1.0.1266
  • Steam : 0.0.0.12

Patch 1.26

  • Origin : 0.2.0.164
  • Steam : 0.0.0.11



Foreign Translation





How do I Install Something ?


This very first step is covered here : How To Install If you have never managed to get a script mod to work on your setup, you should read through that page before continuing onward.



You get a message "It looks like you have installed an incompatible game modification"

anchor: [[Common Install Issues#Unofficial]]

This is one message to take seriously.
  • It means something in the structure of your game is not correct, and playing with it, especially when you save after playing, can corrupt your game. This may or may not be reversible.

You can get this message for various reasons, the most important are:

  1. An incompatible core mod. A core mod is a re-write of part of the game, so it is very important that it matches the rest of the game.
    • A core mod is written for a specific patch level, if you have the wrong patch level it does not "fit".
    • Core mods also differ based on whether you have the Steam or Origin version of the game installed.
  2. A mismatch in patch levels for the various EP/SP's you have. This is just as bad as an incompatible core mod.
  3. Remnants of the "old" way of installing mods in your Program Files. While this is getting more rare, if you've been playing The Sims 3 for a long time, it might still be you've at some point installed something this way.

To remedy, take the following steps:

  • First off, rename your Documents\The Sims 3 folder. Then start the game. Because it cannot find this folder now, it will re-create it.
    • The new copy will be "virginal" like you just installed the game, void of any mods or Custom Content.
    • If the message "unofficial game modification" now disappears, you can be certain it is due to something in your (old) Documents\The Sims 3 folder, most likely a core mod.
    • Look down further in the section Incompatible Mods.

  • If the message does NOT disappear, the next step is to make sure your game is properly patched.
    • Do not trust the launcher in this case and do not trust your own efforts.
    • You can make sure by downloading the official Super Patcher: http://forum.thesims.ist/175477.page and running it. The Super Patcher is less finicky than the launcher and will update everything as needed.

  • If you have done both and you still get the unofficial game modification message, basically the only thing left is that you must have something still installed in the "old way". Carefully follow the instructions at http://www.modthesim._Way_to_New_Way.

It is vitally important that you remedy the unofficial game modification message.
  • This message means your game is busted.
  • It means the saves you did while playing with this message may be corrupted.
  • Even if it looks like the game will play, sooner or later you will run into trouble.



Incompatible Mods

anchor: [[Common Install Issues#Incompatible]]

When you see odd things happening in the game, like for example excess meteors, stuck Sims, dropping social interactions, unselectable Sims, or just about anything that clearly does not belong, remember that all these can happen due to a single innocuous mod that is not updated.

Not every single mod needs to be updated, there are a couple mods around that work in such a way that they sort of dance around the game and never really interfere with it.
  • These mods may be years old, and still work correctly. However, you cannot easily tell whether a mod falls into this category.

The easiest way again is to rename your Documents\The Sims 3 folder and start a new game.
  • This will ensure you start the game with no mods or CC.
  • If you have a good idea what exactly goes wrong in your game, that helps, because you can then easily check in a test game whether that situation still exists.
  • It is important that you verify your problem does not appear in that test game.

If even this action does not remedy the problem, there is still a chance you may have some mods installed in the "old" way.

Once you have a game that runs correctly, you can start copying over mods from your renamed The Sims 3 folder to your fresh new folder.
  • Start with the ones you are fairly certain that they are good, and run your test game again to make sure the problem does not re-appear.
  • You can work in "chunks", you don't really have to do it one by one, the whole point is to find out which mod is causing you trouble.
  • If your last "chunk" of copied mods causes the trouble, delete it again, and instead copy the mods of that chunk one by one.

Another strategy is to just note which one you use, and re-download them from the sites where you got them, taking note of any remarks made by their creators about the status of that mod.
  • This way you re-build your mod structure and at the same time you make sure you get the latest versions of each.

Do leave the most dubious mods for the last, and check them out one by one.
  • Remember that there are mods that don't have to be updated to work, but you have to test to be certain they work.

While this all may be a tedious bit of work, remember we're dealing with computers here. Computers don't work "sort of right". They will work if everything is EXACTLY right and they will not work if it isn't.



Can Bad Custom Content, such as Hair and Furniture cause the serious non-cosmetic issues with the game ?

anchor: [[Common Install Issues#BadCC]]

The simple answer is yes.
  • There have been numerous reports of improper/corrupt hair causing the game to load improperly.

If the game bounces during the initial start-up sequence, due to an error with corrupt custom content, it may fail to load important resources, such as default tuning, or other game resources.
  • When this happens the in-game results can be unpredictable and completely undefined (ie: random)

Do not discount your non-mod related custom content when searching for the reason for a game-break.
  • You should start with your mods of course, since they are the most likely suspect
  • However if after removing all mods, the issue persists, you should consider testing your other custom content



Clean Folder Method

anchor: [[Clean Folder]]

You may encounter any variety of problems in your game. This may be due to any type of causes, and it can be quite difficult to figure out the correct remedy.

One often used advice is to try in a "new Sims 3 folder". What that means is this:

On starting, the game will look for its folder in your Documents\The Sims 3. If it cannot find it there, it will proceed to make a brand new one, and that is a "factory default" one. It contains:
  • No CC
  • No Mods
  • No Installed EA content
  • No set options

To make the game do that, is as easy as renaming your current The Sims 3 folder, or dragging it somewhere else, like to your desktop. When you start the game, it will create the folder anew.

You can now test if your problem persists under standard EA conditions. If it does, it is due to a problem with your game itself, not necessarily any of your mods or CC.

If the standard EA game works correctly, you can re-do your mod framework in this folder, the best reference and all needed downloads can be found here:
Mod The Sims Game Help: Installing Package Files
  • Re-doing the framework ensures that the problem is not with your framework itself.

After you've installed the framework, it is good to test whether the included NoIntro mod works. If that is OK, you can start to add the mods that you suspect are the problem.