[BUG REPORT] 3d rendering polygon glitches in COD4 with 180.35 and above

[rockob]

I get weird rendering glitches (extra polygons) when playing COD4 under wine if I use nvidia 180.35, 180.37, 180.41, or 185.13. See the attached jpg for an example, which is supposed to show a couple of cars. The first level is unplayable, as it renders the screen as three polygons in slightly different shades of gray.

The glitches only occur when I run it at the screen's native resolution (1680x1050), not in the next resolution down. It does it whether in full screen or in a window, with or without compiz running. It is consistent, and the GeForce 8600M GT nvidia card is running at normal temperatures (typically 57C-70C).

The graphics render fine with nvidia 180.29 and earlier using the same xorg.conf settings. So the regression first occurred in 180.35.

I've tried combinations of these drivers on Ubuntu 8.10 with both kernel 2.6.27-14-generic amd64 and 2.6.28-11; and Ubuntu 9.04, kernel 2.6.28-11 and the results are the same. I've tried different versions of wine (1.1.12 and the latest from git) and the results are the same.

The glitches seem to have improved slightly with 180.41. The attached cars image was generated with 180.41 - with 180.37 and 185.13 you can't even recognize that they are cars.

Any ideas?

[rockob]

The 180.44 driver is a considerable improvement, but the regression is still there. The attached image of the start of level one shows this: in 180.35-180.41, the screen was drawn as three gray polygons - it's now closer to what it should be, but there are still some obvious polygon glitches.

[rockob]

I was mistaken about the improvement in the 180.44 driver; there's simply a certain element of randomness to the glitches. The attached image shows 180.44 rendering the gray screen for level 1.

So the regression definitely happened between 180.29 and 180.35. I wonder what might have been the change that caused it?

[rockob]

185.19 suffers from the same problem as well.

[proskelley]

I am also experiencing the same issues with CoD4 running under WINE 1.1.19.
System information is as follows:
Ubuntu 8.10
nVidia Corporation G73 [GeForce 7600 GS] (rev a2)

[Dizzle7677]

Originally Posted by proskelley

I am also experiencing the same issues with CoD4 running under WINE 1.1.19.
System information is as follows:
Ubuntu 8.10
nVidia Corporation G73 [GeForce 7600 GS] (rev a2)

File a bug report with Wine. http://bugs.winehq.org

This sort of odd stuff started to show up with v1.1.19 in Oblivion also but I'm too lazy to file one myself.

[proskelley]

I was able to resolve it with a ridiculous amount of settings in my xorg.conf and my user.reg file under Direct3D. I hope this helps someone.

xorg.conf:

    
    Option "RenderAccel"               "True"
    Option "NoLogo"                     "True"
    Option "NoRenderExtension"          "False"
    Option "TripleBuffer"               "True"
    Option "OnDemandVBlankInterrupts"   "True"
    Option "AllowGLXWithComposite"      "True"
    Option "AddARGBGLXVisuals"          "True"
    Option "AllowSHMPixmaps"            "1"
    Option "AddARGBGLXVisuals"          "True"
    Option "AllowGLXWithComposite"      "True"

user.reg:

"DirectDrawRenderer"="gdi"
"OffscreenRenderingMode"="fbo"
"PixelShaderMode"="enabled"
"SoftwareEmulation"="enabled"
"VertexShaderMode"="hardware"
"VideoMemorySize"="512"

[rockob]

Hey, thanks, proskelly! Including those settings in xorg.conf fixed the problem for me (I'm using 185.19 at the moment).

For performance reasons, I already had all of those user.reg settings except for "DirectDrawRenderer"="gdi" - I left it out when I tested and still ran glitch-free.

Perhaps what has happened is that the defaults have changed for these settings from 180.35 onwards, so they need to be set manually now?

[proskelley]

I did eventually turn off TripleBuffer due to tearing in SDL based emulators and games, specificly zsnes and sdlmame. Also, I switched from the default gdi setting in WINE to opengl to get more "native" performance.
I can only guess about the default settings, but I'm glad my extensive configuration efforts helped you as well. It took forever for me to get the right balance of those options.