Anyone with problems with ATI drivers read this.
 

http://forums.ubi.com/eve/forums/a/t...3/m/5031088038

PF_Coastie over at UBI with instructions on how to let ATI know of the problem so that they might fix it.

RedToo.

While you're right to complain about the bugs, I did manage to get acceptable performance after a lot of painful experimentation. My system has an i7/920 CPU with an ATI HD5870 GPU, but the settings here should be useful to anyone with a recent ATI card.

The simple solution is to use DirectX with the latest Catalyst driver update. I haven't tested this extensively but it delivered excellent FPS performance. The only problem I noticed was that the landscape tended to momentarily break up into black squares whenever the viewing angle was shifted suddenly.

The other problems with DirectX in il2 are one that the water is flat and not nearly as pretty as in OpenGL and two that 'perfect' graphics mode is unavailable. 'Perfect' mode doesn't matter except in clear weather (apparently) when it doubles the draw distance. I did manage to get both these features working in OpenGL as I'll explain.

With the latest ATI drivers (10.2), il2 is pretty much unplayable in OpenGL mode due to the problems of text corruption etc. Dropping a copy of version 9.1 of the ATI OpenGL driver into your il2 directory will allow you to use 9.1 for il2 (which works fine) and 10.2 for everything else.

So... after a lot of messing around, I finally arrived at what I consider the optimal settings:

First the screen resolution:

These settings will work for any widescreen etc. monitor unsupported by il2 simply by altering the width and height parameters to fit your monitor's native resolution.

Now to the Graphics settings:

I get around 32-45fps under 'normal' conditions with these settings. The 'Black Death' shows around 30-35fps on average, dropping to a minimum of around 22 in effects-heavy moments. I know that last figure sounds alarming, but I didn't notice it to be a serious problem in terms of the visual experience.

Setting effects at 1 tended to cause nasty fps hits during explosions etc. Setting water=1 (or higher) radically hurt fps performance. FRAPS showed 17 or so with water=1 but the ground was actually chugging past at around 5fps while only aircraft were showing the 'true' 17fps.

Water=0 is actually ok, still miles better than the DirectX version, and I don't think many people will miss the shadows from effects that effects=1 permits.

The good news is I can ramp anti aliasing, anisotropic filtering etc up to the limit in Catalyst Control Center without hurting the fps count in any way. As far as I can make out, the problem is that the Nvidia-optimised code is dumping extra load onto the CPU and that this is the limiting factor rather than GPU performance. Experimenting with lower resolutions did not produce an improvement in fps performance that I could see.

The game does look really well under these settings and the extra draw distance means that objects 'popping up' are much less obvious than with DirectX. Flying low over Slovakia or the big port town in the MTO map is particularly nice here and missions that use, e.g., smoke markers to designate targets will be easier when the smoke is actually visible from more than a few kilometers away.

At 30-40fps, some 'tearing' when rapidly shifting the angle of viewing, as with using a hat switch, will be apparent to those with sensitive eyes. It isn't a big issue for me, though, so unless you're one of those very few people who are sensitive to fps rates below 60 I'd suggest using the settings shown. Shooting games etc. can be painful enough at 30fps but Il-2 isn't really a 'twitchy' sort of game so I think I'll be sticking with this setup.

Thank you for your good help dduff442. I am using x1950 pro with 7.11 driver. Do you have any idea 7.11 catalyst settings for my card? I am posting my vga setting pictures.

dduff442, thank you! I have a 5850 running triple screen and have been struggling with the graphics settings since installing IL-2.

One question, could you attach or send me a link to the download of the ATI 9.2 OpenGL driver? I'm not sure exactly which file to use and where to find it.

Again, many thanks!

Cheers,
...Colin

Ooops -- got the version number wrong. That's 9.1 rather than 9.2. I've attached the zipped dll.

Checking for Catalyst updates on a regular basis is probably a good idea as well. Don't forget to backup the dll in your Il2 directory to test the updates, though, or otherwise you'll be stuck with 9.1 which isn't perfect by any means.

dduff

Start by taking the bits of 'code' above and pasting them over the relevant sections of the conf.ini file in your il2 directory. It's probably best to make a backup copy before doing so and make sure you save it as .ini and not as .txt. Also, you'll need to change the width and height parameters to match your screen's native resolution.

I'm not certain your card will run Il2 in perfect mode -- my last PC had 250mb of video RAM but I needed to tone down the settings to get an acceptable frame rate. Try those settings for a start, though, and if the fps is not acceptable you can try lowering the screen resolution or anti-aliasing setting.

Never having been able to use AA in Il2 before, I have to say it's indispensible. Without AA, distant planes turn into squiggles and it's impossible to tell where they're headed or to guess the lead for shots.

Hope this helps. If not, get back to me and I'll see what I can do.

dduff

This worked FLAWLESSLY. Thank you very much! Looks wonderful in 5760x1050 and so much better with no text corruption!

S!

Discussed this at ATI froums as well :) I run similar setup as DDuff. Some small differences in setup though. I run OpenGL and in conf.ini I do NOT use UseDither, PolygonStipple, DrawLandByTriangles at all, there is no performance gain or loss with them, no impact on visuals either.

As of Effects=0 or 1. This affects the "blocky text" corruption we get when loading the graphics of the game. With Effects=1 the blocky text clears after a moment when playing a track for example. Without it does not. Also with Effects=0 the 3D models flicker from grey to skinned etc. But with Effects=1 nothing of this is seen.

I wonder how you get VertexArrays NOT to produce the "blue hue" when firing guns? Or is it different in DirectX? I do not run DirectX as it looks crap, I rather use Water=0 in OpenGL than that ugly water in DX mode ;) In OpenGL the blue hue is tied to TexFlags.UseVertexArrays=1, having it at 0 and no "blue hue" even the TexFlags.VertexArraysEXT=1 is used. Go figure.

I used 9.10 version atioglxx.dll before, but not with the new drivers. I just start the game, run a track for a few secs and join servers via IP address. New drivers give good perfromance :) The Black Death averages at 55FPS with 70 maximum and dipa to 26 minimum(La5 and Fw190 collision).

I did go through the logs of my game crashes and it seems it is due IL-2 engine making bad calls to driver and/or hardware thus creating a situation where the game will stop working and just CTD. Discussed this in length with some programmers at the annual virtual pilot convention and these code mongers did explain it would not be too hard to fix if there was more info available..mentions of some wrong values in the code etc.

