IL-2 Random Crashes,ATI video card
 

I have had soem random crashes since doing a computer rebuild
I am using a newer ATI driver than before.It will crash to desktop while playing for 10minutes or 3 hours,its just random.I do have an error file in Il-2 that says this


An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x696621f7
Function name=(N/A)
Library=C:\Windows\system32\atioglxx.dll

NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to release documentation for possible
reason and solutions.



Current Java thread:
at com.maddox.il2.engine.Renders.PostPreRenders(Nativ e Method)
at com.maddox.il2.engine.Renders.doPaint(Renders.java :346)
at com.maddox.il2.engine.Renders.paint(Renders.java:2 53)
at com.maddox.il2.engine.RendersTicker.msgTimeOut(Ren ders.java:637)
at com.maddox.rts.MsgTimeOut.invokeListener(MsgTimeOu t.java:73)
at com.maddox.rts.Message._send(Message.java:1217)
at com.maddox.rts.Message.sendToObject(Message.java:1 191)
at com.maddox.rts.Message.sendTo(Message.java:1134)
at com.maddox.rts.Message.trySend(Message.java:1115)
at com.maddox.rts.Time.loopMessages(Time.java:252)
at com.maddox.rts.RTSConf.loopMsgs(RTSConf.java:100)
at com.maddox.il2.game.MainWin3D.loopApp(MainWin3D.ja va:131)
at com.maddox.il2.game.Main.exec(Main.java:436)
at com.maddox.il2.game.GameWin3D.main(GameWin3D.java: 235)

