Constant Crashing

[Strawblurry Shortcake~<3]

I was wondering if anyone knew a way to get this game working on Windows 10. I've tried compatibility mode, lowering settings incase somehow my pc couldn't handle the game, gone into windowed mode, and uninstalled any & all mods I have. Nothing seems to work. I crash a good 5 minutes into a gamesave. Usually when turning the camera or viewing the world map.

[cruinne]

Can you tell us more about your computer - we have Windows 10. Let us know what the CPU is, and the graphics card, + how much RAM there is.

[Strawblurry Shortcake~<3]

Sure! My CPU is an Intel Core i7-7820X, graphics card is a GTX 1070TI & I have 16 gb of ram.

[cruinne]

That should definitely be enough.

With everything you've tried, my advice would be to clear everything - user files, registry entries, and all, and reinstall fresh. Then ensure that no compatibility options are applied (the game does not need compatibility changes to run on my lesser Windows 10 system - i7-7700HQ, 16 GB RAM, and GTX 1050Ti).

After a clean, fresh install, add the Overwatch and ErrorTrap mods from NRaas, then run the game "clean" - that is, without a bunch of other things running at the same time (decrapify if necessary).

[igazor]

May I ask if the OP has checked their fps rates in-game (if they have time to do so before the crashing thing happens) and if steps have been taken with the Nvidia Control Panel and if necessary Nvidia Inspector to arrange vertical sync for TS3w.exe and explicitly cap the frame rate? A card that strong will lead to far too high and wildly fluctuating frame rates otherwise, which in turn cause performance issues, lag, screen tears, crashing, and can ultimately burn out the card if not tended to. TS3 being an older game has no functional built-in fps limiter.

To check in-game, ctrl+shift+C to bring up the cheats console and type fps on (enter). As you play and move the game camera around, the displayed rate should never exceed the refresh rate of your monitor. Most are 60 Hz, so that means 60 fps, some can run higher. To make the display go away, cheats console again and fps off (enter).

This isn't specific to Win 10 though, players on all operating systems with cards that strong need to adjust these things to make TS3 work as it should for them.

[Bealla Donna]

Origineel geplaatst door cruinne:

Can you tell us more about your computer - we have Windows 10. Let us know what the CPU is, and the graphics card, + how much RAM there is.

Why does that even matter with old games? If anything, they'd be better playing this on a potato because this game is too broken for newer computers.

[cruinne]

Origineel geplaatst door Kaliliyah:

Origineel geplaatst door cruinne:

Can you tell us more about your computer - we have Windows 10. Let us know what the CPU is, and the graphics card, + how much RAM there is.

Why does that even matter with old games? If anything, they'd be better playing this on a potato because this game is too broken for newer computers.

Because some people come by saying "I have a brand new computer - I should be able to run this!" but neither their CPU or GPU are up to the game's spec. The game might be old, but there are a surprising number of new computers that do not meet its minimums.

Meanwhile... good catch, igazor that could totally be it.

[Strawblurry Shortcake~<3]

I do have V-Sync enabled & that sadly did nothing. I shall try re-installing everything tho! Hopefully that helps :P I'll keep ya updated.

[igazor]

It's relatively common for vsync arranged through the Nvidia Control Panel alone to not be enough to lock in the fps in full screen mode and it never works in windowed mode, in case that is relevant. Hence the next step of installing Nvidia Inspector and using it (in Section 2 of its settings) to explicitly cap the frame rate in addition to vsync. There are other third party tools we can call upon to do the same, I have to use RivaTuner on my end because my card is AMD and not Nvidia, but usually Inspector does the trick for those who can use it.

[Strawblurry Shortcake~<3]

Nope, an entirely fresh install (with all files related to the sims 3 deleted) did not fix the crashing. Sadly the mods didn't either. Could it be because im testing it out on Appaloosa Plains?? Thank you all btw for trying to help <3

[Strawblurry Shortcake~<3]

Origineel geplaatst door igazor:

It's relatively common for vsync arranged through the Nvidia Control Panel alone to not be enough to lock in the fps in full screen mode and it never works in windowed mode, in case that is relevant. Hence the next step of installing Nvidia Inspector and using it (in Section 2 of its settings) to explicitly cap the frame rate in addition to vsync. There are other third party tools we can call upon to do the same, I have to use RivaTuner on my end because my card is AMD and not Nvidia, but usually Inspector does the trick for those who can use it.

Do you happen to have a download link to Nvidia Inspector?? :o I tried googling it & just get a LOT of rather fishy looking sites offering different versions of it.

[igazor]

This one is genuine. Note that the real download links are about 2/3 of the way down the page, ingore any download offers in the upper right corner if you have no ad blocker as those are more likely to be rogue ads.
https://www.guru3d.com/files-details/nvidia-profile-inspector-download.html

[Strawblurry Shortcake~<3]

Nope, having both V-sync enabled & the fps counter ticked to 59.7 fps from both the Inspector & the Nvidia Control panel did nothing. Though I HAVE noticed the crash ALWAYS happens when I rotate the camera after awhile into the game, specifically after a minute or two of gameplay. And the crash is super common in parks.

[igazor]

What kind of actual fps rates are you getting in game, though (using the cheat code fps to see them). Is the game actually locking the GPU in at or under 60 as the settings above dictate?

If you have dual graphics, does the DeviceConfig log show that the Nvidia card is the one actually being used? It will show up after about 40 lines and then say Found/Matched 0 vs. 1. Formal recognition on the Found/Matched line is not so important, but if Intel is showing up there (again, possible if you have dual graphics) then the game is still trying to use the wrong GPU.

Other than those two things, I would have to say this is not typical game behavior regardless of upper end hardware and Win 10. Perhaps try dumping your TS3 user game folder (pull it out to the Desktop for safekeeping) and see if the game runs better on the new no-content one that will spawn to take its place.

[Strawblurry Shortcake~<3]

Hm... So I discovered something quite odd. I'll have to test more BUT the game works perfectly fine for me except for the Lexington Grounds park in Appaloosa Plains. If I visit or view anywhere near that park rotating my camera will crash the game.

I'll have to test more then :P Anyways! The game says I have 59 fps at all times pretty much & I do not have dual graphics. It also does say my GPU wasn't found BUT was matched. "NVIDIA GeForce GTX 1070 Ti [Found: 0, Matched: 1]"

[igazor]

Right, that doesn't mean the game cannot find your card on your computer, it means that it is not finding it in its database of known cards. This happens with all modern graphics cards and it's fine as long as the correct card is used. There are some minor benefits to editing the game's sgr files to grant formal recognition, such as a better set of defaults for Game Options are used, but that couldn't have been the issue at hand.

Good job on finding that it was most likely the Appaloosa lot causing the crashing, or at least that was part of it. I rarely play in that world and might not have noticed such a problematic lot. If you like the rest of the world, you could try removing the lot or replacing it with something else in Edit Town. Or play elsewhere if it turns out to have been more than that one lot causing the problem.