Jaggy shores
#1

I know there's been a hundred threads about this, but I can't find any of them. My Il2 runs great, except for those jaggy shorelines. What should I do?
I run Il2 at 1280x1024, (the native resolution of my screen is 1600x1200.

I have a 8800GT 512.

my conf.ini:


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

and

[Render_OpenGL]
TexQual=3
TexMipFilter=2
TexCompress=0
TexFlags.UseDither=1
TexFlags.UseAlpha=0
TexFlags.UseIndex=0
TexFlags.PolygonStipple=1
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=0
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=2
LandShading=3
LandDetails=2

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

VideoSetupId=17
Water=2
Effects=1
ForceShaders3x=1

PolygonOffsetFactor=-0.15
PolygonOffsetUnits=-3.0
ForceShaders1x=0


Many thanks in advance!
Reply
#2

reflected, do you have a screenie of the effect you're talking about?
i'm sure that this issue was addressed with the release of a new set of dll's for IL-2. do a search for dll's, you'll probably find it. there was a d/l floating about here with 5 different sets of dll's in it. if you can find it, try to use those, and see what happens. the more recent ones, i'm sure, did address this issue with some systems.
having a look at your specs, i'm wondering why you don't run it in 1600x1200? - you're doing yourself an injustice running in the lower-res.
one thing you could change in your conf, is the LandGeom=2 setting, in the Render_OpenGL part. Try this with a 3 value, for much improved visibility distances.
Good luck in getting it sorted. Big Grin
Reply
#3

bigbossmalone Wrote:one thing you could change in your conf, is the LandGeom=2 setting, in the Render_OpenGL part. Try this with a 3 value, for much improved visibility distances.

Something to bare in mind - pretty sure changing from LandGeom=2 to LandGeom=3 will revert straight back to 2 if you don't have 4.09 DLL's so pays to get them 1st.
Reply
#4

yep, nzwilliam is absolutely right on that one... :wink:
Reply
#5

bigbossmalone Wrote:i'm sure that this issue was addressed with the release of a new set of dll's for IL-2. do a search for dll's, you'll probably find it. there was a d/l floating about here with 5 different sets of dll's in it. if you can find it, try to use those, and see what happens. the more recent ones, i'm sure, did address this issue with some systems.
having a look at your specs, i'm wondering why you don't run it in 1600x1200? - you're doing yourself an injustice running in the lower-res.
one thing you could change in your conf, is the LandGeom=2 setting, in the Render_OpenGL part. Try this with a 3 value, for much improved visibility distances.
Good luck in getting it sorted. Big Grin

Nah. Sorry to say that, but 4.09DLL,s and 1C DLL,s didn't adress this issue. It's present in coastlines and shorelines, over all at low altitude. You can test the five DLL,s launched, and you will see the effect stays.

The only way I got to eliminate this effect was with supersampling antialiasing through Nhancer (you cannot select this sort of AA through the Nvidia driver control panel, it's only Multisampling). But with SSAA (x16SSAA, for example) the most of rigs fall at their knees.

I live with it.

My rig:

- C2D E8400 @ 4.0Ghz.
- 2*2Gb GSKILL @ 1066Mhz
- Gigabyte X48 DS4
- Nvidia GTX295 @ 675/2100
- Audigy SE
- TX 750 Corsair

Regards.
Reply
#6

Wilhelm, if what you say is true, then i would really like reflected to post a screenie of this, because i haven't had that problem for a long time now.
I have used nHancer in the past, but i can't say that it made any difference to my coastlines...
i think, just so we don't start arguing about it, it would really be good to see a screen of exactly what reflected is talking about?
i'm using a GeForce 9800GT w/512MB, almost all settings maxed via nVidia control panel (Windows 7 RC), for what it's worth. 8)
Reply
#7

bigbossmalone Wrote:I have used nHancer in the past, but i can't say that it made any difference to my coastlines...

Of course. Only using nHancer you aren't going to see any difference. You have to switch to SSAA (enabling one of the supersampling modes).

This is a very old issue. There are hundreds of threads in SimHQ, UBI, etc. If you don't know about what issue we are talking, better for you.
Reply
#8

Oh sorry, the native resolution is 1280x1024 so I guess I'll leave that one as it is.

So the to do list is:
-look for new dll files (where exactly? which one should I install)?
-change the landgeom setting to 3.

it it's still not OK, I'll post some screenshots.
Reply
#9

ok, found a link to them: (The link is inoperative)
just use the most recent set in the rar, or try others until you are happy.
i know full well of the effect, its an old il-2 issue, as Wilhelm said. thing is, the fixes you find on the net do not necessarily work for everyone. so, what worked for Wilhelm, didn't work for me. BUT - i haven't had jaggy coastlines for a LONG time now, that was the only reason i asked for a screenie, just to make sure that what you're seeing is what i think it is.
Maybe i'm just lucky - so i'll leave well enough alone. :wink:

so yes - try the dll's, and then change Landgeom=3, and let us know how that goes for you.
Reply
#10

Blimey, I copied the new dlls, and my game doesn't even start! Not even when I copy the original dlls back again! What's going on?
Reply
#11

reflected Wrote:Blimey, I copied the new dlls, and my game doesn't even start! Not even when I copy the original dlls back again! What's going on?

You have done anything wrong. A lot of us are using these DLL,s with 4.09b or 4.08 version without any problem.

Try to discover where is your mistake.
Reply
#12

Ok, it works. something set the resolution back to 640x480...

however, these dlls didn't solve the issue entirely:

the shorelines are still shimmering and jaggy, especially at large FOV:

[Image: grab0000q.jpg]

I'm using the newest (2_core_dll_090208), I even tried the renaming trick, but no improvement.
I use vertical sync and tripple buffering on, and AA 16x, anisotropic filtering: 16x
FPS: around 70-90.
Reply
#13

There is support for Transparent Anti-Aliasing (Adaptive) w/ the new DLL's, and although it works, it will bring your system to it's knees, especially if your usin' high-res cockpits! I've confirmed it for both the X1950XTX and the HD 4890, but it should work on any NVIDIA GPU w/ Adaptive Anti-Aliasing support.
Reply
#14

Hi, Reflected. Most of this is way over my head. So I hope I am not out of line. I don;t even know what the dlls are or do. Anyway..others have spoken of changing landgeom setting to 3. You mentioned it but have you tried that yet?

This is a shot with my system on 2...and the second shot on 3. Same GPU settings, and nothing else different. Notice the jagged edges on the river banks with setting 2. Smooth on 3.


[Image: il2fb2009071415173983.th.jpg]
[Image: il2fb2009071415233741.th.jpg]
Reply
#15

ok, i've seen a few more differences between your conf.ini and mine.
from yours:

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

VideoSetupId=17
Water=2
Effects=1
ForceShaders3x=1

PolygonOffsetFactor=-0.15
PolygonOffsetUnits=-3.0
ForceShaders1x=0

now mine:

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

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

PolygonOffsetFactor=-0.15
PolygonOffsetUnits=-3.0

i notice that you seem to have an extra 'ForceShaders' line at the end. now, i'm not sure about that. mine doesn't,and never has, had the extra line in it.
that could be an issue as well, but like i said, i'm not 100% sure on this. anyway, no harm in trying to see what happens if you change it, long as you keep 'ye olde backup' somewhere.... :wink:
Reply


Forum Jump:


Users browsing this thread: 10 Guest(s)