Dynamic libraries:
0x00400000 - 0x0049A000 C:\1946\il2fb.exe
0x770E0000 - 0x77260000 C:\Windows\SysWOW64\ntdll.dll
0x751D0000 - 0x752D0000 C:\Windows\syswow64\kernel32.dll
0x766E0000 - 0x76724000 C:\Windows\syswow64\KERNELBASE.dll
0x74F70000 - 0x75070000 C:\Windows\syswow64\USER32.dll
0x76AF0000 - 0x76B80000 C:\Windows\syswow64\GDI32.dll
0x75510000 - 0x7551A000 C:\Windows\syswow64\LPK.dll
0x76930000 - 0x769CD000 C:\Windows\syswow64\USP10.dll
0x76630000 - 0x766DC000 C:\Windows\syswow64\msvcrt.dll
0x75570000 - 0x75610000 C:\Windows\syswow64\ADVAPI32.dll
0x762F0000 - 0x76309000 C:\Windows\SysWOW64\sechost.dll
0x76730000 - 0x76820000 C:\Windows\syswow64\RPCRT4.dll
0x74C50000 - 0x74CB0000 C:\Windows\syswow64\SspiCli.dll
0x74C40000 - 0x74C4C000 C:\Windows\syswow64\CRYPTBASE.dll
0x74A50000 - 0x74A82000 C:\Windows\system32\WINMM.dll
0x76A90000 - 0x76AF0000 C:\Windows\syswow64\IMM32.dll
0x76550000 - 0x7661C000 C:\Windows\syswow64\MSCTF.dll
0x72D20000 - 0x72D45000 C:\Windows\system32\DINPUT.dll
0x66260000 - 0x66288000 c:\progra~2\citrix\system32\mfaphook.dll
0x679A0000 - 0x679FD000 C:\Program Files (x86)\Citrix\system32\CtxSbxHook.DLL
0x6D420000 - 0x6D4EF000 C:\1946\bin\hotspot\jvm.dll
0x733E0000 - 0x7342B000 C:\Windows\system32\apphelp.dll
0x6D220000 - 0x6D227000 C:\1946\bin\hpi.dll
0x6D3B0000 - 0x6D3BD000 C:\1946\bin\verify.dll
0x6D250000 - 0x6D266000 C:\1946\bin\java.dll
0x6D3C0000 - 0x6D3CD000 C:\1946\bin\zip.dll
0x0CFD0000 - 0x0D012000 C:\1946\wrapper.dll
0x76820000 - 0x768AF000 C:\Windows\syswow64\OLEAUT32.DLL
0x75070000 - 0x751CB000 C:\Windows\syswow64\ole32.dll
0x10000000 - 0x1000A000 C:\1946\pathfind.dll
0x10010000 - 0x12EE9000 C:\1946\il2_corep4.dll
0x7C340000 - 0x7C396000 C:\1946\MSVCR71.dll
0x01FD0000 - 0x01FF3000 C:\1946\jgl.dll
0x0E300000 - 0x0E33A000 C:\1946\il2_usgs2.dll
0x75390000 - 0x753C5000 C:\Windows\syswow64\WS2_32.dll
0x76620000 - 0x76626000 C:\Windows\syswow64\NSI.dll
0x0ED00000 - 0x0ED71000 C:\1946\mg_snd_sse.dll
0x74960000 - 0x74990000 C:\Windows\system32\dinput8.dll
0x73430000 - 0x73439000 C:\Windows\system32\HID.DLL
0x74DD0000 - 0x74F6D000 C:\Windows\syswow64\SETUPAPI.DLL
0x76A60000 - 0x76A87000 C:\Windows\syswow64\CFGMGR32.dll
0x75370000 - 0x75382000 C:\Windows\syswow64\DEVOBJ.dll
0x76320000 - 0x7634D000 C:\Windows\syswow64\WINTRUST.dll
0x74CB0000 - 0x74DCC000 C:\Windows\syswow64\CRYPT32.dll
0x770B0000 - 0x770BC000 C:\Windows\syswow64\MSASN1.dll
0x71FD0000 - 0x72050000 C:\Windows\system32\uxtheme.dll
0x6D340000 - 0x6D348000 C:\1946\bin\net.dll
0x742B0000 - 0x742B7000 C:\Windows\system32\WSOCK32.dll
0x73B50000 - 0x73B60000 C:\Windows\system32\NLAapi.dll
0x73AE0000 - 0x73B1C000 C:\Windows\System32\mswsock.dll
0x73A70000 - 0x73AB4000 C:\Windows\system32\DNSAPI.dll
0x729C0000 - 0x729C8000 C:\Windows\System32\winrnr.dll
0x729B0000 - 0x729C0000 C:\Windows\system32\napinsp.dll
0x72990000 - 0x729A2000 C:\Windows\system32\pnrpnsp.dll
0x73AD0000 - 0x73AD5000 C:\Windows\System32\wshtcpip.dll
0x6E180000 - 0x6E248000 C:\Windows\system32\Opengl32.dll
0x72D50000 - 0x72D72000 C:\Windows\system32\GLU32.dll
0x70BA0000 - 0x70C87000 C:\Windows\system32\DDRAW.dll
0x72CF0000 - 0x72CF6000 C:\Windows\system32\DCIMAN32.dll
0x720B0000 - 0x720C3000 C:\Windows\system32\dwmapi.dll
0x69030000 - 0x69B89000 C:\Windows\system32\atioglxx.dll
0x747A0000 - 0x747A9000 C:\Windows\system32\VERSION.dll
0x0FE90000 - 0x0FEBD000 C:\Windows\system32\atiadlxy.dll
0x13240000 - 0x13247000 C:\Program Files (x86)\NaturalPoint\TrackIR4\NPClient.dll
0x74A90000 - 0x74B02000 C:\Windows\system32\dsound.dll
0x74A20000 - 0x74A45000 C:\Windows\system32\POWRPROF.dll
0x769D0000 - 0x76A53000 C:\Windows\syswow64\CLBCatQ.DLL
0x72FE0000 - 0x73019000 C:\Windows\System32\MMDevApi.dll
0x71D20000 - 0x71E15000 C:\Windows\System32\PROPSYS.dll
0x752D0000 - 0x75327000 C:\Windows\syswow64\SHLWAPI.dll
0x72FA0000 - 0x72FD6000 C:\Windows\system32\AUDIOSES.DLL
0x72F60000 - 0x72F6C000 C:\Windows\SysWOW64\pid.dll
0x749B0000 - 0x749B7000 C:\Windows\system32\avrt.dll
0x73C30000 - 0x73C4C000 C:\Windows\system32\IPHLPAPI.DLL
0x743E0000 - 0x743E7000 C:\Windows\system32\WINNSI.DLL
0x73A20000 - 0x73A58000 C:\Windows\System32\fwpuclnt.dll
0x73A60000 - 0x73A66000 C:\Windows\system32\rasadhlp.dll
0x72F70000 - 0x72FA0000 C:\Windows\system32\wdmaud.drv
0x74950000 - 0x74954000 C:\Windows\system32\ksuser.dll
0x74940000 - 0x74948000 C:\Windows\system32\msacm32.drv
0x74990000 - 0x749A4000 C:\Windows\system32\MSACM32.dll
0x74910000 - 0x74917000 C:\Windows\system32\midimap.dll
0x75330000 - 0x75335000 C:\Windows\syswow64\PSAPI.DLL