Thank you for these settings, unfortunately it still won't work with my system. Framerate is probably about 1-5fps and even menus are painfully slow. I have Ati HD4850 1gb card, catalyst 10.2 and 9.1 opengl driver in il2 directory, OS is xp32. Any thoughts what could be wrong?

Thanks for this, I noticed the blue hue last night also, I'll try removing the UseVertexArrays=1 and setting it to 0. Will report back.

Also, if I set Water=2 and Effects=2 the graphics quality is way, way better than both set to 0, it's a significant improvement. Using OpenGL.

S!

Using Effects=2 is not recommended even by Oleg as he said it causes slow performance and have artifacts especially in smoke. Can be flashing etc. I use Water=0 because of online play. I am not there to stare at wave tops but shoot down, or evading others most of the time ;)

Blue hue is tied to UseVErtexArrays. If not using it, then no hue either. The VertexArraysEXT has no effect whatsoever.

DB605, getting back to you at Hades site.

Hi guys,

Terry Makedon(head of the ATI Catalyst driver program) replied to my email and said this problem will be looked into.

As for the atiogl.dll, you guys should be using the 9.10 file (nine point ten) not the 9.1. Especially if you are using a 5xxx series card.

I am currently still tweaking my settings with my brand new rig (5770/amd Phenom II x 4 955BE/win7). I plan on creating a full tweak thread about my findings soon.

Real quick though, I am running 1920x1080 with 4x SSAA(Supersampling AA gets rid of the crawly rivers in the distance!), max Aniso, perfect, with water=0 and I am getting 62fps avg, 27fps min in TBD track.(V-synch off).

I have also found a work around for the Blocky text issue if you do not have the 9.10 atiogl.dll file.

Start the game/go to tracks/choose The black Death track/let play until the text clears at exactly the :21 second mark. Close track and you can play all you want with no more blocky text as long as you do NOT close the game. You can go online using direct IP too. But if you use HL, this will not work.

More later guys, Thanks!

You are correct about the driver version, I looked at the version number which is: 6.14.10.9026 this is associated with the 9.10 catalyst release.

9.1 and 9.10 are (how you say) the same number?!

Flanker's tip about disabling UseVertexArrays is spot on. Checking back, I find my original settings were based on a post of his at the ATI forums. Small world, eh?

Water=1 or higher still kills my system. I was able to improve performance a bit by setting the priority for the Il2fb process to 'high'. If you try this and it messes up your sound, just open Hardware>Sound Settings and click 'Apply and Back' which will reset your sound without changing anything else.

I actually overclocked my i7 to 3.2GHz and got a small improvement but decided it wasn't worth it and reset it to the default values. Fast core-duo machines will beat i7s in Il2 because Il2 only uses one core anyway.

If you think of it as a decimal, yes, it is same number. But when describing ATI's driver versions, that is a big nono and can cause big problems. Think of the decimal as a simple separator for two whole numbers. The first number signifies the YEAR and the second number signifies the MONTH. The 9.10 drivers were released in OCT 2009 and the 9.1 drivers were released in January 2009, ten months before the 9.10 drivers.

Hope this helps you understand the ATI driver numbers now.

Fair enough. The file attached to the earlier post is the correct 9.10 version, though.

S!

Coastie, I did file a Feedback Form for Catalyst team explaining the issues. But better now that you got Terry's attention. Thanks a ton! Hopefully ATI will take a look in this. At the annual virtual pilot con we discussed the IL-2 and how it performs. We did extensive track running etc with logging and checked results. It seems code of IL-2 has errors in some values in it, but hard to tell what without more troubleshooting capability.

Even IL-2 age is showin a small bit of attention could be given, to at least address the support for newer gfx cards. IL2 is so far the only game I run that has problems. Others I play, like STALKER, Rise Of Flight, Aces High 2, Mass Effect 2 etc. Have NO issues at all..go figure.

I am planning to go for AMD cpu just for fun, using Intel i7 920 atm with the Intel DX58SO mobo. Just need to see if the AMD can use DDR3 yet ;)

good news,thanks coastie

S!

Did some testing last night with Catalyst 10.1 Hotfix drivers and different DLL-files of IL-2 floating around. To see which ones would give best image quality and performance. Quite surprising results as average framerates were within 1-2fps between ALL of them with same settings applied to the graphics card. The most recent dll-files caused terrain to flicker and corrupt, but setting Catalyst AI ON solved that. Catalyst AI just has a negative impact on FPS, it drops and noticeable in heavier scenes of The Black Death. But average FPS was with ALL 53-54FPS at 1920x1200 32-bit, Perfect etc. Will post my test setup later today for reference.

A few pointers though. If using AntiAliasing EdgeDetect with 4X and AA Mode at Performance, there is only a very small hit on FPS, maybe 1-4fps. So a very well implemented thing. With Adaptive or SuperSampling almost the same, maybe slight stutter. But need to run more tests to verify this. Anisotropic filtering, if application controlled, gives worse image quality than overriding it with CCC. IL-2 seems to use 2x Anisotropic only. I ran tests with 16x and there was a difference in the water shimmering.

Catalyst AI is a bit complicated issue. Some DLL's required it to be at Standard at least to get normal graphics(terrain only). Some dll's worked normally and faster without it. Catalyst AI at Advanced caused water to look like it was "pixelated" or covered with small squares. So I settled with a set of dll's that gave best image and performance without Cat AI.

The variation of error messages in console with different dll's was wide. Some gave a lot of them, most only the clamped error now and then. So a set of new dll's for IL-2 would clearly help users to get more out of IL-2, but that is up to TD/MG to decide :) Test results with settings and conf.ini later today..still at work..meh!
Coastie, can you keep us posted on ATI Team's responses on the driver issue? Would be great to see these issues rectified.

I rcvd an update from Terry and they are working on it. We will need to be VERY patient with this guys. As long as e have the 9.10 dll's we are ok. A lot of testing will be going into this as well as making sure nothing else is broken in the driver after making adjustments.

I will test some of your findings Flanker. I like what you have come up with so far. But I disagree with your assesment on the in game aniso.

S!

