Anyone with problems with ATI drivers read this.

[Qpassa]

good news,thanks coastie

[Flanker35M]

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.

[=PF=Coastie]

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.

[Flanker35M]

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

[=PF=Coastie]

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.

[Brainless]

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 ()

[window]
width=1280
height=1024
ColourBits=32
DepthBits=24
StencilBits=8
ChangeScreenRes=1
FullScreen=1
DrawIfNotFocused=0
EnableResize=0
EnableClose=1
SaveAspect=0
Use3Renders=0

[GLPROVIDER]
GL=Opengl32.dll

[Render_OpenGL]
TexQual=3
TexMipFilter=3
TexCompress=0
TexFlags.UseDither=0
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=0
TexFlags.TexCompressARBExt=0

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

HardwareShaders=1

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

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

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

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

PolygonOffsetFactor=-0.15
PolygonOffsetUnits=-3.0

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.

[=PF=Coastie]

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!