Local Time = Wed Aug 26 00:15:33 2009
Elapsed Time = 5184
#
# The exception above was detected in native code outside the VM
#
# Java VM: Java HotSpot(TM) Client VM (1.3.1-b24 compiled mode)
#
Anyone know what the heck this means,Thanks for any info
I did change the ATI driver back to 9.7 was runnign 9.8,i originally had 9.5 i think with no problems,im running windows 7

Same here in win7 x64 and 4870...will go back to 9.7.
The crash to desktop happens when i'm in FMB.

~S~

There's a problem with OGL in the latest ATI drivers.

with me it happens with 9.8's.Not so much but also happens with 9.7's.I try and go back to the original ones i had,i think they were 9.5"s.I dont like the new control panel anyway

Weird
 

Yeah usually I got back to another driver.

I remember the old school diamond stealth would only work for games with its beta drivers.

My friend has ATI card, and it hates IL-2. He swapped it for a Nvidia, and it works fine.

My 256 ATI won't run ROF, but my Nvidia will.


My X1650 I had to get certain driver for IL-2 to work.


Lets just say for my next PC build, its going to have Nvidia SLI or PCIe . . .

Do you remember which driver you used? Maybe it could help me.

____

The 7.11 cat was the best for the older cards IIRC

x1950 pro
x1650

Does anyone have any idea which Ati drivers are best for more modern cards? I mean, in respect to the gunfiring graphical glitches, and Open GL compatibility?

Guys, i am using x1950 Pro and really need to know best Catalys settings pls. Thanks...

I have a 4890 and was experiencing all the bad effects like artefacts, blue lighting and worst of all, the FMB crashing! I just went back to the Catalyst 9.5s and everything is just fine.

B

The gunfire artifact goes way back. I was getting the gunfire artifacts on a HD 3850. Before that I was using an x1550, and that was clear of that problem, not half so powerful graphically, but the gunfire artifact didn't show up once. It may well be that on the 3850 I was using a later driver, and earlier 3850 drivers didn't do it, but I don't have any way of knowing about that. All my recent Radeons have been Sapphires, including the x1550, if they don't work with standard Ati drivers, they certainly used to.

Listen guys after 10 years with ATI I have given up, I bought a NVIDIA EVGA GTX 260cor 216 896M ddr3 PCIE for $137.00. http://www.geeks.com/details.asp?inv...VCD&cpc=VCDbsc

IL2 looks even more stuinning with NVIDIA...

and Im getting any where upwards from 40FPS to over 100FPS!!!Everything is maxed!!!

My sugestion drop the ATI cards they sux...

It isn't that simple. I have a crossfire motherboard, I can get a second card that takes me past almost any GF for £120, to beat that combination in a single Geforce card would cost £380. My motherboard doesn't do SLI, and two cards wouldn't be as cheap as one even if it did.

I do like the idea of Ati and AMD as underdogs united. Other than that, I'm slowly coming around to the view that where Open GL in games is concerned, you may have a point.

