http://bugs.winehq.org/show_bug.cgi?id=29455
Bug #: 29455 Summary: Call of Duty 4: persons are not visible Product: Wine Version: 1.3.35 Platform: x86 OS/Version: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: hardy.schumacher@gmx.de Classification: Unclassified
Created attachment 38134 --> http://bugs.winehq.org/attachment.cgi?id=38134 Logfile from "Call of Duty 4"
In "Call of Duty 4" all persons are not visible, Only their equipments can be seen.
This issue was seen with v1.3.34 and v1.3.35 of WINE. Used FreeBSD version is i386 v8.2. As a graphics card an NVIDIA GeForce 7600 GS is used. Graphics driver is from NVIDIA v285.05.09.
http://bugs.winehq.org/show_bug.cgi?id=29455
Hardy Schumacher hardy.schumacher@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |directx-d3d
--- Comment #1 from Hardy Schumacher hardy.schumacher@gmx.de 2012-01-01 12:31:31 CST --- It seems that the issue is gone since I've had replaced my single core AMD Athlon 64 3500+ by an AMD Athlon 64 X2 4800+!
Now all persons are rendered correctly, but the game is much slower than before (with invisible persons).
So please check what's the source of the issue. Because CoD4 does not explicitly require a multi core CPU.
http://bugs.winehq.org/show_bug.cgi?id=29455
nomessage89@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nomessage89@gmail.com
--- Comment #2 from nomessage89@gmail.com 2012-08-07 04:13:11 CDT --- I am experiencing the same issues with missing characters. No bodies, just weapons, helmets, etc. The last version that seemed to work for me was 1.3.18, as several versions after this had the glitch (v1.3 patch 21, 23, 29, 36, v1.2.3, and v1.4.0 or later). Version 1.3 patches 19, 20, and 36 all failed to run the program as a whole, no graphical errors but instead just "PnkbstrB.exe" and "wineserver" running. I am running on an Athlon 3700+ and GeForce 7600GT (very similar specs).
http://bugs.winehq.org/show_bug.cgi?id=29455
Rico kgbricola@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #38134|application/octet-stream |text/plain mime type| |
http://bugs.winehq.org/show_bug.cgi?id=29455
--- Comment #3 from Rico kgbricola@web.de 2012-08-07 05:01:01 CDT --- What's the exact version for COD4? There seem to be reports in the appdb where that game works fine ( see http://appdb.winehq.org/objectManager.php?sClass=application&iId=5934 ), even with pretty similar hardware. You may run a regression test to find the patch which broke it (http://wiki.winehq.org/RegressionTesting/). Do you have any special settings in COD4 that may trigger the problem?
@nomessage89 What's your OS? What's your gpu driver version? The 3700+ is a single core cpu? Does the demo have the same problem?
http://bugs.winehq.org/show_bug.cgi?id=29455
--- Comment #4 from nomessage89@gmail.com 2012-08-15 02:29:08 CDT --- Not sure if you wanted me to answer these too, but here you go anyway: What's the exact version for COD4? -I'm running v1.7 of COD4 There seem to be reports in the appdb where that game works fine ( see http://appdb.winehq.org/objectManager.php?sClass=application&iId=5934 ), even with pretty similar hardware. You may run a regression test to find the patch which broke it (http://wiki.winehq.org/RegressionTesting/). Do you have any special settings in COD4 that may trigger the problem? -Never done a regression test before, looks a little complicated just from skimming the page you linked. May try this when I have some more free time. It says you may run into complications with a 64 bit processor? I'm on an Athlon 64 but running 32 bit OS. Do you think that warning in the instructions would still be relevant? @nomessage89 What's your OS? What's your gpu driver version? The 3700+ is a single core cpu? Does the demo have the same problem? I'm running Xubuntu 12.04 LTS 32 bit. Current driver is Nvidia 302.17, although this issue was still present pre-300 version drivers (from what I recall--seems consistent with Hardy's findings). 3700+ is a single core stock 2.2GHz which I've overclocked to 2.4GHz. Haven't tried running the demo version. May try that first before regression test, or may run COD4 without any patches.
http://bugs.winehq.org/show_bug.cgi?id=29455
--- Comment #5 from Rico kgbricola@web.de 2012-08-20 05:20:37 CDT --- The game looks fine here and the bodies could be seen with a C2Q and a radeon (2.1 Mesa 8.0.3, Gallium 0.4 on AMD RV710). I also tried taskset to 1 and kernel parameter maxcpus=1, both without success in replicating the issue.
I get the feeling, that the combination of the cpu / gpu (driver) makes the trouble. It would be nice, if we could check if the problem happens with combinations like (Athlon 64 and (radeon, intel gma or gforce>8000)) or (Intel cpu and geforce 7xxx). You also may give nouveau a try, but I'm not sure it will run the game at all.
If it is a regression, the regression test will show the faulty commit and will show a lot faster where the problem might come from. I don't expect much more trouble for the regression test, because you use a 32bit system (even if the cpu is capable of running 64bit, it runs in 32bit mode). Trouble may happen if you use a 64bit system. Though compiling wine on a single core cpu may take a while.
@Hardy Schumacher Could you try to limit the max number of cpus to 1 and see if the problem shows up again?
http://bugs.winehq.org/show_bug.cgi?id=29455
--- Comment #6 from nomessage89@gmail.com 2012-10-18 03:20:03 CDT --- Rico, I finally got around to running a regression test. I compiled Wine via your instructions and altered the command "sudo apt-get build-dep wine1.3" by changing '1.3' to '1.4'. I moved my existing Wine folder also and reinstalled CoD4. After it completed, I got a Wine crash and the following error: "Exception Exception in module CoD4.exe at 0017DE3F. Error creating object. Please verify that the Microsoft Data Access Components 2.1 (or later) have been properly installed."
I first installed to .wine by just running setup.exe with the Wine application, but soon after realized this would use standard packages rather than the git package. So I deleted the new .wine folder I made and re-ran from the CD with "/home/xxxx/wine-git/wine setup.exe". I'm hoping that's the right way to do it? Anyways, this also resulted in a crash after it asked me whether I wanted to install Punkbuster. Any ideas on how to get it to work? This is my first time working with a git setup, so I'm still kind of confused about how I'm ultimately supposed to get this to work. Output below, got a pop-up about "Wine internal errors".
xxxx@yyyy:/media/COD4MW$ /home/xxxx/wine-git/wine setup.exe wine: created the configuration directory '/home/xxxx/.wine' WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-4zaiFY/pkcs11: No such file or directory Could not load wine-gecko. HTML rendering will be disabled. wine: configuration in '/home/xxxx/.wine' has been updated. fixme:storage:create_storagefile Storage share mode not implemented. fixme:apphelp:ApphelpCheckInstallShieldPackage stub: 0x32b160 L"Z:\media\COD4MW\CoD4MW.msi" err:mscoree:LoadLibraryShim error reading registry key for installroot err:mscoree:LoadLibraryShim error reading registry key for installroot err:mscoree:LoadLibraryShim error reading registry key for installroot err:mscoree:LoadLibraryShim error reading registry key for installroot WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-4zaiFY/pkcs11: No such file or directory err:ntdll:RtlpWaitForCriticalSection section 0x68769980 "win.c: surfaces_section" wait timed out in thread 002b, blocked by 0009, retrying (60 sec) wine: Critical section 68769980 wait failed at address 0x7bc367dc (thread 002b), starting debugger... Can't attach process 0008: error 5 err:ntdll:RtlpWaitForCriticalSection section 0x68769980 "win.c: surfaces_section" wait timed out in thread 002b, blocked by 0009, retrying (60 sec)
http://bugs.winehq.org/show_bug.cgi?id=29455
--- Comment #7 from nomessage89@gmail.com 2012-10-18 03:24:55 CDT --- PS: I've tried running CoD4 on my laptop with newer multicore processor and AMD integrated graphics from an APU. Theoretically this should run rather easily compared to my current setup on my desktop. However, running both the same version of Wine (1.3.18) as well as 1.4 stable is unbearably slow and locks up the system. I run Linux Mint 13 MATE 32 bit with the latest Catalyst drivers for APUs on the laptop. I took a stab at open-source Radeon a couple of times, but this actually seemed worse since it wasn't drawing to the screen correctly on Battlefield 2 and was also unbearably slow. :/
http://bugs.winehq.org/show_bug.cgi?id=29455
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #8 from joaopa jeremielapuree@yahoo.fr 2012-10-18 03:40:02 CDT --- Does it happen with the demo
http://www.jeuxvideo.com/telecharger/jeux-et-demos/00013409-call-of-duty-4-m...
http://bugs.winehq.org/show_bug.cgi?id=29455
Brandon Corujo haku08879@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |haku08879@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=29455
Jarkko K jarkko_korpi@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jarkko_korpi@hotmail.com
--- Comment #9 from Jarkko K jarkko_korpi@hotmail.com --- Could someone give an update into this?
https://bugs.winehq.org/show_bug.cgi?id=29455
hyacinthe.cartiaux@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hyacinthe.cartiaux@free.fr
--- Comment #10 from hyacinthe.cartiaux@free.fr --- I can't reproduce with the demo and the full game (v1.7) using my setup (archlinux x86_64 / wine 1.7.37 / i7-4600U and the IGP with the xf86-video-intel-driver). Actually, I've never seen this bug with cod4 and I've tested all wine releases from 1.7.28 to 37.
https://bugs.winehq.org/show_bug.cgi?id=29455
super_man@post.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net, | |super_man@post.com
https://bugs.winehq.org/show_bug.cgi?id=29455
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #11 from Anastasius Focht focht@gmx.net --- Hello folks,
there is conflicting information here (even from OP), but at least some people reported it working for them, resolving 'FIXED'.
Regards
https://bugs.winehq.org/show_bug.cgi?id=29455
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #12 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.9.0.