Difference between revisions of "Game Help Talk:Patch Table"

Revision as of 21:01, 8 January 2013 (view source) EllaCharm3d (Talk | contribs) (→‎Workarounds for CAW with version mismatch issues) ← Older edit		Revision as of 06:38, 9 January 2013 (view source) EllaCharm3d (Talk | contribs) (→‎Workarounds for CAW with version mismatch issues) Newer edit →
Line 1:		Line 1:
	==Workarounds for CAW with version mismatch issues ==		==Workarounds for CAW with version mismatch issues ==
−	[[File:Caw version mismatch error.png|right|350px]]Since the TS3W.exe file was introduced, Create-A-World can only load if you have the matching Pack released for that level. ie	+	[[File:Caw version mismatch error.png|right|350px]]Since the TS3W.exe file was introduced, Create-A-World just need the associated base game to be on the same level. That means, CAW and BG versions need to be on the same row, if you refer to the patch table page.
−	* if you have Generations with patch 1.22 (game code ''level 011'' equivalent to ''CompatVersion = 11'') and CAW ver 1.11.10	+
−	* if you have Town Life with patch 1.24 (game code ''level 012'' equivalent to ''CompatVersion = 12'') and CAW ver 1.11.12	+
−	* if you have Pets with patch 1.26 (game code ''level 013'' equivalent to ''CompatVersion = 13'') and CAW ver 1.13.3	+
−	* and so on and so forth...see [[Game Help:Patch_Table]]	+
−	CAW just need the associated base game to be on the same level. That means, CAW and BG versions need to be on the same row, if you refer to the patch table page.
−		+	The workaround, originally found by Kiritra and now maintained by our members in [http://my.modthesims.info/showthread.php?t=457349 CAW and Sims 3 Version Mismatch Work-Around] is to
−		+
−	The workaround, found by Kiritra in [http://my.modthesims.info/showthread.php?t=450303 CAW Version mismatch rebooted, rewritten and solved] and it's replacement [http://my.modthesims.info/showthread.php?t=457349 CAW and Sims 3 Version Mismatch Work-Around] is to	+
	# edit the CAW gameversion to be on the same game code "''level''"		# edit the CAW gameversion to be on the same game code "''level''"
	# copy these 2 lines found in the CAW tool Default.ini file into the last pack's Default.ini file		# copy these 2 lines found in the CAW tool Default.ini file into the last pack's Default.ini file
Line 18:		Line 11:
	# rollback (ie uninstall and reinstall) to use the CAW version and base game version to match the last pack as in that table		# rollback (ie uninstall and reinstall) to use the CAW version and base game version to match the last pack as in that table
	# only patch up to that level		# only patch up to that level
		+	<pre width=60%>
	[Version]		[Version]
	...		...
	CompatVersion = 12		CompatVersion = 12
−	WorldBuilderCompatibilityVersion = 9	+	WorldBuilderCompatibilityVersion = 9</pre>

---

Revision as of 06:38, 9 January 2013

Contents 1 Workarounds for CAW with version mismatch issues 1.1 Step-by-step 2 It didn't work! Help! 3 1.34 updates

Workarounds for CAW with version mismatch issues

Since the TS3W.exe file was introduced, Create-A-World just need the associated base game to be on the same level. That means, CAW and BG versions need to be on the same row, if you refer to the patch table page.

The workaround, originally found by Kiritra and now maintained by our members in CAW and Sims 3 Version Mismatch Work-Around is to

1. edit the CAW gameversion to be on the same game code "level"
2. copy these 2 lines found in the CAW tool Default.ini file into the last pack's Default.ini file
   • or, if patch is newer (ie level number is higher) than CAW's CompatVersion, copy FROM base game TO CAW as shown in the step-by-step section below.
3. see table at the end of post#1 CAW and Sims 3 Version Mismatch Work-Around and find the last pack you own
4. rollback (ie uninstall and reinstall) to use the CAW version and base game version to match the last pack as in that table
5. only patch up to that level

 [Version]
 ...
 CompatVersion = 12
 WorldBuilderCompatibilityVersion = 9

Step-by-step

The FROM and TO would most likely change depending on what is older - CAW or the base game level. In the below scenario, my base game is patched to a higher level (level 014) than CAW (level 013), so I copy FROM base game TO CAW.

• Go to your base game's \Game\Bin path (Red box, on the right)

\Program Files (x86)\Electronic Arts\The Sims 3\Game\Bin\

• Open this file in Notepad, leave it and Alt+Tab back to Windows Explorer
• Then, go to CAW's path (Red box, on the left)

\Program Files (x86)\Electronic Arts\The Sims 3 Create a World Tool\

• Make a copy of this Default.ini file and back it up just in case
• And open this Default.ini in Notepad, as well.
• Copy the 2 lines indicated above from base game's Default.ini. Note the values would change as more patches are released in future.
• Paste it to replace the lines in the Default.ini from your base game's path to the CAW path (Blue boxed).
• Edit the GameVersion of CAW FROM 1.13.3.013037 TO 1.13.3.014037 (Pink boxed), so the game codes are on the same level.
• Finally, the left side is how the CAW Default.ini should now look after the above edits are done (click on image to view in higher resolution).

It didn't work! Help!

If the above steps don't work for you or you have questions, please post in the Q&A thread : CAW and Sims 3 Version Mismatch Work-Around

1.34 updates

Jun Installer file:

GameVersion = 1.16.2.016037
CompatVersion = 16
WorldBuilderCompatibilityVersion = 13

Mar Installer file:

GameVersion = 1.16.2.015037
CompatVersion = 15
WorldBuilderCompatibilityVersion = 12

Even though the CAW version is the same, the installer is of different sizes (see image) and the contents of the Default.ini differs for the lines shown above. So, it appears that one would still need to redownload. I did not test if the older version works without being uninstalled as my system was recently reformatted and I don't think I'd be reverting things just to confirm this theory. If anyone has information to share, please do.

~ ellaCharm3d 07:29, 5 June 2012 (EDT)

I can confirm that the older version works okay, as long as the Default.ini is changed to reflect version 13. Simsample 09:16, 3 July 2012 (EDT)