Thats ok I have the P5WDHdelux its a mobo crossfire set-up, I can run SLI on it no problem. I had 2 x HD 3870's running in crossfire and they would only get 40fps in IL2 4.09mb1 max'ed out...

SLI is ran through your cards, the mobo crossfire is only for the ATI cards that don't need the bridge, the HD 3870's and above that need the bridge use only the ATI CCC crossfire set up enabled... Don't be fooled into think just because it states crossfire Mobo it just means it can be bridged through the Mobo..

Well, I think Alpha was right when he said that the latest couple of Catalyst versions have a problem with OpenGL, at least as far as this old game is concerned. I flew online for a few hours last night, using the 9.5s, and never saw a single problem.

If we're gonna get into product fanaticism - here's a BD score from this driver set - Frames: 10200 - Time: 150000ms - Avg: 68.000 - Min: 26 - Max: 159

That's also with 'maxed-out' settings; I don't think I'm going to junk my Radeon quite yet ;)

B

sorry this is late


I kept posting and the weaksauce login timeout arrgh . . .


Notepad FTW.



anycase I was using 8.4 driver, it was a CD driver. I have other CD's for other 2 ATI's (they were giving them away from work for free) I got.

It worked with IL-2. I tried 8.2 and 8.6 and those work also but the 8.4 works for some other games.

The next part is kinda long, so if your part of the TLDR crowd, its optional.





---



---



My experience with ATI / AMD

ATI has been a flipping hassle. Before IL-2 became the only game I play.

I had to set up 3 different boots of XP w/ different ATI drivers. One was for FPS / Half Life 2. Another was for MMO / RPG's. World of warcrack, mass effect, knights of the old republic, lord of the rings online. The final was IL-2. I had to tweak the card settings.

Then I got one nvidia to play them all. And it was straight out of the box.

I was cleaning out my old pentium 90 mhz and saw my notes for the diamond steath card incident and began to experiment w/ the ATI again and found the 8.4 works.

But 8.4 doesn't like Knights of Old republic or Lord of the rings.




I used to love AMD / ATI. They were cheap and AMD was even faster (at the same price). Then the multi core AMD fiasco came, and they bought out ATI, and the quality went down on both fronts

AMD / ATI are more finicky. A year ago at work, this new hire, a ambitious prick type of coworker tell me he could do our inventory management cheaper.

So the boss fell for his pitch and he bought 100 ATI cards and AMD chipsets. He builds them using the cpu fans and PSU's we used for our normal builds (intel based). I told him he'd need a new PSU wattages and better cooler fans.

I told the boss the new machines would have issues and we didn't test ATI's with the graphics programs.

The AMD's keep crashing due to heat and low wattage. One even cooks the motherboard. ATI's work fine except for our graphic designer / architect depts, so eventually I find a driver that works.

The guy didn't even do one build to test (Normally we research a build, then build one, run it for a year or six mo's, then order sets of 100).

So boss goes back to our usual builds. He Ebays + gives away some to IT the ATI + AMD sets, fires the new guy. Then he busts a Goering on Galland and lets me go for not warning him and for conspiring to get IT to get free goods.

yay economy

That suxs I would have taken him to court... And taken his job...Gone over his head with the owners...

Same problem here
 

:( I have two brand new HD4890's (crossfire'd) and am equally shagrined to find that I have the same CTD problem with IL-2 that others report. I'm using Win 7 RC, so I thought it was with windows or an overclock problem. But, apparently not so. It seems whenever I play online in a COOP with my squadies, I CTD within 10-15 mins of game time. I've tried Catalyst 9.8 and 9.9 drivers and have experienced the problem with regularity when using OpenGL. Doesn't matter whether it's 'perfect mode' in graphics or not. OpenGL use in IL-2 = CTDs. Oddly, I can't replicate the problem as easily with offline play, but have seen it happen. I also noted the ati0glxx.dll issue in the event log and loaded an internet found-copy (2004 version) of that file in the windows/system32 folder, but it did not fix the problem. I understand from other forums that this is thought to be a memory leak with the current drivers and earlier versions might work OK with IL-2. I've backed-out to Catalyst version 9.6, but haven't tested it just yet. I logged my situation at the ATI tech forums and recommend others do the same. Suggest others do the same. I'm kind'a forced into using this card(s) until DX11 cards come out. If ATI doesn't give me satisfaction in the next 30 days with a fix, I'll pull the plug on ATI and when the DX11 cards for NVidia come out. I'm a patient person, but this problem should have been fixed by now as it's been known since late July, so this is completely unsatisfactory to me. As a series IL-2 is quite old now, but as a game it is still the premier online combat sim. What's ATI's problem. Have they just given up on this sim to NVidia?

