|
Your donations keep RPGWatch running!
I am crashing all the time now
October 30th, 2006, 16:12
Patch 2, always the SmartHeap Library.
The memsave tool saves me most of the times but only when I save, not when I crash while playing.
It seems certain areas are more sensitive for me. Two of them is Vengard and the area around Faring+Gotha.
A teleport or quicksave here is almost guaranteed to crash in 50% of the cases.
I wouldnt say it's my computer that is limited. I have a 4800+ A64 dualcore, 2x7900GTX/512mb, 2gb 2-2-2-5 high quality ram and run the game on a 7200rpm SATA drive with 16mb cache.
The memsave tool saves me most of the times but only when I save, not when I crash while playing.
It seems certain areas are more sensitive for me. Two of them is Vengard and the area around Faring+Gotha.
A teleport or quicksave here is almost guaranteed to crash in 50% of the cases.
I wouldnt say it's my computer that is limited. I have a 4800+ A64 dualcore, 2x7900GTX/512mb, 2gb 2-2-2-5 high quality ram and run the game on a 7200rpm SATA drive with 16mb cache.
October 30th, 2006, 16:48
Have you set the Ressource Cash to middle? I´ve heard that helps with the memory-bug. It might even be good to try to set it to low directly before you try to save.
This special bug occurs mainly on fast systems with a lot of ram, I don´t know why.
This special bug occurs mainly on fast systems with a lot of ram, I don´t know why.
October 30th, 2006, 17:36
I changed it to medium now. I let you guys know if it improves anything.
October 30th, 2006, 17:53
Just crashed on medium setting, changed it to low. Will tell you if I still crash.
October 30th, 2006, 17:55
Set the Resource Cache and the Texture Details to middle.
Try not to save near overcrowded places or direct after a teleport.
Try not to save near overcrowded places or direct after a teleport.
October 30th, 2006, 18:14
Are you overclocking? If so maybe you should try loosening those RAM timings just as a test?
--
"For Innos!"
"For Innos!"
October 30th, 2006, 18:39
I have not overclocked, but I run XFX cards that is overclocked out-of-the-box. I do not know how much I am supposed to "clock them down". I was coolbits junkie back around GeForce1, but now I have a rig that pretty much handles anything so I might be able to clock it down if I knew how much.
October 30th, 2006, 18:41
I ran through the G3 tweak guide. I had already done most of it but I found some new stuff. Maybe it helps.
October 30th, 2006, 18:46
Sounds like your having problems due to Distance settings and never set your cache to low, well imo. 
Try everything on medium then if it still causes problems and crashes, then lower Detail Distance to low, since you said Vanguard its the Forcefield doing it I would bet.
The other killer is Texture detail but if you put that to Low it maybe a shock since it really looks worst than G2.
Object Detail is the Distance at which Items/Objects are drawn, iir.
Post Process I wouldn't turn it on past Bloom just to get rid of that Flashing White light.

Try everything on medium then if it still causes problems and crashes, then lower Detail Distance to low, since you said Vanguard its the Forcefield doing it I would bet.
The other killer is Texture detail but if you put that to Low it maybe a shock since it really looks worst than G2.

Object Detail is the Distance at which Items/Objects are drawn, iir.
Post Process I wouldn't turn it on past Bloom just to get rid of that Flashing White light.
SasqWatch
October 30th, 2006, 18:52
Try disabling SLI and running one card as a test. I know some Crossfire folks have attributed instability to their dual setups. Have you verified your SLI? What does FRAPS say?
As an aside - probably the best suggestion is to put the game in the closet for 3-4 months.
As an aside - probably the best suggestion is to put the game in the closet for 3-4 months.
--
"For Innos!"
"For Innos!"
October 30th, 2006, 22:52
Originally Posted by AcleaciusThere are alot of options here… what options exactly is "Detail Distance"?
Sounds like your having problems due to Distance settings and never set your cache to low, well imo.
Try everything on medium then if it still causes problems and crashes, then lower Detail Distance to low, since you said Vanguard its the Forcefield doing it I would bet.
The other killer is Texture detail but if you put that to Low it maybe a shock since it really looks worst than G2.
Object Detail is the Distance at which Items/Objects are drawn, iir.
Post Process I wouldn't turn it on past Bloom just to get rid of that Flashing White light.
October 30th, 2006, 22:53
Originally Posted by ToddMcF2002Disabling SLI is pretty much a nono anyway. It drops my FPS with 40%.
Try disabling SLI and running one card as a test. I know some Crossfire folks have attributed instability to their dual setups. Have you verified your SLI? What does FRAPS say?
As an aside - probably the best suggestion is to put the game in the closet for 3-4 months.
I intend to finish the game in the next 3-4 days if I can.
October 30th, 2006, 23:05
For some reason the Eddie Murphy song "My Girl wants to party all the time" sprang into my head.
"my game keeps
crashing all the time!
crashing all the time!
crashing all the tiiimmmeee!"
I know that's weak but hey man, true story.
"my game keeps
crashing all the time!
crashing all the time!
crashing all the tiiimmmeee!"
I know that's weak but hey man, true story.
--
"For Innos!"
"For Innos!"
October 30th, 2006, 23:07

I have reached the point where I cannot quicksave without a crash or quickload without a crash.
October 30th, 2006, 23:19
--
"For Innos!"
"For Innos!"
October 30th, 2006, 23:59
Thing is, that my PSU is "only" 550 watt, and I ordered a 650 watt yesterday. Will probably be delivered tomorrow. I doubt that have anything to do with the memory problems though.
October 31st, 2006, 01:22
Distance Draws are the Top two, Detail Settings you will need to click on Custom, if the Medium Settings didn't work and Object Detail is the thrid from the top.
It will be understandable once you click on Custom, I am guessing.
It will be understandable once you click on Custom, I am guessing.
SasqWatch
October 31st, 2006, 04:12
Doesn't sound like a classic "memory leak" issue, sounds more like a hardware-one-of-your-ram-pieces-are-dead problem. Either that or a strange compatibility issue, or some weird bug that occurs if you have components A, B, C and D working in a special order.
SasqWatch
Original Sin Donor
|
|
All times are GMT +2. The time now is 03:30.



