- Site Map >
- Community >
- Sims Discussion >
- Sims 3 >
- Sims 3 Help >
- Patching - Problems Installing Superpatch
- Site Map >
- Community >
- Sims Discussion >
- Sims 3 >
- Sims 3 Help >
- Patching - Problems Installing Superpatch
Replies: 5 (Who?), Viewed: 2785 times.
#1
22nd Jan 2016 at 12:59 AM
Posts: 565
This user has the following games installed:
Sims 3, World Adventures, Ambitions, Late Night, Generations, Pets, Supernatural, Seasons, Island Paradise
Problems Installing Superpatch
All right, so I was fortunate enough to get a gaming computer for TS3. Everything moved over to the new computer just fine, except that I didn't have a hard drive of TS3, and a game code instead. Which meant that, upon loading it into the new computer, it patched at 1.69. So obviously there was no other option but to download the Superpatcher for 1.67. I was feeling particularly pleased to have found a fix, until.."The Setup has checked that no version of The Sims 3 is installed. This update requires a previous version of the application to be installed."
Since there is very much a version of TS3 already installed, I turned to search my problem on google and came up empty handed. So here we are.
System Specs:
(There are two different graphics cards, I wasn't sure if I should include the specs for both of them or not. I did, but call me out if I did something wrong.)
------------------
System Information
------------------
Time of this report: 1/21/2016, 18:46:56
Machine name: LAPTOP-CF899DQ9
Operating System: Windows 10 Home 64-bit (10.0, Build 10240) (10240.th1.160104-1507)
Language: English (Regional Setting: English)
System Manufacturer: LENOVO
System Model: 80NW
BIOS: CDCN25WW
Processor: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8 CPUs), ~2.6GHz
Memory: 8192MB RAM
Available OS Memory: 8052MB RAM
Page File: 5288MB used, 4683MB available
Windows Dir: C:\Windows
DirectX Version: 12
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 120 DPI (125 percent)
DWM DPI Scaling: UnKnown
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Supported
DxDiag Version: 10.00.10240.16384 64bit Unicode
---------------
Display Devices
---------------
Card name: Intel(R) HD Graphics 530
Manufacturer: Intel Corporation
Chip type: Intel(R) HD Graphics Family
DAC type: Internal
Device Type: Full Device
Device Key: Enum\PCI\VEN_8086&DEV_191B&SUBSYS_380217AA&REV_06
Display Memory: 4153 MB
Dedicated Memory: 128 MB
Shared Memory: 4025 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: unknown
Monitor Id: LGD04A7
Native Mode: 1920 x 1080(p) (60.020Hz)
Output Type: Internal
Monitor Name: AOC 2367
Monitor Model: 2367
Monitor Id: AOC2367
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: HDMI
Driver Name: igdumdim64.dll,igd10iumd64.dll,igd10iumd64.dll,igd12umd64.dll,igdumdim32,igd10iumd32,igd10iumd32,igd12umd32
Driver File Version: 10.18.0015.4271 (English)
Driver Version: 10.18.15.4271
DDI Version: 12
Feature Levels: 11.1,11.0,10.1,10.0,9.3,9.2,9.1
Driver Model: WDDM 2.0
Graphics Preemption: Triangle
Compute Preemption: Thread
Miracast: Supported
Hybrid Graphics GPU: Integrated
Power P-states: Not Supported
Driver Attributes: Final Retail
Driver Date/Size: 8/23/2015 13:37:36, 36694808 bytes
Card name: NVIDIA GeForce GTX 960M
Manufacturer: NVIDIA
Chip type: GeForce GTX 960M
DAC type: Integrated RAMDAC
Device Type: Render-Only Device
Device Key: Enum\PCI\VEN_10DE&DEV_139B&SUBSYS_380217AA&REV_A2
Display Memory: 8062 MB
Dedicated Memory: 4036 MB
Shared Memory: 4025 MB
Current Mode: n/a
Driver Name: nvd3dumx,nvwgf2umx,nvwgf2umx,nvwgf2umx,nvd3dum,nvwgf2um,nvwgf2um,nvwgf2um
Driver File Version: 10.18.0013.6143 (English)
Driver Version: 10.18.13.6143
DDI Version: 12
Feature Levels: 11.0,10.1,10.0,9.3,9.2,9.1
Driver Model: WDDM 2.0
Graphics Preemption: DMA
Compute Preemption: DMA
Miracast: Not Supported by Graphics driver
Hybrid Graphics GPU: Discrete
Power P-states: Not Supported
Driver Attributes: Final Retail
Driver Date/Size: 12/16/2015 10:59:13, 17104016 bytes
-------------
Sound Devices
-------------
Description: Speakers (Realtek High Definition Audio)
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0235&SUBSYS_17AA3828&REV_1000
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RTKVHD64.sys
Driver Version: 6.00.0001.7624 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 1/16/2016 12:22:29, 4614896 bytes
------------------------
Disk & DVD/CD-ROM Drives
------------------------
Drive: C:
Free Space: 806.1 GB
Total Space: 905.8 GB
File System: NTFS
Model: WDC WD10SPCX-24HWST1
Advertisement
#2
22nd Jan 2016 at 1:22 AM
If it already patched to 1.69, you are not going to be able to use the superpatcher to patch to 1.67, because it's going to find the 1.69 patch, recognize that this is a higher patch level, and refuse to do anything to it.
The only way to downgrade your patch level is to install from a source that is not already patched to 1.69 (i.e. older discs) and patch that installation. Sorry.
I am Ghost. My husband is sidneydoj. I post, he downloads, and I wanted to keep my post count.
Group for Avatar Makers* Funny Stories *2017 Yearbook
The only way to downgrade your patch level is to install from a source that is not already patched to 1.69 (i.e. older discs) and patch that installation. Sorry.
I am Ghost. My husband is sidneydoj. I post, he downloads, and I wanted to keep my post count.
Group for Avatar Makers* Funny Stories *2017 Yearbook
#3
22nd Jan 2016 at 4:27 PM
Posts: 565
Thanks, @Ghost sdoj. I thought I had read somewhere that I could use superpatcher to downgrade, but I guess I read something wrong.
Will 1.67 mods work with 1.69? All the ones on MTS?
Will 1.67 mods work with 1.69? All the ones on MTS?
#4
22nd Jan 2016 at 9:58 PM
Some will, some may not. It depends on the mod.
If it's a scripted object or an XML mod, it probably will. No guarantees, but it's likely that nothing it depends on has been changed unless it's something affecting the Launcher.
If it's a core mod it won't. A core mod is built to a specific patch level.
I am Ghost. My husband is sidneydoj. I post, he downloads, and I wanted to keep my post count.
Group for Avatar Makers* Funny Stories *2017 Yearbook
If it's a scripted object or an XML mod, it probably will. No guarantees, but it's likely that nothing it depends on has been changed unless it's something affecting the Launcher.
If it's a core mod it won't. A core mod is built to a specific patch level.
I am Ghost. My husband is sidneydoj. I post, he downloads, and I wanted to keep my post count.
Group for Avatar Makers* Funny Stories *2017 Yearbook
#5
23rd Jan 2016 at 6:34 PM
Last edited by igazor : 23rd Jan 2016 at 11:54 PM.
Posts: 4,517
Well, it is good to be sensitive to that awful sounding error message core mods can kick up, I would hate to see it at launch each time. But...
If a core mod was designed to run on 1.67, it will display the core version mismatch error on startup if you have 1.69. But if that's the only reason for the error message, the mod will still work the same way once you click through that. There is nothing in any of the three releases of 1.69 that changes gameplay, only the build number (hence the error message) and the way that the game launches.
Script and tuning mods are not affected by the new patch at all.
The only TS3 core mods in common usage, that we know of (or that I am willing to talk about), are:
NRaas ErrorTrap - updated version available, we will continue to develop future versions for both 1.67 and 1.69 in parallel releases
NRaas UntranslatedKey - no updated version yet, but this is mostly for developers
CMarNYC's XCAS - updated version available, the 1.67 version is as well on her archive page
AwesomeMod - no update, they appear to be ignoring the whole thing over there
Consort's Grow and Fitness mods - no update, but he never updated for 1.67 so this is nothing new
Out of the so many thousands of mods and scritped objects out there, that should really be about it.
If a core mod was designed to run on 1.67, it will display the core version mismatch error on startup if you have 1.69. But if that's the only reason for the error message, the mod will still work the same way once you click through that. There is nothing in any of the three releases of 1.69 that changes gameplay, only the build number (hence the error message) and the way that the game launches.
Script and tuning mods are not affected by the new patch at all.
The only TS3 core mods in common usage, that we know of (or that I am willing to talk about), are:
NRaas ErrorTrap - updated version available, we will continue to develop future versions for both 1.67 and 1.69 in parallel releases
NRaas UntranslatedKey - no updated version yet, but this is mostly for developers
CMarNYC's XCAS - updated version available, the 1.67 version is as well on her archive page
AwesomeMod - no update, they appear to be ignoring the whole thing over there
Consort's Grow and Fitness mods - no update, but he never updated for 1.67 so this is nothing new
Out of the so many thousands of mods and scritped objects out there, that should really be about it.
#6
23rd Jan 2016 at 8:53 PM
Posts: 565
Thank you both for the info! Highly appreciated.
Who Posted
|