Related link: http://forums.amd.com/game/messagevi...eyword1=IL%2D2

Thxz for reporting/posting this :)

I tried the 4GB patcher and Catalyst 9.10, neither cured the OpenGL memory leak/CTD problem for me. I seem to get the problem in high particle (explosions, smoke) situations. I've never had it with a dogfight server, only in COOPs with lots of action. I've also posted the problem as feedback at AMD's web site and noticed that the automated form doesn't even include IL-2 as a game listed on their form's pick list. That must be telling me something.

I'm installing Win 7 today and I am seriously considering buying an Nvidia card (prior to) so that my fresh install can be sans ATI. I'm about fed up with this problem. I've given ATI plenty of time to fix it. Too much in my view. :evil:

Here's to hoping. I'm running 2x4850 in CF on Win 7 x64, and had intermittent CTDs (like once or twice a month, but I'm flying 2 nights a week on average). Will try this and we'll see...

I have an ATI 4870.

The dlls worked for me for a while, but last night I started CTD again. Can't figure out why it suddenly started again.

So I uninstalled cat. 9.10 and went back to 9.5 (which is the last version I had before bumping up to 9.9 in September or so).

*sigh*

Same here.
All my squadron pilots with 4870 have CTD everytime, not solution disabling catalyst or with different .dll. We are going back to 9.5.

Yep, I can confirm, dll's don't help. I'll try 9.5... or alternately take atioglxx.dll from 9.5 and stick it into the Il2 folder, see what happens.

EDIT: 9.5 drivers don't crash, but invariably produce artifacts. This sucks. I'll just buy nVidia for the time being and sell of both 4850s...

Not sure if anyone has tried the 9.11's but I was getting graphics corruption once IL-2 loads the landscape (actually the game itself renders fine, the text gets all messed up as well as ui colours).

Anyways my solution was to drop the atioglxx.dll into the IL-2 directory. I'm using 9.9's atm and they seem decent.

Dropping in the 9.9 dll makes it easier as well since you can still use the latest drivers for all your other games.

Hopefully it's okay to attach the dll here. It's freely available at ATI's website. I've just pulled the dll out to make it easier for anyone who needs it.

This is the 64bit Win Vista/7 driver.

I'm on 9.11.

I'm testing what youre saying by dropping it in the main folder of IL2....
Hope it works.....:rolleyes:

If ATI fixes opengl in the next release just remember to delete or rename that file in the IL-2 directory so that it'll use the system default again.

With that dll in my IL2 folder my game refuses to launch.
Have tried all kinds of drivers since getting this 4850 ..from 9.2 up to 9.11 but they all have the same problem. Get flashing artifacts when there is gunfire on screen, luckily no crashes though. Running in Dx solves it but that's not really an option as u lose all the eyecandy. No other game has issues either so I'm pretty sure it's purely down to ATI and tbh i have little hope of them ever fixing it as IL-2 is such an old game.

Hmm I should have known better. That dll is for Windows Vista/7 64bit. I'll re-edit my post to clarify.

I'm not positive if there is a difference for 32bit but I'll see if I can dig something up.
Are you using a 32bit OS?

For anyone having problems in Vista 32bit or XP 32bit you can try these 9.5 drivers. I've read around other forums these were the most stable for IL2.

As I don't have a 32bit O/S installed I haven't tested these myself. Let me know if they work for you.

Choose the appropriate file for your O/S. Place the file in your IL2 root. Remove the file to return to normal operation.

Whats are the oldest drivers that run on the 5800 cards?

9.11 drivers on my 5850 card give me IL2 problems (like you all mentioned already). I tried dropping in 9.10 open gl dlls into the game folder, but that didnt work. Tried with 9.6 dlls, but that would hardly even run (like 1 fps). I dont think those older drivers work on 5800 cards.

Ati card owners are out of luck with IL2 I guess. It too bad, this card screams with every other game I've tun on it. I guess I'll wait for SOW, it should run ok on Ati...right?

This got me flying....

Run il2setup exe, disable vertex shaders, and vertex extensions.

Then in game, video options, set landscape to "excellent", not "perfect". Artifacting, and blocky textures appear with perfect landscape.

This is with 9.11 drivers.

Its not perfect image quality, but its running until they fix these drivers. I might try 9.10 drivers later today.

I have just read this, after Alpha recommended i use 7.11 ccc for my X1950 Pro, and now the FMB map loading works in 409m. Probably this issue with OGL in the later drivers, but then, 408m and 409 beta patch never had an issue for some bizarre reason.

I am runnng the same system as you, but that Link is Dead. Do you have another link?

March Dll's V409m

http://www.sukhoi.ru/forum/attachmen...5&d=1205425809

Same problems here with new system P55-G65 and Ati HD5770.
Cat drivers 9.8 supplied on CD and downloaded 9.10.
9.8 random crashes and 9.10 menu/font/colour problems as described before.

Only game i play on this system: IL2
Older system has (and had) NVidia Cards and never had problems with it.
Hope there will be a solution soon.
Ray

But the font problem didn't occur with 9.10, it started after them.

Try 10.2 or 10.3. Running 10.2 here on a 5870, on DirectX, works brilliantly.

I feel like I fell into the trap with ATi. It's really frustrating and completely random the crashes!

I run Windows 7 Ultimate 64-bit, Radeon 4890 Vapor-X, 8GB Corsair Ram in a Gigabyte EP35-DS4 Motherboard and a Quad 6600 G0 stepping O/C to 3Ghz.

I have Catalyst 10.2. I have disabled Vertex options in conf.ini. I dropped the ati dll file into the main IL2 folder. I also have the March 2008 (so long ago) .dll's in there.

FMB still crashes when it feels like it. When flying offline, I have no problems at-all. No graphics glitches, no problems.

As soon as I venture online (Dogfight Server at WC) I start wondering just how-long I will be around before I CTD.

I have noticed that it seems to be Snow or winter maps where I crash out most often, the usual syptom being the clouds start White and flicker to Black, eventually the ground (Snow) turns black or inverted colours and then I CTD.

I flew last-night for an hour over green fields, and not one probelm was encountered.

I bought the 4890 as it is a powerhouse when it comes to shifting graphics, and being the Vapor-X it runs quietly (which I prefer).

However, as IL2 is pretty much all I have on my PC for entertainment, I am seriously considering swapping back to Nvidia (275 or 285...if I can find one that doesn't sound like a hair dryer) as I cannot take much more of the frustration of never knowing if I will be wasting another gaming session with a CTD meaning another Disco to my record and another mission un-completed.

I know my mobo supports Crossfire, so Ati is 'native' to it, but it will run a single Nvidia if necessary.

So is there (unless this can be fixed) a quiet 275 or 285 card out there, and where is the complaints link to raise an issue with the driver at the ATI website?

Frustrated, MP

same feeling here MP... same GPU as well !

... BUT I now run the 9.10 ... and it WORKS !!!

Have you checked your O/C on Prime95? I had an overclock that appeared stable but showed memory errors in stress testing. Strangely, this didn't cause obvious problems but random errors would be sure to result.

Seeing as you have Win-7 ultimate, why don't you try running il-2 in the Win XP virtual machine. It's supposedly much better than standard 'compatibility mode'

dduff

All tested and stressed. Runs cool and happy. Ran a 12-hour test and no problems. Also it runs fine offline, only online and in FMB I get crashes, whichafter reading lots of posts, seems to be a Memory leak in OpenGL that gives random crashes.

Should be simple to fix, if only ATI can be bothered?

Cheers, MP.

I have the same issue with a 4890. The fix is to change to Excellent settings when using the FMB.
As I am a keen mission-builder I have set up a separate installation with a different conf.ini to use exclusively for mission-building. Once completed I just transfer the mission files (.mis & .properties) to the 'Perfect' installation. It only takes a few seconds to swap, and about 10 GB disc space to set up the 2nd installation. Preferably on a separate partition.

Overclocking is not the issue here: it's just IL-2 showing its age. My game runs glitch-free with a 12% system overclock, and so does the mission-builder if used as above

B

I had the same CTD's, but i think i solve it, never had this CTD's again with this workaround.

I use 10.2 in Opengl mode.
First make following changes to the conf.ini (Opengl Section)
Shadows=1 (or 2)
LandShading=3
Effects=1

Then start the Game, go to QMB, fly - crash the plane into ground or water - the font and menu problems disappear. After that your game should work normal.
The only problem you have you must join multiplayer games manually, you can't use hyperlobby etc.

I love your solution. Now, if only I could buy the GTX 260 core 216 at $137.00. :confused:

I have a ATI HD 4870, i have all the random CDT's with no error messages etc.
If I switch from perfect mode I think they stop happening.
DLL's do nothing at all to prevent crashing I've tried them all.
I'm going to try 9.5 cat to see if that fixes it as others have suggested it will.
Oh and as a sub note, this is an ATI issue.
I'm never buying from them again. This crap has been supposedly being fixed since 2007 when the issue first cropped up.
A problem for the future is if SoW uses OpenGL like IL2 has ATI owners are screwed.
I hope not :(

This problem occurs because we're now at OpenGl 4.1, Il2 was coded in OpenGl1.x if I remember correctly.

I somewhat understand ATI don't give a f*ck about this obsolete version.

You are correct, buy an Nvidia card instead it's the best solution.

BTW: SoW is going to run under Dx

OK so Cat 9.5 nearly fucked my system guess its too old for my card.
How about if I switch to Direct X renderer in the menus will that fix the issues?
Also will i get anything like perfect mode?

Why don't you make proper cleaning and install latest,very good CAT 10.7?

gprr

i run a 4890 and 9.5's worked ok for me (win 7 64 bit)- best driver i found till 10.7.
if it messed up your comp i'd suspect a bad install of drivers- you did reboot into safe mode and run drivercleaner after removing previous drivers?- then install new drivers/ccc

direct X mode appearance wise isn't too dissimilar from excellent mode.. both get rid of fmb crashes and reduce ctd's

one 'trick' i find helps stave off ctd's (on my rig) is to start(and stop) recording an .ntrk. for me ctd's are preceeded by stutters appearing then getting worse ~1hr into mission.
maybe worth trying?

Yeah i did a full uninstall then ran a CCleaner to make sure everything was cleared out before I ran the catalyst prog.
I have Win7 32bit and was running 10.7 since its release.
I'm lucky if I get an 1hr out of IL2 before a crash.
So if I run DX mode, what settings should I put into the conf file to get the best output?

If you overclock via CCC,try not to and see if things improve.
If you overclock your CPU,look into your bios setup.

gprr

Win7 32bit?
How many gigs of RAM?

The 4 series Radeons seem to have a problem with Il2. I've had intermittent crashes with 4850, then it continued with 2x4850 in CF... different driver versions, better cooling, all sorts of shenanigans... nothing helped, from time to time it would just crash. I've bought a 5870 recently and (knock on wood) no problems since (had 10.5 working, switched to 10.7 recently). IMO it's either a problem with that particular silicon, or faulty cards (some small fault to which Il2 is sensitive) or somehow the OpenGL driver issues that just weren't ever resolved for the 4 series...

Hello,

I am using the XFX HD5870 with Catalyst 10.5 (Win7 64b)and I haven't experienced too many problems. Let me know if you have this card and wish to get a copy of the render section of my conf.ini. Catalyst 10.3 to 10.4 also worked well but you need a work around for the text corruption.

Cheers,

Fafnir_6

B.D result looks like this:
Frames Time (ms) Min-- Max-- Avg
8677-- 150000---- 33----64---57.847

Main conf.ini section:

(Sound settings are diffrent from WIN XP and impact performance)

[sound]
SoundUse=1
SoundEngine=1
Speakers=1
Placement=0
SoundFlags.reversestereo=0
RadioFlags.Enabled=1
RadioEngine=2
MusicVolume=0
ObjectVolume=9
MusState.takeoff=1
MusState.inflight=1
MusState.crash=1
MusFlags.play=0
MasterVolume=6
Attenuation=7
SoundMode=0
SamplingRate=1
NumChannels=0
SoundExt.occlusions=1
SoundFlags.hardware=0
SoundFlags.streams=1
SoundFlags.duplex=1
SoundExt.acoustics=0
SoundExt.volumefx=1
SoundFlags.voicemgr=0
SoundFlags.static=1
VoiceVolume=6
Channels=2
SoundExt.extrender=0
SoundFlags.bugscorrect=0
SoundSetupId=8
ActivationLevel=0.02
Preemphasis=0.85
RadioLatency=0.5
AGC=1
PTTMode=1
SoundFlags.UseRadioChatter=0
SoundFlags.AutoActivation=0
RadioFlags.PTTMode=0
RadioFlags.PlayClicks=0
ActLevel=0
MicLevel=0
SoundFlags.forceEAX1=0

[rts]
ProcessAffinityMask=254 >>>>>>> Do not use fist cores(have 4 cores + 4 threads)
mouseUse=2
joyUse=1
trackIRUse=1
DisableIME=0
locale=


[Render_OpenGL]
TexQual=3
TexMipFilter=3
TexCompress=2
TexFlags.UseDither=1
TexFlags.UseAlpha=0
TexFlags.UseIndex=0
TexFlags.PolygonStipple=0
TexFlags.UseClampedSprites=0
TexFlags.DrawLandByTriangles=0
TexFlags.UseVertexArrays=1
TexFlags.DisableAPIExtensions=0
TexFlags.ARBMultitextureExt=1
TexFlags.TexEnvCombineExt=1
TexFlags.SecondaryColorExt=1
TexFlags.VertexArrayExt=1
TexFlags.ClipHintExt=0
TexFlags.UsePaletteExt=0
TexFlags.TexAnisotropicExt=1
TexFlags.TexCompressARBExt=1

TexFlags.TexEnvCombine4NV=0
TexFlags.TexEnvCombineDot3=1
TexFlags.DepthClampNV=0
TexFlags.SeparateSpecular=1
TexFlags.TextureShaderNV=0

HardwareShaders=1

Shadows=2
Specular=2
SpecularLight=2
DiffuseLight=2
DynamicalLights=1
MeshDetail=2
VisibilityDistance=3

Sky=2
Forest=3
LandShading=3
LandDetails=2

LandGeom=3
TexLarge=1
TexLandQual=3
TexLandLarge=1

VideoSetupId=10
Water=2
Effects=1
ForceShaders1x=0

PolygonOffsetFactor=-0.0625
PolygonOffsetUnits=-1.0


Cheers
gprr

Running an HD Radeon 4670 512mb here under Windows 7 Ultimate 32bit Build 7600 (fully updated) haven't had any crashes at all using CCC 10.7 drivers.

System specs:

Windows 7 Ult 32bit Build 7600
4GB RAM PC2-DDr2-5300
Gigabyte HD Radeon 4670 512mb DDR3 (CCC-10.7)
Maxtor 300GB SATA
Sound Blaster X-fi Xtreme Gamer
Asus P5LP-LE (Emery)BIOS 3.19
Thermaltake 430w PSU