Coastie, the anisothing is based on the thing that if I set it to Application Controlled then it reverts to 2x every time I run IL-2, even it would be on 4x or anything else before that. Also when running application controlled the shimmering is closer to you than with forcing it to higher value with CCC. I ran on 16x and it was almost non-existent. But results may vary and we need to test more :)

I now changed rig to AMD Phenom II 965 BE + 790FX chipset Asus mobo added with 8Gb DDR3 in dual channel. IL-2 runs fine even there is still the blocky text. If you need something tested, just let me know and I will dig into it. I am for one very eager seeing IL-2 run fine on ATI cards and if testing helps then even better :)

When you switch to app pref in the CCC it will revert to 2x. It has nothing to do with what the game is rendering. Try this for a comparison......

Start with a random CCC setting of lets say 4x and uncheck use app preference in the CCC. Now start game/choose a map with lots of long straight LEVEL roads/hit fly and lawn dart your plane onto a nice long stretch of level straight road(try to mark the place you crash so you can do it again in the same place). Now, using the external view, look straight down the road at ground level. NOTE HOW FAR YOU CAN SEE THE ROAD CLEARLY UNTIL IT FADES AWAY. (pick a tree or something to mark the spot).

Now close game and go back to CCC and tick use app pref in the aniso block. Also make sure you are using aniso as your mipmap filter in the conf.ini (TexMipFilter=3).

Now go back and crash your plane in the same place and compare how far you can see down the road. I am sure you will be amazed at the difference. I find that using the games aniso gives me much better results and higher fps.

Hi,
I just wanted to share my config.ini settings. I've spend couple of hours in testing to find best settings for my system (ATi User).

System:
CPU: Athlon 64 X2 4600+ @ 3200MHz (Overclocked)
MEM: 2x1GB DDR2 @ 800MHz
Video: ATI Radeon 4850 512MB

Video Settings:
Resolution: 1280x1024 (I'm still using 19" 5:4 LCD)
VSync: Off
TrippleBuffering: Off
Video Mode: OpenGL,
Antialiasing: forced to 6x.
Anisotropic Filtering: forced to 16x
Catalyst A.I.: Low

Test is made with DeathTrack and Fraps.
The Benchmarking is started around one/two seconds after DeathTrack beginning, and stopped after 152 seconds.

The Result is:
Min: 21fps
Avg: 53.776fps :)
Max: 123fps (:o)


I've found that setting some TexFlags to 1 have great impact on fps. Don't know is that true with nVidia.

To dduff442: Can You try with my [OpenGL] config.ini settings (especially TexFlags) and post results. I think You can get far better FPS with Your MONSTER System (compared to mine).

p.s.: Sorry for my poor English.

Brainless, your english is great.

Try checking "use application preference" in the aniso block of the CCC. You are already using the aniso filter in the conf.ini, so you might as well try it. I think you will find that it will give you a few more fps and you won't be able to tell the difference visually (ESPECIALLY WHILE FLYING).

Also, what ati drivers are you using and do you use the atiogl.dll in your IL2 folder?

Very strange you have these off:

TexFlags.TexEnvCombineDot3=0
TexFlags.SeparateSpecular=0

Do you see any texture problems in game?

Lastly, the below two settings are supposed to be for ATI. The ones you have are supposed to be for Nvidia:

PolygonOffsetFactor=-0.0625
PolygonOffsetUnits=-3.0

Your FPS are fantastic and it looks like you have found a sweetspot for your system. I am just trying to see if some of these make any difference in the real world.

I will test your settings too.

Good job!

Mate, i will try this file too but do not know where to i put it.

If you have an ATI 4xxx series card or newer, you want the 9.10 file, NOT 9.1. They are two totally different drivers.

Just drop it in your main il2 directory.

The file attached to the post on pg 1 is the 9.10 driver though.

@Brainless

I've done a lot of benchmarking but I've been fiddling around with the settings so much its hard to compare the results. My setup seems to have made peace with water=2 and gives acceptable frame rates now, the only problem is I can't pin down the exact reason.

The main problems now are freezes when the point of view is changed at the start of missions as the terrain and objects etc are loaded into memory. If anybody's having this problem, the simple solution is to pause at the start of the mission and have a good look around with external views enabled. Do the same for other a/c as well if needed and those annoying stutters at the start should be dealt with.

I'll post benchmarking results and settings tomorrow.

I think I've found an answer to the shimmering water/wriggling shoreline problems and a way to use Water=2 with both good FPS rates and good image quality.

Because I was varying so many parameters before, I was mis-interpreting the meaning and effects of each setting. I was running with Catalyst AI disabled because I'd somehow gotten the idea this causes problems but with my other graphics settings too high this gave me the incorrect impression I needed to set Water=0.

Enabling Catalys AI together with maximising all the Catalyst settings gives playable FPS on my system but the problems of shimmering water etc. remain. This is because as the graphics settings are too high, Catalyst starts scaling back the anti-aliasing etc settings in GPU-intensive scenes. The shimmering/wriggling starts when the AI throttles back the AA and you basically get no AA when the GPU load gets too high.

I've found it best to start with AI disabled and every other Catalyst setting minimised except for AA Mode which I set to 'Super Sample AA'. Super sample AA has the biggest impact on both FPS and image quality. It's the only setting that will fix the shimmering/wriggling problems completely so if image quality is important to you this is probably the best place to start.

After checking that FPS is still acceptable, you can then start upping the other Catalyst settings bearing in mind that AA is both most intensive for resources and is most important to image quality (it being the reason for enabling the GPU-hungry 'super sampling' in the first place).

At 1920x1200, my HD5870 gives (Track) AvgFPS/MinFPS (TheBlackDeath) 49/15, (Kamikaze2) 48/15 and (P39vsBf-109) 79/49 with Catalyst set as follows:

AI disabled
4xAA using 'Edge Detect' for a total of 12x samples
Super-Sample AA
'Use Application Settings' for AF
'Quality' mipmap.

...the FPS drops in BlackDeath and Kamikaze are fleeting and barely noticeable. P39vsBf-109 is problably more typical of normal operation. Max FPS is anywhere from 120 to 160.

