[Bug 11545] New: call of duty 4 stopped working around the time of 0.9.54( not fixed with 55)

http://bugs.winehq.org/show_bug.cgi?id=11545

Summary: call of duty 4 stopped working around the time of
                    0.9.54(not fixed with 55)
           Product: Wine
           Version: unspecified
          Platform: PC-x86-64
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

Created an attachment (id=10712)
 --> (http://bugs.winehq.org/attachment.cgi?id=10712)
error message

So around the time that 0.9.54 came out I lost COD4 on both my desktop 
and laptop. In order for it to work you have to compile wine with the 
3dmark patch, so I was using the git, but when that didn't work I tried 
52 and 54 tarballs. Thing is I know it worked with the 52 git and with 
the 52 tarball it still doesn't work, I've tried reinstalling all the 
depends even... I've tried using a completely fresh prefix. I've tried 
downgrading my nvidiadrivers(169.09) to 07 and to 100.14.19 on my 
laptop(desktop has a 8800GT) and everything else I could think of. Attached 
is the error log.
tried versions 1.3, 1.4 and 1.5 of COD4
Desktop:
gentoo 2.6.24-r1 amd64
athlon 3800 x2
8GBs DDR2-800 ram
8800GT (169.09 and 169.07)

Laptop:
gentoo 2.6.24 amd 64
turion 2.2GHz (think it's ML-40)
1GB ram(don't remember the specs)
7900GS (169.09, 169.07 and 100.14.19)

[Bug 11545] call of duty 4 stopped working around the time of 0.9.54( not fixed with 55)

http://bugs.winehq.org/show_bug.cgi?id=11545

James Hawkins  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|critical                    |normal
           Keywords|                            |regression
            Version|unspecified                 |0.9.54.

--- Comment #1 from James Hawkins   2008-02-10 19:46:26 ---
Then use git to run a regression test between 0.9.52 and 0.9.54.

http://wiki.winehq.org/RegressionTesting

[Bug 11545] call of duty 4 stopped working around the time of 0.9.54( not fixed with 55)

http://bugs.winehq.org/show_bug.cgi?id=11545

Rico  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #2 from Rico   2008-02-11 14:39:42 ---
The Demo starts and runs without trouble.

Wine 0.9.55 + 3dmark.patch
8800GTS (100.14.23)
OffscreenRenderingMode = fbo

Just disable Soften Smoken Edges and Field of depth otherwise there are graphic
glitches.

At the exit there is a stack overflow but it happens after you press quit ...
so this shouldn't be a problem.

[Bug 11545] call of duty 4 stopped working around the time of 0.9.54( not fixed with 55)

http://bugs.winehq.org/show_bug.cgi?id=11545

--- Comment #3 from Roderick Colenbrander   2008-02-15 17:58:54 ---
Please investigate which particular patch broke COD4 for that perform a
regression test as James indicated. We are very intested in this bug, further
it might not occur on all videocards (for a part it could be related to the
amount of video memory we report).

[Bug 11545] call of duty 4 stopped working around the time of 0.9.54( not fixed with 55)

http://bugs.winehq.org/show_bug.cgi?id=11545

--- Comment #4 from Matthew Clark   2008-02-16 04:08:37 ---
(In reply to comment #3)
> Please investigate which particular patch broke COD4 for that perform a
> regression test as James indicated. We are very intested in this bug, further
> it might not occur on all videocards (for a part it could be related to the
> amount of video memory we report).

oh, sorry, it sounded like I was the only person with this issue, so I figured
no one cared(no offense intended). I've since tried everything from the old
kernel with the tarball of 0.9.52 with 100.14.19("perfect" combo) and still
nothing. I'll will try to bisect it(though I've never tried that before, so I'm
not positive how it's going to work) and report back here. Thanks for your
interest^_^

[Bug 11545] call of duty 4 stopped working around the time of 0.9.54( not fixed with 55)

http://bugs.winehq.org/show_bug.cgi?id=11545

--- Comment #5 from Matthew Clark   2008-02-16 05:13:27 ---
Created an attachment (id=10806)
 --> (http://bugs.winehq.org/attachment.cgi?id=10806)
error message2

I got 2 other error messages that were basically the same(checked them with
diff), but with libs in different orders.

[Bug 11545] call of duty 4 stopped working around the time of 0.9.54( not fixed with 55)

http://bugs.winehq.org/show_bug.cgi?id=11545

--- Comment #6 from Matthew Clark   2008-02-16 05:13:55 ---
well, I wanted to just edit the last one, but no luck. Don't think the bisect
thing worked. After I patched dlls/wined3d/directx.c(I hard reset git and then
re-patch) like I have to it says:
Bisecting: 348 revisions left to test after this
fatal: Entry 'dlls/wined3d/directx.c' not uptodate. Cannot merge.
and after I built it and ran it and it crashed again and I tried to "wine
bisect bad" it says:
Bisecting: 555 revisions left to test after this
fatal: Entry 'dlls/wined3d/directx.c' not uptodate. Cannot merge.
but I did get a different error message(I think) this go.(Attached).

Please let me know what else I can do to help.(I'm lost with the whole bisect
thing. Wine is the first project I've used git for)
-Matt

[Bug 11545] call of duty 4 stopped working around the time of 0.9.54( not fixed with 55)

http://bugs.winehq.org/show_bug.cgi?id=11545

--- Comment #7 from Rico   2008-02-16 12:17:23 ---
Created an attachment (id=10811)
 --> (http://bugs.winehq.org/attachment.cgi?id=10811)
3dmark.patch

Simply run:

- git bisect start
- git bisect good ...
- git bisect bad ...
1:
- patch -p1 < 3dmark.patch
- ./configure && make clean && make depend && make
- patch -p1 < 3dmark_rev.patch
- git bisect bad/good
- goto 1 until you have found the right one

[Bug 11545] call of duty 4 stopped working around the time of 0.9.54( not fixed with 55)

http://bugs.winehq.org/show_bug.cgi?id=11545

--- Comment #8 from Rico   2008-02-16 12:19:47 ---
Created an attachment (id=10812)
 --> (http://bugs.winehq.org/attachment.cgi?id=10812)
3dmark_rev.patch

This is the second one you need. This only reverts the changes done by this one
http://bugs.winehq.org/attachment.cgi?id=10811 .

[Bug 11545] call of duty 4 stopped working around the time of 0.9.54( not fixed with 55)

http://bugs.winehq.org/show_bug.cgi?id=11545

--- Comment #9 from Rico   2008-02-16 12:41:52 ---
Your log in post #5 looks like you have something installed which isn't
necessary for cod4. 
err:winedevice:ServiceMain driver L"Cdr4_2K" failed to load
err:winedevice:ServiceMain driver L"Cdralw2k" failed to load
This could also a root of a problem, so please try always with a fresh wine
prefix!

But the crash of the game looks as it is in the sound component.
=>1 0x7d56797c IDsCaptureDriverImpl_Open+0x6c

[Bug 11545] call of duty 4 stopped working around the time of 0.9.54( not fixed with 55)

http://bugs.winehq.org/show_bug.cgi?id=11545

--- Comment #10 from Austin English   2008-02-16 16:23:07 ---
(In reply to comment #8)
> Created an attachment (id=10812)

--> (http://bugs.winehq.org/attachment.cgi?id=10812) [details]
> 3dmark_rev.patch
>
> This is the second one you need. This only reverts the changes done by this one
> http://bugs.winehq.org/attachment.cgi?id=10811 .

You could run:

patch -p1 -R < 3dmark.patch

instead to revert the patch.

[Bug 11545] call of duty 4 stopped working around the time of 0.9.54( not fixed with 55)

http://bugs.winehq.org/show_bug.cgi?id=11545

Matthew Clark  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED

--- Comment #11 from Matthew Clark   2008-02-18 19:47:57 ---
Well, I'm not positive what happened, but it works now...  I guess it was the
latest nvidia-drivers I installed (169.09-r1 gentoo), because all of the sudden
all the git sources from 52 to current work... /sigh sorry for the waste time
and energy on your part, but at least I learned how to do regression tests^^

thanks,
-Matt

[Bug 11545] call of duty 4 stopped working around the time of 0.9.54( not fixed with 55)

http://bugs.winehq.org/show_bug.cgi?id=11545

Dan Kegel  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #12 from Dan Kegel   2008-02-22 11:40:17 ---
0.9.56 released, so closing all bugs marked as RESOLVED FIXED.