![]() Game is functional to the extent of no pink flashing and no crashes when switching hood or lots, but I haven't let it run for very long yet.ĮDIT: Spoke too soon. So yeah, all of these things seem to be necessary. NVIDIA drivers reinstalled via DDU & restart Tried to load a completely different household not used in any previous tests, but which is part of the same apartment as the household in 9. Went straight to secondary hood first, it is NOT flashing pink. It crashes again.Īttempt 10: Back to boolProp enableDriverMemoryManager true. Went straight to secondary hood first, it loads but is mostly flashing pink. Sad trombone.Īttempt 9: Removed cache & thumbnail files. Attempt to load the household that crashed in Attempt 6. Switching to another hood = 30% flashing pink. Exit household, application has crashed.Īttempt 8: Full cleanout & restart with DDU: Hood loads, household loads. Hood loads, household loads, both look normal. Sad trombone.Īttempt 7: Clean driver install via NVIDIA's executable, PC restart was not requested. Exiting out of household back to hood view, it is no longer pink. Switching to another neighborhood, hood view is about 30% flashing pink. However, switching to a different neighborhood crashes.Īttempt 6: Undid changes in attempt 4, so now: boolProp enableDriverMemoryManager false. Crashed when loading household!?Īttempt 4: boolProp enableDriverMemoryManager true: crashes when loading neighborhood.Īttempt 5: I restored the cache and thumbnail files deleted in Attempt 3. so game sort of works.Īttempt 3: deleted cache and thumbnails (no other changes). exe, windowed mode.Īttempt 2: applied 4GB patch: hood view loads, is mostly flashing pink. When I first started having these problems, the game would be okay for a while, and then next thing I knew, the household was pink. Also curious to see how long the game will go without crashing. Unfortunately I don't know which step did it, and don't have time to roll stuff back one piece at a time to find out. everything is flashing pink.ĥ) Slowly did the 50/50 CC test, and never did find anything (each subsequent load was fine). game is now working on my original PC (identical in specs to top post of this thread, but different machine).Ĥ) Added in all my old hoods and downloads. Going backwards now.ģ) Used this 4GB patch. Result, crash on loading household.Ģ) Clean NVIDIA driver install after DDU cleanout. exe and in windowed mode.)ġ) Edited Graphics Rules to include: "boolProp enableDriverMemoryManager true". I can move it over to MTS instead, although there's a certain "it's not happening to me, so it must not be happening" element that persists over there,įollowing CatOfEvilGenius's most recent info: If you want the thread somewhere else, please let me know. ![]() My apologies to the mods, this site is just where I've seen the most troubleshooting happen when it comes to making this older game work on newer hardware and operating systems. Second edit: it occurs to me that I'm posting this in a subforum called "Sims Graphics Cards" while saying I don't think it's a GPU problem. After 1709, the problems persisted after a clean driver install to bring them up to Jan 2018. ![]() I ran that game install frequently over the winter. My original "flashing pink" problem (which started immediately after my original PC installed 1709) was on a PC with a GTX 1070 running drivers from Oct 2017. I checked Reddit, but unfortunately everyone there plays sims 4.Įdited to add: I really don't think this is graphics drivers, but for what it's worth: ![]() I'd actually recommend people start posting directly on the EA forums, because I think that's where the fix will come from. iso rips of the CDs, which I no longer own), but not a ton of time, and even if that worked it's a dumb solution when we have the UC all rolled up and easy to install. I've got a lot of different things in mind to try (like my old. All I've really done so far is narrow down the conditions to a set where the problem is 100% reproducible. I'll probably keep chipping away at this on my end because I'm stubborn, but I'm unlikely to be the person who finds the fix. I'm trying to keep up with the various threads on this topic, and I know things are a bit scattered, but it does seem pretty apparent to me that on certain machine configurations, Windows 1709 is breaking the game. (In those scenarios I just wipe the machine in question.) I think "reset this PC" is a bit more destructive, but I've never used it: Unfortunately "Go back to an earlier build" is the exact wording that was there when I did it: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |