Created attachment 3753 [details]
Fix for fragdata GLSL error

Created attachment 3754 [details]
BF2 main graphical anomalies (ARB hardware shader mode)

What graphics card / drivers are you using? I know that at least the current
nVidia BETA drivers have a slightly stricter GLSL compiler, which doesn't like a
couple of things we do. I've got patches for those issues, and will submit them
later today.

As for the cursor issue, I've got a set of working patches for that as well, but
unfortunately it doesn't look like it will be applied in the short term.

The stuff on the top of the screen is related to offscreen rendering, I'm
working on that.

Video card / drivers are: Geforce 6800XT / OpenGL 2.1.0 NVIDIA 96.25. I suppose
it wouldn't hurt to try with the other drivers.

There's also a D3D format warning issued on start, though I have no idea if it's
actually important or not.

fixme:d3d:debug_d3dformat Unrecognized 1178752590 (as fourcc: NVBF) D3DFORMAT!
fixme:d3d:getFormatDescEntry Can't find format unrecognized(1178752590) in the
format lookup table

Yes, those are the beta drivers I was talking about, the stable drivers
shouldn't have these issues (the issues are in wine, but the older GLSL compiler
is a bit more forgiving). The warning about the NVBF format should be harmless.

The GLSL errors should be fixed in current git. The offscreen rendering will be
a bit harder to fix.

Created attachment 3894 [details]
Battlefield 2 without the 'overhang' graphical anomaly

If I change 'pbuffer_support' and 'pbuffer_per_surface' variables in
dlls/wined3d/device.c to TRUE, the major 'overhang' anomaly (which shifts due to
perspective as well, taking up more of the screen as you pan down) is no longer
there, and just the ground texture(s) are missing.

Yes. The problem here is that in D3D the depth buffer can be shared between an
offscreen and onscreen surface, and in wine we currently can't. That causes the
sky to be drawn over the terrain, giving the invisible terrain. I've got some
patches that fix this issue in my local tree, but at the moment they break a lot
of other things, and the performance is unacceptably slow.

Current git has a registry setting
"HKCU/Software/Wine/Direct3D/OffscreenRenderingMode" to select the offscreen
rendering mode. Setting that to "fbo" should fix the invisible terrain and the
garbage in the sky. It will probably take a while before that becomes the
default though.

I tested it with the demo, and it works perfectly, even at high detail.

Still present with current GIT. Using OffscreenRenderingMode fbo doesn't help at
all. Not quite as bad but it still happens with terrain that isn't close to the
player. The game is also unplayably slow.

Not major, reclassifying.

I'm not sure if that's the same issue or something different.

Hello there, I don't know if I should bother you all with this, but I've got BF2
working reasonably with wine and got the same anomalies as mentioned in this
bug. Since I've played this game too much I'm pretty certain the strange sky
'overhang' is in fact some kind of overlay texture for the ground. It occured to
me because where there should be mountains visible on the horizon there are
instead strange bumps in the sky 'overhang'. And also when the 'overhang'
touches the place where there should be a ground, it shortly becomes visible..... 

That's why it shifts down when you look down and disapears when you look up.
(It's the horizon that's moving upside down). So my guess is if wine is able to
map this texture on the ground where it should be, there will be a lot of
improvement in the complete look of BF2. Maybe even make it playable. Bu I have
no idea in which feature/API-call this would have to be fixed.

Since I am completely new to the source in wine I have no patch, but I will try
to look into this now. 

As mentioned in a previous comment, the OffscreenRenderingMode setting should
fix that. The issue Enverex describes may be related, but it should probably be
a separate bug.

Ah, so the sky overhang should be a separate bug? Because that one is definitely
a matter of some ground visibility-overlay-texture (I don't know what it should
be called) being mapped upside down. It's the cause of the anomaly in the image
that is attached to this bug. Mapping it correctly will also surely make the
ground appear normally. And I don't think it is a matter of setting the
offscreen rendering mode correctly, because that won't change the way that this
specific texture is drawn (right?).

