I have 768mb ram and it happens to me.

I was just going to post about this. I can run a large bomber mission for 10 or 15 minutes than it begans to chug and then stop. I wait, and it starts going again like it gets a secound breath. I was going to buy more memory but sounds like it is something in the program.

Hey sitzkrieg I am from CR also, email me at rcwarbirds@earthlink.net

This is an excellent thread. I will try to help keep it bumped so we can build up a substantial voice. I'm sure that the Maddox team will have lots of things on their plate, so it might be a challenge to be heard.

1 GB of 1066 RdRam Page file locked to 768 Mb I'm 10 missions into the Finn campaign flying the Brewsters and have had 0 problems that have been described here.

Not bragging or trying to be a hero just adding my 2c for comparison.

Only issue I've had with FB was a hard lock when I enabled the mirror in the Hurri (Hard lock to the point of having to press "reset" something of a first for XP since I've had it)

More RAM definitly reduces the chance of that happening. I posted it in Oleg's RR to make sure he sees it. I'll reference this thread there. Thanks for the screenshot, that will be most helpfull for Oleg.

WB: I was just going to post about this. I can run a large bomber mission for 10 or 15 minutes than it begans to chug and then stop. I wait, and it starts going again like it gets a secound breath. I was going to buy more memory but sounds like it is something in the program

RS there's two separate problems in this thread - the memory error that's been well flagged; and the one that Warbird mentions above... 'getting a second breath' describes it exactly

I'm getting a screen freeze offline for many seconds sometimes and then it returns to normal. It's not a loading pause and there's no chugging at all before it happens

I'm on 1GB DDR, I've seen this a few times online too

Bit worrying this

Ming

Could well be connected. Sitzkriegs explanation about a pointer to a protected memory area sounds good, but it does not explain why the programm would start slide show before the error message comes up.

It got to be some form of memory leak. Sometimes pausing a programm will clear up memory it uses, allowing it to run fluently again. It seems also possiple that when the programm starts to chug around, either your OS or the programm itself try to get more memory free - maybe some computers are clever enough to free up more RAM before the error comes up - result is that you see chucking and stuttering but never crash.

I forgot to mention that when my game starts to slide show after a couple minutes of intense action the hard drive light starts blinking and sometimes stays on untill that "secound breath".


I see this in my Henkle quick mission with full load of bombers and fighters. Things are smooth untill the bombs start to explode and the anti air gets heavy. Frame rates fall, as to be expected with all the graphic intensity of a full bombing raid with fighters attacking the bombers and bombs going off and planes burning and crashing. But not expected is what happens next. The slide show gets very slow and then stops and the hard drive light stays on. The first time this happened I thought the game froze, but no, it did start up again. Not perfect but running just the same.

I do not get an error notice, but I think I have error notices turned off in services.

XP Pro S1
Barton 2500
A7NX8 Asus Nforce 2 MB
512 DDR Ram
ATI 9700 Pro
Soundstorm
Squirl in cage running very fast (tweaked of course)

Paul
http://www.rcwarbirds.com

I've tried all sorts of memory and system tweaks myself (I have 1 gig of PC2100DDR ram BTW) and I'm still getting these CTDs after some stuttering. All my other games and apps run fine with no memory errors.

Based on reading peoples posts it seems this effects a wide variety of users, even those with high end system specs. But the strange thing is , as someone pointed out, it doesn't effect everyone. So there has to be some sort of system combo that the game doesn't like. This is a matter that Oleg's programmers must look into for the first patch.

-Krypto

Seeing this happen to people with 1 gig DDR certainly means it has nothing to do with hardware specs. It might be related to OS, though.