For anyone who joined the discussion late, I'll go through all the steps again: (1) edit conf.ini, using Flanker35M's settings. (2) Drop version 9.10 of atioglxx.dll (attached on pg 1) in your Il-2 directory (3) Switch off Catalyst AI, minimise all Catalyst settings and set the AA mode to 'Super Sampling AA'. Check your FPS in 'BlackDeath' -- if it's okay, start increasing AA and AF settings in Catalyst checking FPS after each increase. If FPS is too low with 'Super Sampling' enabled, you'll need to choose between lowering the resolution, lowering the Sampling method to e.g. Multi-Sample or setting Water=0 in conf.ini.

Multi-sample AA will cause wriggling/shimmering effects on water, but if you can live with that then fine. Otherwise you can enable Catalyst AI which will ensure a decent FPS but the wriggling etc. will still pop up every now and again.

Your final nuclear option to hang on to 'perfect mode' graphics is to set Water=0 and Effects=0 in conf.ini. That way you'll still get the maximum draw distances but lose a little eye-candy. Alternatively, you can lower the draw distance and hang on to the nice graphics settings -- they're very nice indeed with all the niggles ironed out.

Very good point Duff. It is always a good idea to start at a low base and work your way up.

For instance, with my 5770, I only run SSAA in "box"AA at 2x because my card has a lot less horsepower than yours. But it still gets rid of the shimmering and it looks great at 1920x1080.

Now, If I drop down to say HDTV 1280x720 (you must have an HDMI cable to see this setting) I can bump that up to 4x and still get about the same fps!

Also, I prefer to run water=0 because quite honestly, I think water=2 just looks stupid in rivers. It looks great in open ocean. But in rivers it just looks silly. I think water=0 just "fits" better to rivers.

On a side note: I hope they "scale" this feature in BOB. So that you still get the same effects with different water settings (reflections,shadows) but it scales to the body of water it is in. In a river, even in windy weather, the waves should not look the same as they do in the ocean or a big lake.

S!

Yes, good to test various settings. This is how I did it as well. The "jaggy" rivers is no real show stopper for me, as again I am not there to look at the rivers or water ;) But it is true SuperSample AA setting helps with it.

The thing with Effects-setting. If using 10.1's without the Effects=1 you are almost certain to get graphical anomalies when explosions or gun fire near the planes. When at 1, then nothing. So is this setting tied to lighting as well on surfaces etc?

Catalyst AI. I keep it always off, it reduces FPS in IL-2, easily measured in The Black Death for example. Having it off gives a few extra FPS. Funnily enough Catalyst AI is required with some DLL's (IL2 ones, not ATI) to get rid of the terrain showing up as flickering and distorted squares. The latest 13.3.2008 DLL's work without Catalyst AI with decent perfromance. On par with the 9.2.2008 ones, very slight difference.

I also run 1920x1200 as having 16:10 scale 24" screen. My FPS in black death with current settings with VSync on is min 23 max 72 avg 53 FPS. Without VSync the minimum is the same, maximum 200+ and average around 82 FPS. I run now an AMD rig instead of Intel, just for the fun of it ;)

Yeah, the shimmering is one of those things that just drives some people nuts. It is a real eye catcher on certain maps with lots of rivers, that is why I try to get rid of, or at least reduce it a little.

People so often try to max out all this different eye candy without ever consider the real world affect WHILE FLYING IN COMBAT! If you are flying in combat, you will not notice 75% of this stuff.

Take the "effects" settings for instance. The only real differences are effects like shadows under explosions and small puffs of smoke......REALLY? Can someone honestly say they see the difference in this stuff while fighting a dogfight or attack ground targets?.......REALLY?

That said, it is still good to know what your machine can do. Maybe you like to take high res screen shots and stuff like that. Well then you really need to know what is your max settings that can still be playable so you can record tracks while playing then go back and get the best possible effects. But for 95% people much less settings will do because they will never see the difference in game in combat.

S!

Did some more testing, results can be seen over here: http://forums.ubi.com/eve/forums/a/t...5031088038/p/4

S!

After testing some more..I set on the Vertex Array options in conf.ini and got following results...There is an impact for sure. Hoping ATI will issue this un upcoming drivers.


Black Death track, both VertexArray option enabled

Minimum: 28fps
Maximum: 284fps
Average: 93fps

+ Increase of fps in smoke and flame intense scenes of the track and average boosted a bit.
+ No artifacts or anomalies, either no console errors.
- The "blue hue" is there with these on.


Black Death track, only VertexArrayEXT enabled

Minimum: 24fps
Maximum: 285fps
Average: 93fps

+ Perfromance still good
+ No "blue hue" noticed nor artifacting, console clean.
- Would perform better with both options on.


So ATI has some homework to do with their drivers. I post the results I got without the vertex arrays enabled below. Figure the rest ;)


Black Death track, no vertex arrays

Minimum: 23fps
Maximum: 286fps
Average: 93fps

+ No artifacts or errors, no blue hue
- Slightly lesser overall performance in dense places of the track.


If you look at the numbers there is no big difference. The difference was in overall performance of the track playing. With both Vertex Arrays ON, the track ran at a higher consistent FPS than without them in many places so definitely has an impact on performance of IL2. This can explain the difference between nVidia and ATI in IL2 as nVidia can use Vertex Array option without problems thus giving more FPS in certain situations. If ATI and/or MG/TD can fix this issue then there is none or very small difference in performance of either card brand.

Back to testing...

You should send those test results into the ATI feedback form....good stuff!

S!

Feel free to use them if you are in direct contact with Terry :) I can be your tester if he asks for something :D

S~! Coastie

Long time no see.

I have done a lot of experimenting with ATI and confirm flankers results with vertex. Its also the same with AnisotropicExt changing to 0 or 1 yeilds little to no difference.

I recently went to the darkside (temp rma my sapphire) with an Nvidia 275 GTX and must say that the performance increase is incredible.
Over 30 fps increase in Black Death average and minimum frames up by over 15fps.

My understanding is that SoW is going to be heavily optimized for Nvidia...... I hate to admit it but I think my move to Nvidia may be permanent.

Ati is not supporting S.o.W according to some devs..... highly doubt there will be anything really done to improve IL2

But keep pluggin :)

My settings FOR MAX visual quality while maintaining high frames as follows

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

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

HardwareShaders=1

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

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

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

VideoSetupId=17
Water=0 (change as you see fit)
Effects=1 (change as you see fit)
ForceShaders1x=0
PolygonOffsetFactor=-0.0625
PolygonOffsetUnits=-3.0