But if it should be a separate bug, just let me know. Also if I can help, I'll
do what I can. (I've got pretty new hardware, so testing some stuf won't be a
problem)

Cheers,

No, that's not a texture. Currently wine uses the backbuffer for offscreen
rendering by default, and the "texture" you see in the sky is stuff left over
from that. As mentioned in comment #10, in d3d you can share the depth buffer
between onscreen and offscreen rendering modes, which is required for the
terrain to be visible. When using the backbuffer for offscreen rendering the
depth buffer is in fact shared, but not in the right way, that's why the stuff
in the sky is upside down and the ground becomes visible when they touch
eachother. When using FBOs for offscreen rendering, we *can* share the depth
buffer in the right way, which is why it works there. Note that BF2 is currently
affected by a regression that prevents it from starting though (bug 7443]).

Just an update with pre0.9.36...

Using FBO mode makes the game too slow to use, it renders at about 0.2fps, maybe
less. Using whatever is default causes a giant texture to cover everything as
you look down. The more you look up the more it disappears (but you can't run
around looking at the sky else you can't see what you're doing anyway).

Created attachment 5953 [details]
Covering texture issue

any progress on the "but mouse cursor does not appear" part of this bug report?

with OffscreenRenderingMode set to pbuffer I get only the missing ground
texture. with backbuffer, I get the giant ugly thing in the sky and the missing
ground texture. With fbo, everything is black, and at an unplayable fps.

What's interesting to note, that I discovered while using pbuffer, is that when
the blurry vision starts (from "shellshock") everything is fine, the ground
textures are there, the mountains and sky are clearly visible and normal,
everything looks perfect, except for the blurry vision and ringing ears :) Once
the effect fades away, it all goes back to the way it was before, with no ground
texture.

this is all on wine 0.9.40 though.

small update: I just compiled 0.9.41 from source with the fragdata GLSL error
patch, and now fbo looks completely perfect, but still at an unplayable fps.
Everything else is still the same.

