DokiDoki
Nov 12 2009, 03:35
Up to the Manhattan mission I gotten through all the missions with only 2 crashes in hours of gametime.
I also did some random scenarios, fooled around a bit in the Armory, no crashes.
This was with video memory on default (something I couldnt do before) and Hyperthreading on (which I had to turn off before, more on that soon).
I could even set the view distance up to 7,8KM and have still a smooth game. 10KM is even possible, just still a bit slow and I'd rather have a bit extra FPS (what a joy to fly helos with that in Armory though :)).
Before I had it set to 4KM to keep the memory from overflowing.
Now came the Manhattan mission. A few minutes into it and the first crash came. Restarted, played a few minutes -> crash.
Rebooted, turned Hyperthreading off again. Very low FPS suddenly in that mission. Turned the view distance down to 3KM, didnt help. Turned it down more to 1.6, also did nothing to get up the FPS.
Played on a bit with that and gotten a crash again after a few minutes.
Turned Hyperthreading on again and FPS is good again but still crashes every few minutes.
The crashes are seemingly random but only in this mission. It can happen when I save, open map, or just walk or drive around.
In the capture Chernorosk mission I used to have the memory overflow very quickly, now not anymore, played perfectly with 7.8 KM view distance, so I dont think its that.
Using the same workarounds I used to use (setting video mem to very high and view distance to 4KM) also does not work, so Im not sure what the problem here is now.
Hyperthreading used to be a problem through all of the game and turning it off helped a lot. Now turning it off utterly kills my FPS.
Im now saving my way through the crashes in the Manhattan mission to see what happens in the Bitter Chill mission.
My PC:
I7 860 2.80GHz
Geforce GTX275 using 191.07 drivers.
6 GB DDR3
Windows 7 home premium 64 bit
TrackIR5 (dont think that matters in any way, I tried the game without it already.)
I know this system has the potential to give trouble with this game. I had namely a lot. My old PC which is a lot less fast ran the game a lot more stable.
Now up to the Manhattan mission ArmA II is PERFECT, cant get better. This here is now the only culprit. And I love the campaign here :).
All in all still a very good development with this latest betas in the last few days and keep up the good work.
EDIT: Ok, after some time I could not save at all anymore. Either it crashed or said it saved but didnt (???). Restarted the mission, at first ran very well, then started crashing again. Tested after that some scenarios and these run fine. Weird. Gonna play these and some MP for now as theres so more to ArmA 2 than only the campaign :).
I also did some random scenarios, fooled around a bit in the Armory, no crashes.
This was with video memory on default (something I couldnt do before) and Hyperthreading on (which I had to turn off before, more on that soon).
I could even set the view distance up to 7,8KM and have still a smooth game. 10KM is even possible, just still a bit slow and I'd rather have a bit extra FPS (what a joy to fly helos with that in Armory though :)).
Before I had it set to 4KM to keep the memory from overflowing.
Now came the Manhattan mission. A few minutes into it and the first crash came. Restarted, played a few minutes -> crash.
Rebooted, turned Hyperthreading off again. Very low FPS suddenly in that mission. Turned the view distance down to 3KM, didnt help. Turned it down more to 1.6, also did nothing to get up the FPS.
Played on a bit with that and gotten a crash again after a few minutes.
Turned Hyperthreading on again and FPS is good again but still crashes every few minutes.
The crashes are seemingly random but only in this mission. It can happen when I save, open map, or just walk or drive around.
In the capture Chernorosk mission I used to have the memory overflow very quickly, now not anymore, played perfectly with 7.8 KM view distance, so I dont think its that.
Using the same workarounds I used to use (setting video mem to very high and view distance to 4KM) also does not work, so Im not sure what the problem here is now.
Hyperthreading used to be a problem through all of the game and turning it off helped a lot. Now turning it off utterly kills my FPS.
Im now saving my way through the crashes in the Manhattan mission to see what happens in the Bitter Chill mission.
My PC:
I7 860 2.80GHz
Geforce GTX275 using 191.07 drivers.
6 GB DDR3
Windows 7 home premium 64 bit
TrackIR5 (dont think that matters in any way, I tried the game without it already.)
I know this system has the potential to give trouble with this game. I had namely a lot. My old PC which is a lot less fast ran the game a lot more stable.
Now up to the Manhattan mission ArmA II is PERFECT, cant get better. This here is now the only culprit. And I love the campaign here :).
All in all still a very good development with this latest betas in the last few days and keep up the good work.
EDIT: Ok, after some time I could not save at all anymore. Either it crashed or said it saved but didnt (???). Restarted the mission, at first ran very well, then started crashing again. Tested after that some scenarios and these run fine. Weird. Gonna play these and some MP for now as theres so more to ArmA 2 than only the campaign :).