weird crash

posted on October 3rd, 2011, 2:14 pm

i've been playing FO for a while now but i've not had this problem before. I'll be playing instant action on Nirvana II and suddenly on the minimap the asteriods would disappear, shortly after the game would crash. Now I can pause and resume the game and that brings the asteriods back but any idea whats going on?

posted on October 3rd, 2011, 3:07 pm

hard to tell. in very long games it can happen that textures fill up the whole available game memory and make the game instable as no more memory is available. as workaround when you see such error occur, switch to the escape menu and then resume the game. the texture cache will be flushed.
the upcoming FO version introduces some engine enhancements to improve memory usage

posted on October 3rd, 2011, 3:16 pm

ok

posted on October 4th, 2011, 1:31 am

Interesting. TUN just reported to me yesterday he is getting a very similar issue with his beta version of Sigma (which has a loooot of weapons in use), and the minimap actually completely disappears as well.

posted on October 4th, 2011, 2:49 am

i do tend to play against seven Merciless AI on unlimited resources, could it be an overload of textures and weapons fire?

posted on October 4th, 2011, 1:37 pm

hard to tell. in very long games it can happen that textures fill up the whole available game memory and make the game instable as no more memory is available. as workaround when you see such error occur, switch to the escape menu and then resume the game. the texture cache will be flushed.
the upcoming FO version introduces some engine enhancements to improve memory usage

OOOH does that mean no more Out of memory errors? 

posted on October 4th, 2011, 3:25 pm

that the minimap disappears is the result of clearing the textures cache. that is the last line of defense before an out of memory error occurs.

OOOH does that mean no more Out of memory errors? 

atleast there will be a lot more capacity before such errors appear. more optimizations are planned.
in case you use a nocd patch, make sure you don't have replaced the "armada2.exe" when applying a nocd patch. the "armada2.ldl" file should be replaced.
armada2.exe supplied by fleet operations sets a flag that allows armada to use 3gb of ram instead of being limited to 2gb.

posted on October 4th, 2011, 8:39 pm

I use and ISO, would that affect anything? I only have the issue on my other systems as my primary rig has 8 gigs so its a non issue. However my other systems are running 2 gigs and one is at 1 gig and have the problem. I suppose I could just throw in another gig in each. Does FLOPS use any more then 3gigs?

posted on October 4th, 2011, 8:51 pm

I use and ISO, would that affect anything?

While I am not DOCa, I think (from my personal experience) it wouldn't.

posted on October 5th, 2011, 8:39 am

Correct, ISO is ok