patches for beta?

from Sins Forums

Hi guys, I have had a pretty bad time with the constant crashing of the game to the point I actually reinstalled vista fresh onto the machine again to see if it fixed my problems.

After updating the drivers etc I installed sins and it seemed to play okay for about an hour then I got the same error back with the gameplay pausing, going black, then a 50/50 chance of the game continuing or it crashing leaving me with a blank screen which I have to alt-tab out of. (I think its vista recovering the drivers??)

Don't worry I understand what beta is so this is no flame my question is do you release patches between the main betas, or do I need to wait until Beta 4?



8,059 views 21 replies
Reply #1 from Sins Forums Top
Don't worry, they do release patches between betas.

You do have sent them the crash messages, mini dump, etc.? Or they won't be able to fix the crash, of course.
Sins of a Solar Empire II
Reply #3 from Sins Forums Top
How much memory do you have, and what's your pagefile set at? What driver and graphics card?

Sounds like an out of memory error.

As for patches, Blair (head honcho) mentioned in another thread that there might be a hotfix this week, to address the AI issue at least.
Reply #4 from Sins Forums Top
Hi, seem to be having an ID crisis at the moment (posting as FluXsUK and FluXs at work \o/)

I posted spec before under FluXsUK, but cant find it.

Off the top of my head (at work atm) its:

2GB DDR2 (OCZ)
NVIDIA GeForce 7950 GT
NVIDIA NForce 680i SLi Motherboard
Intel Core2Duo 2.4Ghz (6600)
x2 500GB (SATAII)
Vista 64bit (Prem)

page file.. cannot check here, but it will be at.. 'default' ^_^

I'm using nvidias 162.18, I tried the beta ones before I formatted, but it killed the game during loading...

all my other drives including BIOS have all been checked


memory error? When I get home ill run a memory check.
Reply #5 from Sins Forums Top
If I had to guess, I would say the issue is the 64-bit edition of Vista. I've got the 32 bit running with similar CPU, GeForce 8800gtx is the largest difference, and the game hasn't crashed once, even with the beta drivers I installed for Crysis.
Reply #6 from Sins Forums Top
Give http://www.nvidia.com/object/winvista_x64_163.69.html a try FluXs, they aren't beta and are what I run with with my 7800GTX on Vista x64 Ultimate, granted I have an inferior setup as far as Ram, CPU, Mobo goes.
Reply #7 from Sins Forums Top
apologies Novaburst, (I am at home now) just checked and I am already running the 163.69 drivers

Ive just installed the beta ones again (163.71) and it let me load the game but it lagged like hell, also got the blank screen from vista resetting drivers... This time the game didnt crash out with a mini dump as I only got about 4 minutes of gameplay and quit the game myself. I got the usual dialog box waiting for me on the desktop:

"Display driver nvlddmkm stopped responding and has successfully recovered."

Which is true if you leave it long enough the game continues but you get the constant repeating sounds effects until it does.   and afterwards this time constant lag...

The error itself is very generic as seen from this 113 thread on nvidias forum
http://forums.nvidia.com/index.php?showtopic=25381

 

/jumps out window
Reply #8 from Sins Forums Top
"Display driver nvlddmkm stopped responding and has successfully recovered."

Which is true if you leave it long enough the game continues but you get the constant repeating sounds effects until it does. and afterwards this time constant lag...

The error itself is very generic as seen from this 113 thread on nvidias forum
http://forums.nvidia.com/index.php?showtopic=25381


Funky. I started getting this once in a while with World in Conflict and Crysis, but it hasn't happened in Sins yet. I was partly right though, it does seem to be a Vista issue, just not Sins-specific.
Reply #9 from Sins Forums Top
Hmm, I didn't update to the very latest beta drivers yet and haven't had any issues. We do have a ticket in with Nvidia on previously reported crash bugs with their drivers, however.
Reply #10 from Sins Forums Top
well i got a pretty much virgin pc atm, vista, stardock central, sins and gtalk, thats it! I did a complete format and reinstall on this pc yesterday.

The beta drivers made the problem worse for me, but its the same error. vista recovers the drivers the game pauses goes blank and comes back to life. eventually after 3 or 4 times the game doesnt come back and crashes out. Im no programmer so I could not say if its nvidia with sins eventually crashing due to the numbers of resets, or vice versa...

Ive tried all different types of settings even on super high with x4 anti-alias its the same.

Reply #11 from Sins Forums Top


page file.. cannot check here, but it will be at.. 'default' ^_^


We need to know how much is being used to be able to evaluate it. Though on Vista, that number will be high anyway...
Reply #12 from Sins Forums Top

We need to know how much is being used to be able to evaluate it. Though on Vista, that number will be high anyway...


When I get home from work (about 1 hour from now) ill post the page file size.
Reply #13 from Sins Forums Top
Right, according to vista my page file is at 2345mb (auto manage)

min: 16mb max: 3067mb

Hope this helps?
Reply #14 from Sins Forums Top
ewww, set the min and max to like 3500
Reply #15 from Sins Forums Top

ewww, set the min and max to like 3500


1500 should be more then sufficient, 3500 being overkill by a long shot IMO. In any event keep min/max the same.
Reply #16 from Sins Forums Top
if hes getting errors, id go overkill ^.^
Reply #17 from Sins Forums Top

Right, according to vista my page file is at 2345mb (auto manage)

min: 16mb max: 3067mb

Hope this helps?


Even for vista, a page file of 2345 MB's is overkill. As in you have a lot of junk running in the background, try running in a clean boot. (Unless that means that its allocated that amount, but isn't using it... I don't know enough about vista to point you to the exact spot I need).
Reply #18 from Sins Forums Top
really? this is a fresh install of vista. I even turned off sidebar, it still has the default wallpaper!

It has msn messenger and google talk, stardock central and sins installed, thats it, yes i have not installed any AV yet

I will check again when I get home. Im thinking of installing XP again
Reply #19 from Sins Forums Top


Right, according to vista my page file is at 2345mb (auto manage)

min: 16mb max: 3067mb

Hope this helps?


Even for vista, a page file of 2345 MB's is overkill. As in you have a lot of junk running in the background, try running in a clean boot. (Unless that means that its allocated that amount, but isn't using it... I don't know enough about vista to point you to the exact spot I need).


That should be the allocated value (and is relatively normal -- mine's hovering just over 2 gigs) -- checking the performance tab of the task manager should get you the used value, I believe.


Reply #20 from Sins Forums Top
Try these link that Massgate has posted for folks with Vista problems.

http://www.massgate.net/read.php?28004,29632

I'm running Vista 64bit, and sins has been working before I used the above MS KB fix/patches. Though I did have problems running single player World in Conflict, the above actually helped fix it.

You mentioned that Vista told you that it has recovered from something something etc. One of the fix in the above link talks about that.


Honestly, Vista has a LOT of small problems that appears here and there to certain hardware setup. MS seams to be releasing fixes within the KnowledgeBase support as patches. Hopefully when the 1st SP for Vista comes out, a lot of these annoying problems will be fixed.

BTW I'm running:

Vista 64
4GB ram
7950 nvidia gfx card just like you (I think mine is made by asus)
Creative X-FI Platnium sound card. (using their sound drivers from may 2007 and using the latest alchemy.

Also using the latest nvidia drivers as mentioned above too. However, sin DID run fine (single beta before beta3) with previous gfx drivers.

I've had the recovered from driver error msg for awhile. I think (can't remember for sure) I fixed it with one of the MS KB patch before I read the above massgate post. I guess I found it via googling earlier at another time.

Good luck!