S!

I really really hope SoW is NOT going to be a "one trick nVidia pony" like IL2 is. There was a reason for this, but with SoW I do not see ANY. Not gonna buy nVidia just to play one game my current ATI maybe could have problems with. I read the forums how people bitch about ATI but in most cases I do not have their problems at all..so the BIGGEST factor here is the organic plump that is between the keyboard and chair ;) People expect and assume too much, think they know it all etc. And even then..after all the moaning they have to admit it was a thing they did. IMHO. And if there really is a problem, then there are channels to voice your concerns, if done in an appropriate manner of course. Saying: it won't work you suxxors is hardly constructive feedback that a dev will react to ;)

DirectX 11 is same for both brands..and both brands provide massive performance in it. Also if devs say ATI gives no support..it really is a 2-way road to be honest. Have they even put effort to it..and what do we even know what is going on behind the MG curtain? Sure nVidia could be lobbying and smearing, nothing new there in the world of business and hard cash. But I do not think ATI would ignore a title that will be a benchmark for years to come. Like shooting yourself in the leg.

But not to derail from the topic..The pipe towards ATI is open regarding drivers with IL2 which is a good thing :)

Wishing on it REALLY hard won't make it so ...... ATI has never had proper drivers for IL2 ... never mind 'optimized' ones.

Devs code for NV ..... it has been stated. You can bury your head in the sand or you can deal.

I have been ATI in this game from day one, but now its not really feasible .....when one brand gives you a 30fps average frame advantage ...... its time to move on.

ATI is great piece of hardware for a good price ..... but its not for this series of sims if you are looking for maximum performance.

S!

ATI is looking into IL2 now and even with the bugs in drivers I have come very close to the FPS nVidia users get ;) Maybe should start lobbying ATI to take a look in SoW. They have DirectX 11 certified hardware already and SoW is DX 11 ;)

To put it this way..If regurarly I run many other games without a glitch, namely Rise Of Flight, Aces High 2, Mass Effect 2, STALKER, Dawn Of War, EVE Online etc. and ONLY IL2 or SoW would cause me any kind of need to tweak or such..that should tell something and not very flattering in my book.

I will buy SoW to support flight sims anyway..and tinker to make it work if ATI supposedly does not look into SoW..which I think is not true.

S~!

Well good luck with that Flank ..... I am 42 and have better things to do with my time than to constantly tweak defective drivers for a game that is optimized for another card maker. Oleg has a longstanding relationship with NV .... whether we like it or not. NV cards run his games BETTER - and that couldn't be more evident with the latest drivers ATI is pumping out. That is not opinion...... but fact.

At some point you have to weigh whats best for you and the games you play.

There was a time when hardware was roughly equal in IL2.

That is no longer the case ..... regardless of what you "think" .... benchmarks don't lie ..... and your not that much more tech savvy then the rest of us regardless of what you try to 'insinuate' ;)

Indeed there might 'gasp' be some people posting in this thread who own a computer business and consult/build/troubleshoot/optimize hardware/software for a living :eek:

Once you get to my age, tinkering loses its appeal. I just want things to WORK now.

S!

I have not stated being any tech savvier than anyone else, far from that. What I know is based on my experiences with computers. And not that far from your age either, so referring me as a teen is an insult actually ;) :P

For me slight tinkering is not a bad thing, that way I learn more how things work. Blaming ATI having worse drivers than nVidia is utter BS in my opinion. There are no perfect drivers. nVidia pours out drivers now and then, but it does not mean quality. Neither does ATI's 1 per month. Too many configurations and systems to make everything click, so I find it worthless to debate of 2 brands making stuff making us able to play..

Benchmarks are crap. Take a benchmark, construct a set of drivers just for it and then show off the FPS. Hell yeah, so far from truth that anything can be. Joe Average is blinded by the tech mumbojumbo, flashy fps and buys the card and is soo disappointed when the marketing hype is going down the drain..I believe when I see with my own eyes.

So I would end this by saying that if feedback to ATI makes a difference, then this tinkering etc. has not been in vain. Pointless to bring up the fanboi mentality, both brands offer more than enough power for our needs. Just a matter of preference which one you use.

I loled:lol:

We dont even know when the game will be finish, yet you're already saying that NV will be better....

If you look at game these days, both ATI and NV are quite the same, except if the develeoper take HAVOK or PHYSX.....

I really dont think we'll see a diffenrence in quality if the game is made in DX mode....

We got problem with ATi because of the OPENGL driver....

Anyway, wait and see:rolleyes:

Hey Proto, been a long time man. I see you haven't changed! ;-)

What ATI card did you have before you changed? Did you upgrade your entire PC? Are all things exactly equal here?

Because your claims are complete BS man. If you had a card on the same level as your GTX275, it would have been an ATI 5870 or maybe a 4890. Otherwise, you are not comparing apples to apples here.

Guys with 5870's are getting very close to same fps at the 280's are IF all things are equal. Which they likely are not.

ATI's AA settings are way different than Nvidias as well as the quality. To get two games set up exactly alike would be tough because the AA settings alone just do not match up.

So, lets just get off the fanboy wagon here(I am one, I know it) and get back to the topic.

LOL

EXACTLY the same system and if you actually read the post you would see what the hardware was.

It was a 4850X2 2gigabyte card water-cooled and overclock to 4890+ clocks. 3D vantage scores are within a couple of hundred points of each other with the 275GTX


The lack of knowledge in here is stunning.... and for the record its my first NV card in almost 10 years..... was straight ATI since day one in this game.

Make it personal ......... but as the young pups say the facts are raping your faces :cool:

The only fanboy wagon, is the one you fellas are riding, owned both and benchmarked both which is more than anyone else in this thread can say. Orb results available if necessary.

But hey I got love ..... just make sure to post those new ATI drivers that will fix text corruption, close the memory leak in 9.x & 10.x drivers AND will give EQUAL frames for same IQ ...... LoooooooooooooooooooooL

Loyalty to people is good. Loyalty to companies is for idiots.

Sorry, but I still dont see where you posted your card. I must be missing a post or something.

Glad you found something you are happy with. Your right, Nvidia is perfect in every way and ati is the devil. Thanks for your contribution to this thread.

You are 100% correct in all aspects.

