#Sims 3 Alder Lake issue
Explore tagged Tumblr posts
Text
Yet more hassle for this game
Well, I got CC Magic to actually stay open (see my previous post) but then I had an even bigger issue: no matter what I did, no matter which .exe file I ran, The Sims 3 simply wouldn't start up. I tried via CC Magic, I tried via Steam, I tried via the direct .exe files. The launcher would fire up, I'd click to play, and then it would close. No error messages; it just closed.
After a lot of frustrated (and increasingly frantic) googling, I found out why. I'm a victim of the 'Alder Lake issue'. That is, the CPU in my new PC is an Intel 12th Gen ('Alder Lake') processor, and it turns out that... EA haven't fixed a specific issue.
They've been aware of it since January 2022, when - according to the users of their help forum, "The only news we've received from EA is that someone is looking into it. Part of the problem is that there isn't a team at EA responsible for upkeep on Sims 3 in general: the development team was disbanded back in 2013 or so."
Thankfully, a user named Miaa245 wrote a PowerShell script that fixes the issue. Find it on the second post of this page, if you encounter the same issue and need a fix. (Instructions are here if you're not sure what to do.) You have to run the script every single time before you launch the game, and apparently it fixes the issue by limiting the game to only one CPU core while it loads, then - once it's loaded - reinstating all the CPU cores.
It runs well enough that way with no CC other than a couple of essential NRaas mods, but I've not yet tried it with a bunch of CC. I've also just tried launching it via Steam (as that's how I have it installed) for now, and I managed a couple of hours of gameplay.
Tomorrow I'll try launching it via CC Magic, and if that works I'll start pushing a little CC into my folders, to see if it can handle that.
The things I do to keep playing this game that I love so much :(
ETA: I do still have the old PC, which runs it just fine, as well as my gaming laptop (which I keep for cc-free building; seriously, mine is a multi-computer household!) So if push comes to shove I'll just have to set up another desk elsewhere in the house for the old computer to sit, just so I can play Sims 3 there.
ETA 2 - 29-Jan 2023: @lazyduchess - once again you have saved a Simmer's bacon. THANK YOU THANK YOU THANK YOU for this patch for the Sims 3 Alder Lake processor issue. I'd previously been using a PowerShell workaround that was - quite honestly driving me bonkers because I had to continually use it every time I wanted to install something new via the launcher - but your patch worked like a dream for me. I am SO HAPPY right now, you have no idea. You're an absolute star <3
10 notes
·
View notes
Text
Quick Newsflash
After much blood sweat and tears, the Jazz Hands half of our operations has got Sims 3 finally working again.
What was crucial was the Lazy Duchess Alder Lake patch (or whatever it's called).
Now for the plot twist.
Your humble narrator is using a desktop which is using the same processor, an Intel i9-14900KF, as the one that has just about reduced the other half to tears trying to get to work. Yet only they had to use the Lazy Duchess patch to get the game to work. Figure that one out.
Other half is now about to enter the following phrase of switching from a Windows 10 compliant laptop to a Windows 11 compliant laptop to run Sims 3 on ...
3 notes
·
View notes
Text
How to use DXVK with The Sims 3
Have you seen this post about using DXVK by Criisolate? But felt intimidated by the sheer mass of facts and information?
@desiree-uk and I compiled a guide and the configuration file to make your life easier. It focuses on players not using the EA App, but it might work for those just the same. It’s definitely worth a try.
Adding this to your game installation will result in a better RAM usage. So your game is less likely to give you Error 12 or crash due to RAM issues. It does NOT give a huge performance boost, but more stability and allows for higher graphics settings in game.
The full guide behind the cut. Let me know if you also would like it as PDF.
Happy simming!
Disclaimer and Credits
Desiree and I are no tech experts and just wrote down how we did this. Our ability to help if you run into trouble is limited. So use at your own risk and back up your files!
We both are on Windows 10 and start the game via TS3W.exe, not the EA App. So your experience may differ.
This guide is based on our own experiments and of course criisolate’s post on tumblr: https://www.tumblr.com/criisolate/749374223346286592/ill-explain-what-i-did-below-before-making-any
This guide is brought to you by Desiree-UK and Norn.
Compatibility
Note: This will conflict with other programs that “inject” functionality into your game so they may stop working. Notably
Reshade
GShade
Nvidia Experience/Nvidia Inspector/Nvidia Shaders
RivaTuner Statistics Server
It does work seamlessly with LazyDuchess’ Smooth Patch.
LazyDuchess’ Launcher: unknown
Alder Lake patch: does conflict. One user got it working by starting the game by launching TS3.exe (also with admin rights) instead of TS3W.exe. This seemed to create the cache file for DXVK. After that, the game could be started from TS3W.exe again. That might not work for everyone though.
A word on FPS and V-Sync
With such an old game it’s crucial to cap framerate (FPS). This is done in the DXVK.conf file. Same with V-Sync.
You need
a text editor (easiest to use is Windows Notepad)
to download DXVK, version 2.3.1 from here: https://github.com/doitsujin/DXVK/releases/tag/v2.3.1 Extract the archive, you are going to need the file d3d9.dll from the x32 folder
the configuration file DXVK.conf from here: https://github.com/doitsujin/DXVK/blob/master/DXVK.conf. Optional: download the edited version with the required changes here.
administrator rights on your PC
to know your game’s installation path (bin folder) and where to find the user folder
a tiny bit of patience :)
First Step: Backup
Backup your original Bin folder in your Sims 3 installation path! The DXVK file may overwrite some files! The path should be something like this (for retail): \Program Files (x86)\Electronic Arts\The Sims 3\Game\Bin (This is the folder where also GraphicsRule.sgr and the TS3W.exe and TS3.exe are located.)
Backup your options.ini in your game’s user folder! Making the game use the DXVK file will count as a change in GPU driver, so the options.ini will reset once you start your game after installation. The path should be something like this: \Documents\Electronic Arts\The Sims 3 (This is the folder where your Mods folder is located).
Preparations
Make sure you run the game as administrator. You can check that by right-clicking on the icon that starts your game. Go to Properties > Advanced and check the box “Run as administrator”. Note: This will result in a prompt each time you start your game, if you want to allow this application to make modifications to your system. Click “Yes” and the game will load.
2. Make sure you have the DEP settings from Windows applied to your game.
Open the Windows Control Panel.
Click System and Security > System > Advanced System Settings.
On the Advanced tab, next to the Performance heading, click Settings.
Click the Data Execution Prevention tab.
Select 'Turn on DEP for all programs and services except these”:
Click the Add button, a window to the file explorer opens. Navigate to your Sims 3 installation folder (the bin folder once again) and add TS3W.exe and TS3.exe.
Click OK. Then you can close all those dialog windows again.
Setting up the DXVK.conf file
Open the file with a text editor and delete everything in it. Then add these values:
d3d9.textureMemory = 1
d3d9.presentInterval = 1
d3d9.maxFrameRate = 60
d3d9.presentInterval enables V-Sync,d3d9.maxFrameRate sets the FrameRate. You can edit those values, but never change the first line (d3d9.textureMemory)!
The original DXVK.conf contains many more options in case you would like to add more settings.
A. no Reshade/GShade
Setting up DXVK
Copy the two files d3d9.dll and DXVK.conf into the Bin folder in your Sims 3 installation path. This is the folder where also GraphicsRule.sgr and the TS3W.exe and TS3.exe are located. If you are prompted to overwrite files, please choose yes (you DID backup your folder, right?)
And that’s basically all that is required to install.
Start your game now and let it run for a short while. Click around, open Buy mode or CAS, move the camera.
Now quit without saving. Once the game is closed fully, open your bin folder again and double check if a file “TS3W.DXVK-cache” was generated. If so – congrats! All done!
Things to note
Heads up, the game options will reset! So it will give you a “vanilla” start screen and options.
Don’t worry if the game seems to be frozen during loading. It may take a few minutes longer to load but it will load eventually.
The TS3W.DXVK-cache file is the actual cache DXVK is using. So don’t delete this! Just ignore it and leave it alone. When someone tells to clear cache files – this is not one of them!
Update Options.ini
Go to your user folder and open the options.ini file with a text editor like Notepad.
Find the line “lastdevice = “. It will have several values, separated by semicolons. Copy the last one, after the last semicolon, the digits only. Close the file.
Now go to your backup version of the Options.ini file, open it and find that line “lastdevice” again. Replace the last value with the one you just copied. Make sure to only replace those digits!
Save and close the file.
Copy this version of the file into your user folder, replacing the one that is there.
Things to note:
If your GPU driver is updated, you might have to do these steps again as it might reset your device ID again. Though it seems that the DXVK ID overrides the GPU ID, so it might not happen.
How do I know it’s working?
Open the task manager and look at RAM usage. Remember the game can only use 4 GB of RAM at maximum and starts crashing when usage goes up to somewhere between 3.2 – 3.8 GB (it’s a bit different for everybody).
So if you see values like 2.1456 for RAM usage in a large world and an ongoing save, it’s working. Generally the lower the value, the better for stability.
Also, DXVK will have generated its cache file called TS3W.DXVK-cache in the bin folder. The file size will grow with time as DXVK is adding stuff to it, e.g. from different worlds or savegames. Initially it might be something like 46 KB or 58 KB, so it’s really small.
Optional: changing MemCacheBudgetValue
MemCacheBudgetValue determines the size of the game's VRAM Cache. You can edit those values but the difference might not be noticeable in game. It also depends on your computer’s hardware how much you can allow here.
The two lines of seti MemCacheBudgetValue correspond to the high RAM level and low RAM level situations. Therefore, theoretically, the first line MemCacheBudgetValue should be set to a larger value, while the second line should be set to a value less than or equal to the first line.
The original values represent 200MB (209715200) and 160MB (167772160) respectively. They are calculated as 200x1024x1024=209175200 and 160x1024x1024=167772160.
Back up your GraphicsRules.sgr file! If you make a mistake here, your game won’t work anymore.
Go to your bin folder and open your GraphicsRules.sgr with a text editor.
Search and find two lines that set the variables for MemCacheBudgetValue.
Modify these two values to larger numbers. Make sure the value in the first line is higher or equals the value in the second line. Examples for values: 1073741824, which means 1GB 2147483648 which means 2 GB. -1 (minus 1) means no limit (but is highly experimental, use at own risk)
Save and close the file. It might prompt you to save the file to a different place and not allow you to save in the Bin folder. Just save it someplace else in this case and copy/paste it to the Bin folder afterwards. If asked to overwrite the existing file, click yes.
Now start your game and see if it makes a difference in smoothness or texture loading. Make sure to check RAM and VRAM usage to see how it works.
You might need to change the values back and forth to find the “sweet spot” for your game. Mine seems to work best with setting the first value to 2147483648 and the second to 1073741824.
Uninstallation
Delete these files from your bin folder (installation path):
d3d9.dll
DXVK.conf
TS3W.DXVK-cache
And if you have it, also TS3W_d3d9.log
if you changed the values in your GraphicsRule.sgr file, too, don’t forget to change them back or to replace the file with your backed up version.
OR
delete the bin folder and add it from your backup again.
B. with Reshade/GShade
Follow the steps from part A. no Reshade/Gshade to set up DXVK.
If you are already using Reshade (RS) or GShade (GS), you will be prompted to overwrite files, so choose YES. RS and GS may stop working, so you will need to reinstall them.
Whatever version you are using, the interface shows similar options of which API you can choose from (these screenshots are from the latest versions of RS and GS).
Please note:
Each time you install and uninstall DXVK, switching the game between Vulkan and d3d9, is essentially changing the graphics card ID again, which results in the settings in your options.ini file being repeatedly reset.
ReShade interface
Choose – Vulcan
Click next and choose your preferred shaders.
Hopefully this install method works and it won't install its own d3d9.dll file.
If it doesn't work, then choose DirectX9 in RS, but you must make sure to replace the d3d9.dll file with DXVK's d3d9.dll (the one from its 32bit folder, checking its size is 3.86mb.)
GShade interface
Choose –
Executable Architecture: 32bit
Graphics API: DXVK
Hooking: Normal Mode
GShade is very problematic, it won't work straight out of the box and the overlay doesn't show up, which defeats the purpose of using it if you can't add or edit the shaders you want to use.
Check the game's bin folder, making sure the d3d9.dll is still there and its size is 3.86mb - that is DXVK's dll file.
If installing using the DXVK method doesn't work, you can choose the DirectX method, but there is no guarantee it works either.
The game will not run with these files in the folder:
d3d10core.dll
d3d11.dll
dxgi.dll
If you delete them, the game will start but you can't access GShade! It might be better to use ReShade.
Some Vulcan and DirectX information, if you’re interested:
Vulcan is for rather high end graphic cards but is backward compatible with some older cards. Try this method with ReShade or GShade first.
DirectX is more stable and works best with older cards and systems. Try this method if Vulcan doesn't work with ReShade/GShade in your game – remember to replace the d3d9.dll with DXVK's d3d9.dll.
For more information on the difference between Vulcan and DirectX, see this article:
https://www.howtogeek.com/884042/vulkan-vs-DirectX-12/
534 notes
·
View notes
Text
Sims 3 and 12, 13 and 14th gen Intel
I want to save people from the major stress that I went through changing to a new computer this weekend. First off, EA help chat won't be of any help. I don't know why this likely common issue is unknown to them but apparently it is.
If you get a computer with an i8 or i9 Intel core Sims 3 will not open. There are two fixes (one worked for me one didn't). One involves going into task manager after opening launcher and choosing affinities and going to one only core (hopefully I am explaining this correctly). It was mentioned in a post that after the game loads you can go back to all processors because menus will take a while to load, but I haven't tested that. The other fix is running a powershell script I think after loading launcher right before you go into game. This is the one I couldn't get to work. You can put the error below into google and should find discussions of this issue. There are also threads in the ea help forums. You may need to look for 'Sims 3 Alder Lake' and that might bring it up if you have any issues.
Essentially if you get an error in your Sims 3 document and it says '
[Exception info] date: 2024-03-09 time: 17.42.18 type: INT_DIVIDE_BY_ZERO' you likely have this issue.
Hopefully I can save anyone any stress when their game won't open.
0 notes
Text
Across Canada
I will try to post a little more text today, but the internet service here is pretty poor so I will leave posting of any more photos until we get home. We leave the US this evening and arrive back in Melbourne before dawn on Wednesday, having missed an entire day along the way.
We took a cab to Union Station to catch the VIA Rail across the country. We have usually paid cab fares by card, but Heather used cash this time. The cabbie gave her a few coins as change and when Heather said that there should have been some notes, he said he was keeping that as his tip - about 50% of the fare. Heather argued, but he bullied her and insisted that he was keeping it. Had I been closer instead of getting our bags out of the boot, he may not have been so demanding, but it left a sour taste in our mouths as it was.
The train is by no means luxurious, obviously oldish, but it is quite functional and we are comfy enough in our little cabin. One good thing is that the bunks are bigger and much more comfortable than on the ship or the other trains we have used. We have both slept well.
On the other hand, there is no WiFi at all, only an occasional phone signal and although there are 110-volt power outlets, they won’t charge my PC - so once again, the technology has failed us. Maybe I am naive, but we are now in the 21st century and I reckon basic power and signal issues should have been sorted out years ago. As it is, the battery in my PC is flat and there is no way I can use it until we reach Vancouver at best. That means I can’t look at my photos or do much with my blog other than draft bits on my iPad.
Canada is exquisitely beautiful. It is an absolute picture postcard, full to bursting with trees and lakes. The overwhelming colour is green, with literally billions of tall skinny pointy trees. Actually, they are not that tall. We have seen very few trees more than 8-10 metres tall, but there are zillions of them, mostly densely packed with both understory and overstory. In some places, it is a bit more open, but still usually gloomy and mysterious, inviting us to explore - if only we were out there in the bush. Aspen, larch, spruce, alder, birch, pines and firs, conifers of every description, millions of stark white trunks, black trunks, all sorts, drowning in a thousand shades of green, leaves shimmering in the breeze, gleaming in the sun, with just a smattering of autumn tones starting to appear here and there.
Then there are the thousands of lakes. We must have traversed 1000 kilometres of marshy land with water shimmering through the low vegetation as far as we could see. But there are thousands of open lakes as well, from just a hectare or two to those speeding past the train for kilometre after kilometre. Did I say picture postcard? We have seen them all. The little ones that look like they came out of a cutesy 50s or 60s movie, with the summer camp atmosphere - a few canoes tied up to a little landing, a pontoon and shallow diving board, a short rowing course, maybe a pathetic little waterski-jump and a collection of quaint little huts that are probably family holiday shacks. Then there are the more remote ones, some with a tiny island or two with just 2 or 3 perfectly conical fir trees on them and a kayak tied up to a partly-submerged drowning landing that defies imagination about how one might access it - not even a hiking track, much less a road, in sight. Then we have the larger ones with a couple of small tinnies out there, each with a fisherman or two, sound asleep with their rods dangling limp over the side, or perhaps the ten deserted sheds, some literally falling down, and only a tiny Cessna anchored to the shore to suggest that anyone might occasionally visit them. We are not talking upscale Hillbilly country. This is magically picturesque country that should warrant criminal charges if anyone but us invades it. Add your own superlatives, but for me, I have run out. Simply stupendously glorious!
Later. We have just crossed the border from massive Ontario into Manitoba - after more than 20 hours heading west. Slowly, the trees and lakes seem to be getting slightly larger, the terrain is a little more open, the trees a little lighter green and the wildflowers more profuse and colourful - mainly white, yellow and mauve/purple.
For the entire trip, there has been a line of telegraph posts and cables beside the train: around 20 cables, but obviously long defunct. Thousands of the posts have simply sunk into the boggy earth or fallen over or submerged into the lakes, and many of the cables are broken or hanging limp and tangled. I am amazed that nobody has attempted to salvage the hundreds of thousands of dollars of copper out there.
As we went west, it became a little hillier and we even went through a couple of short tunnels. We also went through many cuttings where the rock had been blasted away for the track. There was a lot of red in the rocks and it is likely that some sort of algae was growing on it to make it that colour.
It was getting dark when we rolled into Winnipeg, but we had an hour and a bit stopover, so we went into the station and used the WiFi to download our email - alas, mostly more bills to pay! I had prepared a few emails to send, but they were all on my PC and inaccessible due to the flat battery!
It was a very rocky night, but we were up early for showers. I raised the blind just a centimetre or two in our cabin and could see everything there was to see. The landscape was entirely in landscape. Flat, flat, flat - all the way to the horizon. Everything looked manicured as if the farmers had risen early and swept or ironed their paddocks to welcome us. A bit later, we saw patches of forest and lots of neat (or sometimes sprawling) farmhouses, often with 2 or 3 little cottages and a barn or two, and mostly at least a field-bin or ten (or 30) and a tractor parked nearby. Many farms also have a machinery graveyard, usually at a distance from the house, with rows of rusty tractors, trucks, cars, pick-ups, ploughs, harvesters, caravans, campers and who knows what, all lined up in their final resting places, slowly sinking into the landscape. The houses all have pitched rooves, presumably to avoid too much snow collecting on them in the winter.
The paddocks are mainly cropped with wheat, barley, oats and canola, but there is also a lot of uncropped land, mostly looking too boggy to crop. Quite a bit of the uncropped land is still productive though, with miles of road and rail verges being harvested and baled for silage. It is obviously harvest time over here with quite a lot of crop already cut, but with plenty more still to go. We haven’t seen much actually being harvested, but plenty of hay bales in neatly shorn paddocks. There are a few cattle but no big herds. Also a few horses, half a dozen goats, a donkey, a young deer standing beside the track staring at me - and at least one fox scampering across the prairie with four magpies harassing it. It was nearly two days later before we saw any sheep: about 20 near one house and 3 at another – then none through to Vancouver.
There have been a few shallow lakes, mainly fairly small and at last, a few birds. We crossed one wide river, very shallow with flat mud islands and hundreds of birds: all gulls and Canada Geese as far as I could see. It is very frustrating not having any internet because I can’t identify the birds conclusively without my favourite Merlin app, but I am taking photos and making notes and hope I will be able to tie some of them down later. It is even more frustrating that Heather can sit there posting to Facebook and her blog almost any time when the SIM we purchased for me doesn’t work in either my phone or my iPad!
There were a few places along the rivers and nearby lakes where I suspect beavers were at work. A couple of creeks appeared to be dammed and there was an area near one suspected lodge where a whole lot of smallish trees had been felled – all with pencil-sharpener bases. And I saw a few flat conical structures a metre or so above the water level – again with a collection of pick-up-sticks pencil-ended logs embedded in the structure. I could be just imagining it, but the indications seemed to be there that beavers could have created the dams and underwater pyramids.
It is strange that we rocketed through the night, speeding along much faster than anywhere to date, making for a very bumpy ride - then arriving in Saskatoon where they said we were way ahead of our timetable so there would be a two hour stopover to get back on schedule. Go figure! The track we are on is apparently owned by a freight company and freight trains always have priority. This means that we frequently need to stop at sidings or on branch lines, often for half an hour or more until a freight train passes. The freight trains are massive, up to about 3 kilometres long and mostly double-deckers that roar along carrying hundreds of thousands of tonnes of cargo across the country day and night. They are not as bad as in Russia where a few kilometres of freight barrelled past us every time I raised my camera for a shot, but there must still be at least several dozen here each day.
Next time we woke up, we were in Saskatchewan and the terrain slowly became more varied, with lumpy low hills, uneven ground, more diverse vegetation, taller trees and in due course, we had an hour or so stopover in Edmonton and next morning we rolled into Jasper in the Canadian Rockies. Our Edmonton stop was marked by the start of a dramatic electrical storm. It was really ferocious with lightning flashing brilliantly around us every few seconds. We went to dinner as it was getting dark and the lightning outside the dining car was tremendous. We were soon locked up, cosy in bed, but several other passengers said the electrical storm was amazing and followed us for hours.
1 note
·
View note