(In reply to comment #9)
> If I change 'pbuffer_support' and 'pbuffer_per_surface' variables in
> dlls/wined3d/device.c to TRUE, the major 'overhang' anomaly (which shifts due to
> perspective as well, taking up more of the screen as you pan down) is no longer
> there, and just the ground texture(s) are missing.

Where do I find that file?

(In reply to comment #24)
> 
> Where do I find that file?
> 

it's part of the wine source code.

Created attachment 8587 [details]
Battlefield 2 with Wine 0.9.47 and default Wine settings.

Just showing the current state with unchanged Wine renderers (i.e. as Wine is by default).

Still the same in current Wine GIT (0.9.56+).

Still same issues with 0.9.60 and backbuffer rendering. With OffscreenRenderingMode set to fbo the game fails to even start.

Sorry, I meant pbuffer there. With fbo the game does start, but plays very slowly (about 15fps) and everything is black, only 2D elements and light coronas are drawn.

Ok, I think I've found something interesting:
I'm using Ubuntu 8.04 and wine 1.0RC2

I tried to play BF2 (dynamic shadows and lightning disabled).
Then I created a game against bots...in the match, a tank fired at me (you know the screen is bleary etc.)
And...while the screen was blearing, I had a "normal" screen!
No graphical bugs or something like that, just as it should be

Look at the attachment I created!

Created attachment 13406 [details]
screenshot just after a tank shooted in my direction

ok, I could repoduce it with the "standard" grenade and the grenade thrower of the assault soldier
-> http://img84.imageshack.us/img84/5387/bildschirmfoto1eh8.png
-> http://img84.imageshack.us/img84/6656/bildschirmfoto2xa8.png

when your player is "normal" again, the screen has the same graphic bugs again...

Could you give this a try with current git and FBO ORM?

I don't know what ORM is (or where I can set it) but I've set the shader thing to fbo...and in wine1.1.0 it works :)

yeah...the performance isn't like it is under Windows...but it works, I think the bug is fixed...

(In reply to comment #34)
> I don't know what ORM is (or where I can set it) but I've set the shader thing
> to fbo...and in wine1.1.0 it works :)
> 
> yeah...the performance isn't like it is under Windows...but it works, I think
> the bug is fixed...
> 

How do I use the current git, what is git? I have this issue too. I'm using wine 1.0.0 and setting the shader to fbo does fix this but makes the game unplayable due to such low frame rates.

Created attachment 14612 [details]
some problems remain

(In reply to comment #33)
> Could you give this a try with current git and FBO ORM?
> 

Works for me with the demo, the overhang and transparent ground have gone.  Now, when panning the view around there are some black spots on the ground where there should be a texture and some odd dots and thin black lines elsewhere.  Screenshot attached.  NVIDIA 100.14.19, GeForce 8800.

confirming that the issue Jeff Zaroyko describes, and as indicated in the working screenshot he has attached, still exists as of today's git.  using FBO ORM.

I'm using 32bit Ubuntu Hardy Heron, wine 1.1.7. I installed BF2 just fine without errors, installed some windows libraries for direct 3D (found out how to do it from here http://vostrolinux.blogspot.com/2007/11/setting-up-battlefield-2.html )

Battlefield 2 Boots up just fine, I of course don't have a mouse cursor, but I am able to start a single player game. Game works, but I have the "overhang/blob/shader anomaly/cloud/sky glitch" This renders the game unplayable. I try the registry Direct3D "fbo" fix. It renders my game unbootable-- the EA video plays, then after ~3 seconds, the video/application hangs indefinitely.

I'm guessing the Direct3D "fbo" fix worked in an earlier version of wine, but not in 1.1.7? Can anyone confirm this so I have some valid reason to try an earlier version? If it is my version of wine, can I have some info on what version works best with BF2?

I cannot confirm this for BF2 (haven't tried it) but for many other games (CS:S/TM:N) I've the same result: Using fbo makes the games hang.

So yes, there is a problem with fbo in wine 1.1.7

(In reply to comment #39)
> I cannot confirm this for BF2 (haven't tried it) but for many other games
> (CS:S/TM:N) I've the same result: Using fbo makes the games hang.
> 
> So yes, there is a problem with fbo in wine 1.1.7
> 

I can confirm this for BF2, with latest git, geforce 8, 177.80.  With fbo glibc prints a message about corrupted double linked list.  With backbuffer it goes further.

Created attachment 17456 [details]
anomalies in wine 1.1.9

Confirmed for wine 1.1.9

Created attachment 17491 [details]
Log using wine 1.1.9, additional: d3dx9_24, _25 und _36, fbo enabled

Created attachment 17492 [details]
Log using wine 1.1.9, additional: d3dx9_24, _25 und _36, fbo enabled

*** Bug 7044 has been marked as a duplicate of this bug. ***

(In reply to comment #36)
> Created an attachment (id=14612) [details]
> some problems remain
> 
> (In reply to comment #33)
> > Could you give this a try with current git and FBO ORM?
> > 
> 
> Works for me with the demo, the overhang and transparent ground have gone. 
> Now, when panning the view around there are some black spots on the ground
> where there should be a texture and some odd dots and thin black lines
> elsewhere.  Screenshot attached.  NVIDIA 100.14.19, GeForce 8800.
> 

Same deal with wine-1.1.9-301-gbbac6de, nvidia drivers 180.06

Removing deprecated CVS/GIT version tag. Please retest in current git. If still present, update version field to earliest known version of wine that had this bug. Thanks!

Created attachment 18848 [details]
Graphics bug in Wine 1.1.13 / 1.1.12

Hi,

The battlefield 2 game is working in Wine versions before the ani cursor support (no specific old version though).  After I upgraded to 1.1.12 and 1.1.13, the game graphics is corrupted after a while during playing.  I have attached the screenshot.

Thanks in advance for the help.

Latest Git Version 1.1.14

With OffscreenRenderingMode=fbo the Game its looks like the Attachment in previous Comment. 

With OffscreenRenderingMode=backbuffer the Game looks like the same Attachment but with black Sky. If you look up the Sky looks perfect but if you look down all will change to black. 

The Ground texture will gone when you spawn again or have nearly an explosion.

When an explosion occoured nearly you and you didnt die for seconds the graphics are perfect. When youre normal again the graphics will be bad like before.

I have recompiled git from source using tag wine-1.1.4 and there was no graphics problem, e.g., the sky or terrain is not corrupted.

Using git tag wine-1.1.5, the graphics corruption was reproduced.  Tag was dated Sept 19, 2008.  The following commits are likely responsible for the graphics corruption (related to fbo):

wined3d: Create a FBO for each combination of render targets and depth stencil.

wined3d: Get rid of context_set_depth_stencil_fbo().

wined3d: Get rid of context_set_render_target_fbo().

wined3d: Handle drawbuffers in context_apply_fbo_state() instead of context_set_render_target_fbo().

Still present in Wine 1.1.15 but it wasn't immediate. The game seemed ok for about a minute then suddenly the floor and other textures disappeared causing it to look exactly the same as the previously reported issue.

(In reply to comment #50)
> Still present in Wine 1.1.15 but it wasn't immediate. The game seemed ok for
> about a minute then suddenly the floor and other textures disappeared causing
> it to look exactly the same as the previously reported issue.
> 
Exactly the same problem for me with Wine 1.1.18 on an ATI4850 with fglrx 9.3
Another strange thing is that tanktextures never show up, while other vehicles don't have this problem. The textures seem to return when stunned.

Another strange graphical glitch is that groundtextures in the distance look overbright yellow, when you get closer the normal looking groundtexture pops in.

(In reply to comment #50)
> Still present in Wine 1.1.15 but it wasn't immediate. The game seemed ok for
> about a minute then suddenly the floor and other textures disappeared causing
> it to look exactly the same as the previously reported issue.
> 
Exactly the same problem for me with Wine 1.1.18 on an ATI4850 with fglrx 9.3
Another strange thing is that tanktextures never show up, while other vehicles don't have this problem. The textures seem to return when stunned.

Another strange graphical glitch is that groundtextures in the distance look overbright yellow, when you get closer the normal looking groundtexture pops in.

(In reply to comment #49)
> I have recompiled git from source using tag wine-1.1.4 and there was no
> graphics problem, e.g., the sky or terrain is not corrupted.
> 
> Using git tag wine-1.1.5, the graphics corruption was reproduced.  Tag was
> dated Sept 19, 2008.  The following commits are likely responsible for the
> graphics corruption (related to fbo):
> 
> wined3d: Create a FBO for each combination of render targets and depth stencil.
> 
> wined3d: Get rid of context_set_depth_stencil_fbo().
> 
> wined3d: Get rid of context_set_render_target_fbo().
> 
> wined3d: Handle drawbuffers in context_apply_fbo_state() instead of
> context_set_render_target_fbo().
> 

I can confirm that BF2 (Complete Colection updated to 1.41 patch) works OK under Wine 1.1.4 but not in previuos versions !!! they work in previous version till you respawn and/or be severely injured or killed...with Wine 1.1.4 works OK w/o this problem....only thing is that textures must be set to low or else you get some black holes in the ground....the other issue is some black lines...BTW, how can i attach an image to show the results ?!?, TIA, AJSB

Created attachment 20661 [details]
black lines

notice that black lines don't affect all ground....only "dirt" ground shows black lines....this is Wine 1.1.4 under Slackware 12.2 with NVIDIA driver 180.44

ooops ....in my 1st comment i meant that all versions after 1.1.4 won't work at all...ground texture completly messed AFTER 1st respawn and/or when seriously injured (after the "shake" (during which the graphics are actually quite good !!!))

Created attachment 20674 [details]
ARB_framebuffer_object support

Does this patch improve things (with FBO ORM)?

(In reply to comment #56)
> Created an attachment (id=20674) [details]
> ARB_framebuffer_object support
> 
> Does this patch improve things (with FBO ORM)?
> 

Is that patch for a specific version of wine or works (In reply to comment #56)
> Created an attachment (id=20674) [details]
> ARB_framebuffer_object support
> 
> Does this patch improve things (with FBO ORM)?
> 

Sorry i'm, kinda of a newbie about apply patches :D
This patch is for a specific version of wine or not ? 
how can i apply it ? (i.e. what folder and what is the complete comand line to apply it before compilation...and can i still use the standard ./tools/wineinstall to procede with compilation and instalation ?)

TIA,
AJSB

Does the demo http://www.jeuxvideopc.com/demo/7817-battlefield-2.php show the same problem?

http://wiki.winehq.org/Patching

(In reply to comment #58)
> Does the demo http://www.jeuxvideopc.com/demo/7817-battlefield-2.php show the
> same problem?
> 

Last time I tested, comment #45 the demo showed the same problem.

OK, i mannaged to apply the patch to WINE 1.1.19  and now the ingame graphics are as good as with version 1.1.4 , w/o the need for any extra dlls  and w/ cursors working (which wasn't true for 1.1.4) :)
Only thing( just like with version 1.1.4) is the black holes if you try ground textures above low and the random dots and black lines that i posted a pic show of version 1.1.4 are still present...but now we can die/respawn w/o problems finally :)

I notice that there is a new wine 1.1.20, does it needs also this patch, and if so, is this patch compatible with it or we will need a new version for wine 1.1.20 ?

TIA,
AJSB

Created attachment 20690 [details]
A small new bug...the sideway "white ghost" ! :))

When choosing overall quality to high BUT replacing resolution of it to 1280x1024, this is what happens....with resolution fo 1280x1024 and OQ set to medium also happens....notice that with overal quality set to low at 1280x1024 DOESN'T happen and also doesn't happen with OQ set to medium or high and resolution set to 800x600.

To be honest i'm not too worried with this bug (yet)  because finally this last patch solved all transparent ground  problems in any circunstances including respwn,etc. and this bug doesn't show with oq set to low which  is the  way game plays faster anyway....what i really wanted now, if possible, was to get rid of those black spots/lines in all quality settings and black holes in ground textures (it's the first  setting about textures in the menu (top option about textures) that triggers the black holes) everytime that it's set above low...and to know if patch is compatible with wine 1.1.20 :D


AJSB

PS: notice however that my screen is also set to resoltion of 1280x1024 so i wonder if this bug is a side effect of to try make a window of 1280x1024 in a screen with 1280x1024 pixels of resolution....

AJSB

(In reply to comment #45)
> (In reply to comment #36)
> > Created an attachment (id=14612) [details] [details]
> > some problems remain
> > 
> > (In reply to comment #33)
> > > Could you give this a try with current git and FBO ORM?
> > > 
> > 
> > Works for me with the demo, the overhang and transparent ground have gone. 
> > Now, when panning the view around there are some black spots on the ground
> > where there should be a texture and some odd dots and thin black lines
> > elsewhere.  Screenshot attached.  NVIDIA 100.14.19, GeForce 8800.
> > 
> 
> Same deal with wine-1.1.9-301-gbbac6de, nvidia drivers 180.06
> 

(In reply to comment #56)
> Created an attachment (id=20674) [details]
> ARB_framebuffer_object support
> 
> Does this patch improve things (with FBO ORM)?
> 

Tested with the demo and Henri's patch applied to 1.1.20, 180.44, there are still sections of the ground missing as per comment #45

Yes, i allready told that Jeff...but that only happens when you set in the VIDEO options the option "TERRAIN" to anything above "Low"...if it's set to "low" the black holes are not present....notice that most important thing about this patch, that it really solves, was the fact that w/o it , in wine versions above 1.1.4, as soon as you repawn or was severely injured , no matter the settings you end up with screen with a happearance like in comment  # 3 and similar.

This new patch solves once and for all that problem...

AJSB

(In reply to comment #65)
> Yes, i allready told that Jeff...but that only happens when you set in the
> VIDEO options the option "TERRAIN" to anything above "Low"...if it's set to
> "low" the black holes are not present....notice that most important thing about
> this patch, that it really solves, was the fact that w/o it , in wine versions
> above 1.1.4, as soon as you repawn or was severely injured , no matter the
> settings you end up with screen with a happearance like in comment  # 3 and
> similar.
> 
> This new patch solves once and for all that problem...
> 
> AJSB

I'm still running into this bug. I am running git 1.1.20 nvidia 180.44. I have all my graphics settings to low at resolution 800x600. I have applied the patch by henri. But it doesn't seem to solve the problem.

The bug has manifested itself in version 1.41 and 1.50 beta

Wine-1.1.21 patched with  "ARB_framebuffer_object support"
GFX NV GF 9xxx on 185.18.14
ORM=fbo

I would like to inform that overriding antialiasing (in nvidia-settings) to at least 2x solves the black lines problem (from Comment #54). Hope it helps :)

*** Bug 19886 has been marked as a duplicate of this bug. ***

Created attachment 23336 [details]
screenshot

Hi,

I have wine 1.1.28 installed and see problems with the graphics in BF2.

Video Card: NVidia PCI-E 8800 GTS
Nvidia Driver version: 185.18.36
Linux kernel: 2.6.30.5 (x64)

Please see attached screenshot. What can I do to remedy the issue?

How does this work in current git?

(In reply to comment #71)
> How does this work in current git?

Can't see any changes, looks the same as comment #64 with wine-1.1.31 
OpenGL renderer string: GeForce 8800 GTS/PCI/SSE2
OpenGL version string: 3.2.0 NVIDIA 190.29

I just tried the game again after installing Ubuntu 9.10.
The bug is gone. I had no graphic bugs that I could see.

(In reply to comment #73)
> I just tried the game again after installing Ubuntu 9.10.
> The bug is gone. I had no graphic bugs that I could see.

Fixed.

(In reply to comment #74)
Whoa, one user which isn't reporter of this bug and didn't provide Wine, hardware, drivers version he used is able to make this bug closed? 
I would be more cautious, because to remove this bug you only need to set antialiasing to at least 2x as I mentioned earlier in comment #67

(In reply to comment #75)
> (In reply to comment #74)
> Whoa, one user which isn't reporter of this bug and didn't provide Wine,
> hardware, drivers version he used is able to make this bug closed? 
> I would be more cautious, because to remove this bug you only need to set
> antialiasing to at least 2x as I mentioned earlier in comment #67

Agreed, you'd think at least someone should have to independently confirm my statement. I don't know what my antialiasing was set to, can't recall ever touching that setting.

My wine is 1.1.32, though from git so may be any commit near there.
Nvidia acc. graphics driver version 185
NV43 [GeForce 6600 GT]
Full hardware profile: http://trezker.bafsoft.net/desktop_hardware.html

Unclear if this is actually fixed, reopening.  I saw comment 73 but ignored it because of lack of details.  I don't have the demo at the moment, so someone else is free to test and provide more detail.

This issue is also fixed for me. I'm using Ubuntu 9.10 with Wine 1.1.32 from the PPA. I have no graphical issues with BF2, and am using all settings on low at 1024x768 fullscreen with an Nvidia 6600 GT.

wine-1.1.32-260-gf222a16
OpenGL renderer string: GeForce 8800 GTS/PCI/SSE2
OpenGL version string: 3.2.0 NVIDIA 190.29

Downloaded the demo again, the issue is still present, same as comment 72 still.

(In reply to comment #79)
> wine-1.1.32-260-gf222a16
> OpenGL renderer string: GeForce 8800 GTS/PCI/SSE2
> OpenGL version string: 3.2.0 NVIDIA 190.29
> 
> Downloaded the demo again, the issue is still present, same as comment 72
> still.

FWIW, the issue in http://bugs2.winehq.org/attachment.cgi?id=14612 looks like depth buffer precision differences between the onscreen and offscreen depth buffer. I think this might only be a problem for GF8 and later cards.

I've just bought a new computer and I've gone from a 6600 GT to a 9600 GT. I can now see the same problems as in http://bugs2.winehq.org/attachment.cgi?id=14612 and http://bugs2.winehq.org/attachment.cgi?id=20661. Setting anti-aliasing to 2x in nvidia-settings does help but the graphics still aren't perfect. I can run with pretty high settings and get a good FPS though.

Created attachment 27283 [details]
Graphical / Flicker corruption in Windowed and Fullscreen Modes

In this image I cannot show it, but, cursors is corrupted, too.

Created attachment 31379 [details]
Battlefield 2 screenshot [Nividia 8800GTX (260.19.12) WINE 1.3.5]

Visual glitches (hatching in textures) present with latest WINE and Nvidia blob driver versions. (Black bars are not present in game and are due to frame refresh/capture).

Created attachment 31380 [details]
Battlefield 2 screenshot [Nividia 8800GTX (260.19.12) WINE 1.3.5]

Visual glitches (flicking blackening of texture surfaces in near to far distance) present with latest WINE and Nvidia blob driver versions. (Black bars are not present in game and are due to frame refresh/capture). NB this "bug" was present (as I recall) in an older Windows Nvidia driver when running the game natively under Windows 7 x64.

still a bug in current wine?

The glitches as seen in the screenshots from Robert and Adam still exist in 1.3.30.

Ubuntu 11.04 64-bit
Linux kernel 2.6.38-11
Nvidia driver 270.41.06
GeForce 9800 GTX+

(In reply to comment #86)
> The glitches as seen in the screenshots from Robert and Adam still exist in
> 1.3.30.
> 
That's essentially a driver bug, but the "AlwaysOffscreen" registry key can be used as a workaround.

(In reply to comment #87)
> (In reply to comment #86)
> That's essentially a driver bug, but the "AlwaysOffscreen" registry key can be
> used as a workaround.

That didn't work. What did work was setting Antialiasing to 2x (from off) in the game.

Sorry, it turns out they are completely different glitches, at least as far as the workarounds.

The "AlwaysOffscreen" workaround does work for the black lines all over the ground (as seen in Adam's screenshots), as does enabling AA.

To get rid of the flickering black hexagonal patches seen at mid-long distances (mostly visible in Robert's last screenshot), I had to set the terrain quality to low.

The flickering black hexagons in the ground are a game bug. They occur on my brother's Windows 7 machine with a AMD Radeon HD 4670 too.

(In reply to comment #90)
> The flickering black hexagons in the ground are a game bug. They occur on my
> brother's Windows 7 machine with a AMD Radeon HD 4670 too.

in that case, I'd say it could also be a AMD driver bug. (they seem to have problems with transparent things...look at current GnomeShell /w AMD's fglrx driver)

I see the black hexagons on Nvidia on Wine. I suspect that the issue is depthbias related. Getting the depthbias right in d3d is next to impossible.

"Black holes" in the ground is clearly a game bug that just happens to show up more in WINE...but in some circumstances also happens in Windows XP and more easily, in Windows 7...i know this for a fract because i tested in all those OS also.

Intel HD4000 Gfx (Core i7-3770)
Linux Kernel: 3.4.9
Intel Driver: 2.20.4
GLX version: 1.4
OpenGL version string: 3.0 Mesa 8.0.4
OpenGL shading language version string: 1.30
Wine Version: 1.5.11

In order for BF2 to run on Intel, I had to disable the "Dynamic Lighting" option in BF2, and set the "Lighting" option to no higher than Medium.  

Upon starting a game, the graphics are very very dark, as if the gamma were really low, almost unplayable because its too dark.

If I disable GLSL in the winereg, the gamma is still dark, but I can see a few more textures that were not visible (or too dark to see) previously.

Regarding the difference in textures with GLSL enabled and disabled.  I tried again, and I saw no difference in textures; however, on Intel gfx, the gamma is extremely low in BF2, making it almost unplayable, because everything is so dark and hard to see.

I'm pretty sure the original issue is fixed. Please open separate bugs for any remaining issues.

Closing bugs fixed in 1.7.13.