Murse Steve Murse Steve

Sins and Vista?

▼

Sins and Vista?

Sins + Vista = Love?

from Sins Forums
I recently stumbled upon this game from various gaming websites/forums rabidly raving about how sweet this game is. My only concern, is that about Five-ish months ago I bought a new gaming computer. Unfortunately, I didn't do enough research and am now unhappily stuck with Windows Vista (AKA piece of shista). While things have been getting slightly better due to my use of 3rd party programs like Wlan to stop annoying internet hiccups; most games still have flaws that do not work well on my computer.

Examples:
**TF2 randomly has an error where the driver crashes, but miraculously recovers about a minute later. It's like watching the resurrection! (My drivers are all up to date)
**Universe at War: Randomly crashes when the game starts to get interesting. (Unrelated to number of units, the crash is, completely random.)

My point is this. Both of these games are part of the new cute line of "Games for Windows!" However it is in my honest opinion that the line should read "Games for Windows XP Service Pack 2."

So, developers. I have a Geforce 8500gt graphics card, 4 gigabytes of memory, over 500 GB of disk space and a sincere will to try your game. My question to you is this: Is your game Vista friendly or should I avoid this game too?

Ps. I read you're coming out with a demo soon.. interesting! Perhaps I will wait and see how well that runs on my machine before deciding to purchase. Time-i
technical
16,386 views 32 replies
Reply #26 from Sins Forums Top
"Display driver nvlddmkm stopped responding and has successfully recovered."
End of quote


This is what I was looking for. This is the TF2 error I was talking about. If anyone knows if this is just a vista bug or what. I've googled the internets and can't find a solution to this problem. Since TF2 has that error I'm going to safely assume that this game will as well. Bummer, I really wanted to try this game out too. Ah well, if the community wants to help me figure out what the heck is wrong with display driver nvlddmkm, it'd be most appreciated as it would allow my purchase of this quality game.

Reply #27 from Sins Forums Top
Just found this:

http://www.microsoft.com/whdc/device/display/wddm_timeout.mspx
Elemental: Reforged
Reply #28 from Sins Forums Top
Vista64 Home Premium - AMD X2 6000 - 8gb ram - 7950gx2

Only thing that happens to me is every now and then the game will freeze for 5 - 10 seconds, screen will flickr black once and go back into game like nothing happened. When it runs, it's smooth and sweet.

It's the only game I have had any problems with in Vista and as 2 of the developers have already stated, it's a driver problem and should be in Nvidia's court now to fix.

TF2 runs like a champ on my system. Never had anything from Valve crash on my Vista install.
Reply #29 from Sins Forums Top
Vista Home Basic, 1g RAM, 80G hard drive (20G for Linux, 20G for Vista, 40G of FAT32 so both OS can read-write to it).

Laptop was 350 bucks one-day sale at Walmart, integrated Intel graphics. Better to play Sins with a mouse than the touchpad but it does an acceptable job of playing.
Reply #30 from Sins Forums Top
game runs fine in Vista or XP, However there are network desynchronizations (minidumps) i believe when you play against XP players. and vice versa. im going to test this hypothesis today.
Reply #31 from Sins Forums Top
Vista Ultimate 32-bit, 4 gig ram, 500 gig HDD, 8400M nvidia, HP laptop, core 2 duo 2.0Ghz...

I would get a lockup after about 3-5 hours of playing where it wouldnt save anymore because the memory became full. Since 1.02 I havent had that problem. I played a 10 straight hour game without so much as a hickup. The engine is extremely smooth even on the laptop. I say go for it! This game is worth playing!

Reply #32 from Sins Forums Top
Apparently the problem I'm experiencing is one between nvidia graphics drivers + vista. Supposedly vista is fixing this in service pack 1. However, SP1 is only available to beta-testers at this time. Not all games cause this error though. So, since someone else has already experienced this error, it looks like there is nothing I can do but hope and wait.