EA/Maxis has found the Nvidia problem!
morriganrant:
Quote from: MistyBlue on 2008 March 15, 03:44:41
It's not JUST Norton, it's Norton in conjunction with nVidia and possibly system specs. Read and use logic dammit!
If you have an ATI card, this does not pertain to you...
I know that, but they are arguing that their game does not have a memory leak. Which it does. Norton is also a resource hog. You would think that at least some issue would come up with others if it is just Norton, even if it wasn't the same card. It is still a little mysterious what it is that Navidia has that seems to go "ARrRRRRGGGGEEEEE NOOOOO" when in combination with Norton. Is it that NAvidia needs more from a machine then an ATI card does? Thus card that requires a lot+ Game that requires a lot+ virus scan that hogs a lot = boom? The point is that they can not just blame Norton, there is more there, how many other performance demanding games get this blue screen with the same card and Norton running? I mean seriously?
SnootCB:
What gets me is that they are basing this conclusion off of one instance that they experienced on one computer and are pretty much completely ignoring customer feedback.
Quote from: doren on 2008 March 14, 13:48:34
Like many others - at least 20 in a German forum posting on this topic (everyone who tried it) - I could solve the problem by switching back to an "outdated" driver. Unfortunately this is not a solution for anyone with a brandnew nVidia card because the latest series don't work with this driver. Did I report my finding on the BBS? Did I tell EA tech support? - Yes. What is the first message you get from tech support? - Update your drivers. It's pathetic. Now if I have a driver that works and then the next version doesn't my logical conclusion would be to compare the two, look at the changes and try to narrow down the problem. It's not the way EA/Maxis approached this though. I do not expect them to ever find the answer, so I am sticking to my old driver and my old card (which is pretty good anyway and can handle the game without problems) and have the problem solved for myself.
I've also heard that using old drivers helps. I tried going back three or four drivers with no luck. That was last summer. What drivers are you using? I may just not have gone back far enough.
On top of all that, they have already fixed this problem once before. It broke again with BV for me. I'm inclined to lay the blame equally on nVidia and Eaxis, because similar-quality ATI cards don't have this problem with TS2, and my nVidia card doesn't have this problem with any other game.
I got tired of arguing with TS2 tech support about this several months ago. Here's what we know: across multiple system builds that include otherwise satisfactory nVidia cards, turning off shaders fixes the mystery BSOD, and apparently using outdated drivers fixes it too. Now, what could those two things have in common, besides having absolutely NOTHING to do with Norton?
doren:
Quote from: SnootCB on 2008 March 15, 04:34:52
I've also heard that using old drivers helps. I tried going back three or four drivers with no luck. That was last summer. What drivers are you using? I may just not have gone back far enough.
6.14.00010.7772 build june 2005. I got the problem when I updated with the next version, build sometime 2006. I get a few minor graphical glitches (sometimes the neighbourhood screen darkens when I rotate the view, but only for a few seconds), but otherwise it works fine, I get all the effects, water reflections, fish etc..
I have a Geforce 6600 GT.
DJKID:
I run a GeForce 8600 GT, and if I don't turn off shaders I get the BSOD about 10 minutes within the loading of a lot. I don't have Norton on my computer and I turn everything, with the exception of iTunes, off before running Sims. These guys are so full of crap it's starting to really piss me off... Is anyone here going to bother fighting EA on the subject?
On a different note, I'm sorry if this sounds incredibly stupid... but what exactly do you guys mean by a "memory leak" and how would they fix it?
jsalemi:
Quote from: DJKID on 2008 March 15, 14:10:48
but what exactly do you guys mean by a "memory leak" and how would they fix it?
A memory leak is when an application keeps taking new memory to run the same functions rather than using the memory it's already allocated. They fix it by proper programming (i.e., having the app check to see if what it's looking for is in memory already first before allocating more).
Navigation
[0] Message Index
[#] Next page
[*] Previous page