Thank you and sorry for my blaring ignorance Sir.

S~!

Its all good. Ignorance is Bliss. Sir.

Looking forward to those new drivers.

S!

Protos, maybe you should cool down a bit. My cards have been both ATI and nVidia, since day one or whatever you refer to. And I can say this 5870HD rapes the face of my previous 280GTX bar none. ONLY game where nVidia has been even close challenging this card or even topping it is..tadaaaaa..IL-2. So cut the crap and stop saying your 275GTX beats my ATI. And that is a FACT. Do not need to be a fanboi even to state it ;)

As of the drivers. 10.1's have no memory leak. Before they had as you said, no arguments there. Was easily spotted when trying to build a mission in the FMB, the game crashed after a while. Now nothing, zilch, nada! It works like it should. IL-2 is an old game, nearly 10 years and it shows. If ATI is looking into the driver issue and IL-2 bug it is a good thing, a benefit for all.

I do not test and tinker IL-2 with ATI to promote myself or prove something. Just to provide information what makes what if changed in settings. Those with knowledge of the internal workings of IL-2 like TD or MG MIGHT read this msgboard and take a look and possibly even do something about it.

It would be very nice of you if you stopped spewing the nVidia stuff in a thread supposed to give hints and tips for ATI users. And if you are such a guru with ATI, since day one, then maybe you could contribute as well rather than poop out nVidia supermacy or propaganda. It serves no-one.

So back on track here...Testing and seeing what does what ;)

S!

And just for Protos as you said benchmarks do not lie. A link to Guru3D that tested the cards on similar system to achieve results. Numbers speak for themselves I think. Fermi will for sure change the listing, it is a neverending story of fluctuation. But here the link http://www.guru3d.com/article/vga-ch...ecember-2009/1

S!

For the fun of it tested Protos's conf.ini, except did not have all those NV related items on, only 2. Some notes on them. Sky=1 equals to no clouds so gives a boost in FPS. Easy way to pad your average. Landgeom=2 also gives a bit more FPS. The AnisoEXT=0 or 1..slight difference in image, with 1 better for me. But let the numbers speak for themselves..

Protos conf.ini, otherwise equal to my settings above
* Min 25 Max 296 Avg 107 FPS

With only Sky=1 on my original conf.ini
* Min 25 Max 286 Avg 100 FPS

My original conf.ini
* Min 23 Max 286 Avg 93

Note that I use Sky=2 and LandGeom=3 that drop the average FPS a bit.

ouch, I laughed so hard I think I just broke one of my ribs :lol:
I dont know where you get your ''facts'', but in 90% of games ATI is over NV in benchmark. And dont take Vantage as a reference, it's working with PHYSX:rolleyes:.

My 4870 were my 1st ATI card ever, always was with NV before. There is some things I like more with NV than ATI, and vice versa.

And for someone over 40, you act very childish and seems to be a very stuborn person:!:

I'm waiting for FERMI to be released to see what my next purchase will be, but I'll certanliy not made my choice because a compagny screwed up a game 10yo :rolleyes:

I'll never understand why folks get all spun up about ATI v's NVidia. They're just two hardware vendors who both compete to make the best graphics cards they can. Whenever one releases a new card that is usually the card to have to be soon leapfrogged by the next.

Right now if you want triple-screen or maximum performance the only option is ATI. When NVidia release their new card as long as you don't mind single-monitor there is NO DOUBT that will be the card to have. But at this time the new ATI offerings utterly destroy anything from NVidia. As to be expected, those NVidia cards are ancient now!

We're fighting with a 10 year old game here people, it's obviously going to have some issues with the newest hardware. Frankly I'm astonished it works with my 5850 in triple-screen in OpenGL (really who uses that these days) at all!

Just enjoy what you have and expend the energy arguing over air supremacy, not who's card is better (na na na na boo boo)

S!

New Catalyst 10.2's are out. Ran a few tests with them. Performance is good, but the blue hue and blocky text is still there. did not expect any fixes this fast though and filed a Feedback form with detailed info how it shows and how to reproduce etc.

What I noted with these new drivers is that clouds look normal in Black death track again, before they looked kinda too bright etc. Also tested with NV related settings on, this time no console errors at all and no decrease in performance as before. But need to conduct more extensive test runs today.

Keep filing those feedback forms with details :)

Thanks Flanker!

I had just enough time to load 10.2's and run a track. Then I realized I still had the ogl file in my folder. Moved that and ran again. The one thing I noticed was that I got a 2fps jump in Min and 6fps jump in average....interesting! But yes, still blocky text. I will look at the clouds later today. I did notice they looked "bright" before.

I will be sending in my report this evening also.

PLEASE FOLKS, SEND IN A NEW REPORT IF YOU TRY THESE DRIVERS.

S!

Will file a feedback form about 10.2's as well COastie. It seems performance is getting there, but I got a bigger boost with Vertex Arrays enabled. This of course brought the "blue hue". Blocky text is a bit odd, as it is partially affected by Effects-setting in conf.ini :confused: If Effects=0 then blocky text would not clear, if 1 or 2 then clears.

But again, back to testing..

But still no relief for those of us who fly through Hyperlobby but get shut out by the blocky text issue. Damn!

B

Brando,

Doesn't placing the atioglxx.dll from the 9.10 driver set work for you? This enables you to fly just fine in IL2 with no blocky text issues while still letting you use the latest drivers until they get this fixed.

S!

Brando, tyr the thing Coastie mentioned OR launch game, run a track and check with console when the blocky text disappears as it does clear after a bit. Then join the server via Multiplayer from game typing in the IP. I use this, even it is a bit more work to do so. But it is either 9.10 file in folder, use of older drivers or waiting for solution/using the workaround.

New report sent to ATI with full details on reproducing problem.

S!

Sent as well. These 10.2's offer very good performance though even they still have blue hue/blocky text.

Hey guys,

We have done our job. Terry Makedon emailed me back. Feedback forms are no longer needed, they are definately looking into the issues.

Good job guys, now we just need to be very patient. These things take a lot of time.

S!

Thank You to everyone that did file a feedback form and provide information. And thanks Coastie for opening the channels to ATI :) A good point to work forward towards SoW :)

Running 10.2 in 4.09. I have the 9.10 ati file in the 1946 folder.

