crashed with the most recent patch
 

ATI5870 10.8 driver

Getting game freezes. Had two last night on ATAG server. Can't be sure if I git them during the beta(version2).

Sometimes the crash file is empty but I'm attaching one from last night which created 4 files! plus two more from last night and one from the night before.

I did then re-run the .NET redist as someone suggested. No freezes after that but I was only on for one hour - will edit here if more crashes.

By the way I sometimes notice it freezes, or it seems to happen, when I change from FoV 90 to 30 or back (direct stick switch input) whilst pressing TS3 transmit key F12. Could be co-incidence.

Im getting Launcher.exe crashes.

My crash files
 

Always happens when online, have lots of memory

S!

Getting launcher.exe crashes online only. Mainly playing on ATAG server. But the files are 0kb..

If the files are empty, (0kb) enable logkeep in conf.ini file.

Quick mission, Allied column attack: crashes when I get on 109's 6 o'clock.

LINK (right click, save as)

Specs / drivers from the sig.

Here are some crash dump files from me post the new final patch. I Get regularily game freezes after like 30-45 min gameplay in multiplayer.

http://www.mediafire.com/download.php?3656y9e1j0pwf87

Hope this gets sorted soon.

Winger

Thought to be left untroubled by it, but well...

After 10-30 minutes of flight in multiplayer I often get a total freeze. Hope the crash dump will help to iron it out ;)

http://www.sowskins.com/crashdump/22...2_5668_187.dmp

System specs beyond sig. Thanks.

edit:
My experiences are that I only get launcher freezes on servers with full realism settings. On arcade servers I didn't get any servers so far. Can it be?

I have also experienced the online crash after 20-30 minutes twice (have only had time to fly online twice on the new patch so 100% there). I have mailed the dmp-files with a detailed description to Ilya - but I did notice one interesting thing before killing "launcher.exe" the last time... The 32-bit process took 3Gb of memory. That should be "against the wall" even if it's compiled to be large address aware. Feels like a memory leak to me as an old C++ programmer...

Anyone else that has noticed this?

By the way, I had 20 dmp-files from the same minute it crashed the last time.