I have disabled both Vertex option in the conf.ini. so no blocky text or blue hue.

But I sometimes get the oddest effect when flying over summer or winter landscapes. It can happen at a random time, but the ground goes Deep Blue/Black in colour, all the objects stay correctly coloured, but after about 10-seconds the game CTD's.

I have the original dll installed with the game, so would the 13-3-08 version help do you think?

Cheers, MP.

Hey Puma, Great to see you man!

Yes, the newest dll's from the 4.09m patch should fix that. Even though I have not seen what you describe, it would only make sense. It certainly would be worth a try.

S!

Mysticpuma, also make sure Catalyst AI is OFF. It does not work very well with IL-2..ATI is looking into IL-2 issues. But I rarely even use Cat aI, see no improvement using it.

Hi Flanker, I have been keenly following this post to make sure I get the most from my 4890!

I have made sure that AI is off, I am running all settings maxed, with Program control switched off, so I get max AA and AF. I need max settings for the movie work I do, so any Graphical glitches cause me great irritation! I long for the days when I flew for fun!

I hope that the guys at ATI can get a fix for this as IL2 is pretty much the only game I have on my system at the moment (although I do have Modern Warfare 2 and Fallout 3 ready to go when I finish the Checkertails movie!) and it's a real pain to have to tweak settings in the conf.ini so I don't get the Blue muzzle flash effect!

Really appreciate the time and effort you have put into this thread and contacting ATI, and looking forward to a fix! Soon!! lol.

Cheers, MP.

S!

If you can live without the older atioglxx.dll in your IL-2 folder and run Black Death for a few secs every time you start the game, then you can safely use 10.2's or even the leaked 10.3's floating around. It sure is a bit more work, but I do this way, just run track to clear blocky text and after that game runs normally. It is only the first load of 3D that does it in Perfect mode.

I've been running tests so my face is blue to get best settings. Actually you get very good image with game controlled Anisotropic Filtering and using Box 2x with SuperSample Antialiasing, it clears the shimmer effectively. Coastie found this. Also in Color at CCC panel you can fiddle a bit with gamma, I dropped it a few notches and the colors are better too :)

I slap my conf.ini below, check it and see what you can use :)


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

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=2
TexLarge=1
TexLandQual=3
TexLandLarge=1

VideoSetupId=17
Water=0
Effects=1
ForceShaders1x=0

PolygonOffsetFactor=-0.0625
PolygonOffsetUnits=-3.0

Flanker, can you post your CCC settings that compliment the in-game settings above?

S!

Of course! Here they are...Taken in order as they are in ALL-tab, using 10.3 drivers.

Smoothvision HD Antialiasing: BOX 2X samples
Smoothvision HD Anisotropic filtering: Use Application Settings
Catalyst AI: Off
Mipmap Detail Level: High Quality(to right)
Wait for vertical refresh: On, unless application specifies
Triple buffering: On

Is use VSync as I hate the tearing when using TrackIR. In Benchmarking I have VSync and triple buffer off.

OOps, you forgot one:

Antialiasing Mode: Super Sampling

S!

Yeah, forgot that one ine the hurry I was in :) Any news from ATI yet? I wonder if they include the fix in a new version, like 10.3 or 10.4..or as a separate hotfix driver. I would guess in a major package release though. Shall see, can't wait to finally get this ATI issue with IL-2 sorted!

Amen to that Flanker! Looking forward to a fix. I also asked in the questions to Team D, whether updated dll's could be looked at for 4.10 as there have been so-many updates in cards and drivers since the last March 08 release.

Cross-fingers, IL2 and ATI will be a working combination very soon?

Cheers, MP.

I'm going to wait until March before bugging Terry again. He said that he would be in touch. So I will wait a while. I really don't want to push the issue anymore than I have and possibly ruin a very good thing. I also doubt it will be a hotfix. My guess is CAT 3.4's at the very earliest. More than likely the 5 or 6's though.

my guess is 3 to 5 months.. if at all
you know ATI is already working on stuff many months in advance, and also they need room to put out fires..

S!

At least they got a lot of feedback and detailed info on the issue which could help narrow down the fix in the drivers. Just a guess as I am no programmer :D Still, it can be a wait but if they really put some time and effort in, the result will be even better.

MP, Team Daidalos does not change DLL's as their resources are not enough and going in to that jungle, as one of them said once, is not very likely. It would require someone from Oleg's original team who was working with them to do anything about it..and SoW is #1 now so I guess not too likely, at least before SoW is out. After that..who knows?!

But again, let's wait and see. Coastie has contact to Terry which is extremely good. I have been reading how ATI gets fire why games do not work and they should fix this and that. Well, in most cases I checked the poster's spec and almost ALL systems were overclocked to maximum..Expecting hardware strained to limits run a piece of software flawlessly is just utopia.

I have not overclocked my system at all and I do not have any problems either..currently only with IL-2 but that is being remedied as well :) All I can say that DirectX 11 games just look so damn good with the new features like tessalation etc. Aliens vs Predator is goddam gorgeous :)

Thanks Flanker. I've noticed no loss in frame rate by turning the AA all the way to 8X. However, I cannot use super-sampling as that is an unacceptable frame rate killer for me. I am running 5760x1080 with an ATI 5850 card and in order to maintain an acceptable frame rate I run with Anti-Aliasing Mode set to "Multi-Sample AA". Any other setting absolutely kills fps.

So my final settings are:

Smoothvision HD Antialiasing: BOX 8X samples
Smoothvision HD Anisotropic filtering: Use Application Settings
Catalyst AI: Off
Mipmap Detail Level: High Quality(to right)
Wait for vertical refresh: On, unless application specifies
Anti-Aliasing Mode: Multi-sample AA (all the way left)
Triple buffering: On

S!

Nice setup there maclean525, with such big resolution. But do you really need 8x Box when maybe 2-4x would do the same with less impact on FPS? I use 2x with SSAA and looks just OK on my mere 1920x1200 resolution.

I tested 2x, 4x and 8x AA and the fps was the same on my machine for all three settings. Picture quality was better though which is why I stayed with 8x.

S!

Yesterday tested the Black Death again with settings I have. These 10.3 drivers hold a promise and if we get the IL-2 issues fixed the performance will be damned good.

What I got was as follows..Min 24 Max 296 Avg 97 FPS :) So pretty decent performance!

Flanker, do you have Perfect mode? Dont you see something stange ?

S!

Qpassa, what do you mean? I run Perfect mode yes, HardwareShaders=1. The game runs smooth and has no artifacts and no error messages in the console..so no, nothing strange there. Sure I have the "blocky text" when loading graphics, but it clears when the track has played a few seconds. Sure if I play with VSync Off I get tearing with TrackIR, but online I use VSync On so not an issue.

As of the minimum FPS, it is a bit less than on a nVidia card I know. But when ATI fixes the issues I think it will go up. If I adjust Forest=0 and Sky=1 I will get over 300fps maximum, but then there would be ugly forests and cloudless sky. So I sacrifice a few FPS for the clouds and forest. When I play on the Slovakia map summer, my average is 120-140fps, minimum 50fps near those populated towns/airfields, maximum nearly 400fps. So I would say totally playable :)

I have been following the whine of people about ATI and in MOST cases when they have problems I see their system specs. And there is the common thing for over 90% of them, seriously overclocked systems. One can NOT expect a rock solid system with such OC. I run stock speeds and have zero problems. For example people complained about MAss Effect 2 and Aliens vs Predator games having problems..I have none and in AvP the DirectX 11 mode just is amazing...Go figure ;)

no OC here..

S!

Ramstein, in general in some hardware forums the power users/overclockers whine of hardware not working while pushing it far beyond the design limits thus begging for trouble. But sure it is an interesting hobby to OC. And yes, also "stock people" have problems, do not deny that.

So far I have been very happy with ATI, IL-2 being only game with some issues. Sure workarounds help, but even better when ATI is looking at the issue now. My computer is for gaming only and I have as little useless crap installed as possible, which can be one reason for no or very few problems. A casual user might have his/hers machine for other use too and it is always a compromise. If I had to use a computer for working, it would be separate :)

But not derailing the thread here. We are eagerly awaiting info from ATI via Coastie. Meanwhile testing and playing :)

There's overclocking to instability which will cause problems with the most stable of drivers. But blaming these Ati issues on overclocking is just a red herring. I run both my CPU and my 4890 overclocked but stable and I have no problems with any drivers up until the November Catalysts. Or none that couldn't be relieved by adjusting the config file in IL-2. After that date I began to see the blocky text which is only eliminated by using the earlier atioglxx.dll. So overclocking is not a part of the issue.

B

He was simply making a point Brando. He was not saying these text issues are related to OC'ing.

Ah OK, I misread the post. Sorry.

B

NP man, easy to do here.

S!

Yes, as Coastie said. Not blaming OC for problems in IL-2 as they are clearly driver related issues. OC just can make system more prone to errors and other anomalies in some cases. That was my point.

AMD's ATI 10.3a Catalyst Driver Update "17-March"
 

Hello Guys !

Question of the Day :

Will the ATI 10.3a includ IL2 fix ?

S!

Good news! So today have to check the Release Notes of the official 10.3's if IL-2 is included as in fixed. I still would guess these fixes are maybe at earliest in 10.4's. But shall see, another exciting wait ahead today! I did drop 9.10 version atoglxx.dll in IL-2 folder while using 10.3 previews..no problems and FPS ranged from minimum 25fps up to 308fps maximum in Black Death :D

S!

Catalyst 10.3a do not fix blocky text in IL-2. Performance of these drivers is good though, even noticed a strange thing when comparing them with and without atioglxx.dll in IL-2 folder. Results below on 1920x1200, Perfect settings.

10.3a with 9.10 dll file in IL-2
Min 22fps Max 304fps Avg 95fps

10.3a without dll file in IL-2
Min 22fps Max 284fps Avg 95fps

So we still have to wait a bit, maybe in 10.4's. And now with these drivers, file the feedback form again ;)

Do you mean with Catalyst 10.3a the Preview Version from February or the new Catalyst 10.3 Preview Version of this month?

S!

The 10.3a drivers released 17th of March :)

Jep, I saw this to late… Thanks for the "NCIS – Gibbs back of the head slap" ;)

So never mind. :rolleyes:

http://sites.amd.com/us/underground/...3-preview.aspx

the 10.3a Beta only say for Vista/Win7

** WinXP is not in here..

wth??

geeesh

S!

Ramstein, on 26th of March the official 10.3's will include support for WinXP. Do not worry :)

Best Quality Settings for ATI Radeon HD3000 series and later:

[Render_OpenGL]
TexQual=3
TexMipFilter=3
TexCompress=0
TexFlags.UseDither=1
TexFlags.UseAlpha=0
TexFlags.UseIndex=0
TexFlags.PolygonStipple=0
TexFlags.UseClampedSprites=0
TexFlags.DrawLandByTriangles=0
TexFlags.UseVertexArrays=0
TexFlags.DisableAPIExtensions=0
TexFlags.ARBMultitextureExt=1
TexFlags.TexEnvCombineExt=1
TexFlags.SecondaryColorExt=1
TexFlags.VertexArrayExt=0
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=17
Water=2
Effects=2
ForceShaders1x=0

PolygonOffsetFactor=-0.0625
PolygonOffsetUnits=-1.0


Recomended CCC Settings:

Anti Aliasing on Highest settings (edge detect 12x).
Anisotropic Filtering at Aplication Controled.
Catalist A.I. Disabled
Detaillevel Mipmap at Max Quality
Vertical Refreshing (Vsync) at Off/Aplication Controled.
Adaptive Anti-Aliasing Enabled (has a big impact on FPS so i usualy recomend to Disable it).
OpenGL Triple Buffering Enabled.

Note:
TexFlags.UseVertexArrays=0 and TexFlags.VertexArrayExt=0 are 2 Settings that have to be Disabled ("0") for ATI Radeon HD cards!
Just like TexFlags.TexEnvCombine4NV=0, TexFlags.DepthClampNV=0, and TexFlags.TextureShaderNV=0 wich are nVidia only settings.
Water=2 is the Highest setting for ATI, but that looks atleast as good as Water=3 for nVidia cards if not better.

S!

Tweaked a bit with effects etc. Testing their impact on FPS. With 10.3a + 9.10 dll in IL-2 root got the following performance on my settings posted here. Track is Black Death.

Minimum 27fps
Maximum 313fps
Average 103fps

So ATI is getting there :)