[Bug 29194] New: Batman Arkham Asylum demo: black screen with Catalyst >= 11.6
http://bugs.winehq.org/show_bug.cgi?id=29194 Bug #: 29194 Summary: Batman Arkham Asylum demo: black screen with Catalyst >= 11.6 Product: Wine Version: 1.3.33 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: danxuliu(a)gmail.com Classification: Unclassified Created attachment 37672 --> http://bugs.winehq.org/attachment.cgi?id=37672 Batman Arkham Asylum demo log with Catalyst 11.11 I'm not sure if this is a real Wine bug or just a Catalyst bug. If it is a Catalyst bug, sorry for bothering you :) In a fresh wineprefix, I have configured Wine (1.3.33) to run in windowed mode, in 1024x768 resolution. After that, I have installed Batman Arkham Asylum demo (http://cdn2.netops.eidosinteractive.com/batmanarkhamasylum/BMDemo_installer....). Then, I have installed dotnet20 with winetricks (as .NET is needed to run the game). Due to bug http://bugs.winehq.org/show_bug.cgi?id=20651, I also have to add in "installed Batman Demo directory"/BmGame/Config/UserEngine.ini: [Engine.Engine] Language=int Once all this is done, executing "installed Batman Demo directory"/Binaries/ShippingPC-BmGame.exe with Catalyst 11.5 shows a Batman image and then the intro videos (bink videos) start. However, with Catalyst 11.6 and newer (the newest at the time of this writing is 11.11, and it shows the problem too) instead of the intro videos a black screen appears. If I change to other window and then show the Wine desktop again, the game window is not refreshed (I mean, the contents of the game window are those of the window I showed over it). My graphics card is an Ati Radeon HD 4890. I have attached the Wine log. Note that the "^C" in the eighth line from the end was caused by a Ctrl-C in the console to stop the game. I don't know what other information is needed, so please ask :) -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=29194 Daniel Calviño Sánchez <danxuliu(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |http://cdn2.netops.eidosint | |eractive.com/batmanarkhamas | |ylum/BMDemo_installer.exe -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=29194 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #1 from joaopa <jeremielapuree(a)yahoo.fr> 2011-11-28 03:16:34 CST --- Newest catalyst 11.11b fix a problem with this game. Please, give it a try -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=29194 --- Comment #2 from Henri Verbeet <hverbeet(a)gmail.com> 2011-11-28 08:37:13 CST --- (In reply to comment #0)
err:ntdll:RtlpWaitForCriticalSection section 0x7df65b58 "wined3d_main.c: wined3d_cs" wait timed out in thread 003a, blocked by 0000, retrying (60 sec)
This probably means it died while holding the wined3d critical section, possibly because of the ^C you did. It may be useful to try to get a backtrace at the point the game is hanging. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=29194 --- Comment #3 from Daniel Calviño Sánchez <danxuliu(a)gmail.com> 2011-11-28 20:30:53 CST --- Created attachment 37686 --> http://bugs.winehq.org/attachment.cgi?id=37686 Batman Arkham Asylum demo backtrace with Catalyst 11.11 (In reply to comment #1)
Newest catalyst 11.11b fix a problem with this game. Please, give it a try
According to http://support.amd.com/us/kbarticles/Pages/catalyst-1111b-performance.aspx, Catalyst 11.11b is a Windows only release, so I can't try it ;) Please also note that "Batman: Arkham City" is not the same game as "Batman: Arkham Asylum", but a sequel. (In reply to comment #2)
It may be useful to try to get a backtrace at the point the game is hanging.
I have rebuilt the Wine 1.3.33 package of my distribution (Mandriva 2010.2) using "-O0" to disable optimizations. To get the backtrace, I launched ShippingPC-BmGame.exe and when the screen went black, I executed winedbg in another terminal. Then, in winedbg prompt I typed "bt all". The output of "bt all" is what I have attached here. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=29194 --- Comment #4 from Henri Verbeet <hverbeet(a)gmail.com> 2011-11-29 00:01:11 CST --- (In reply to comment #3)
Backtracing for thread 0038 in process 0008 (C:\Archivos de programa\Eidos\Batman Arkham Asylum Demo\Binaries\ShippingPC-BmGame.exe): fixme:dbghelp_dwarf:dwarf2_get_cie wrong CIE pointer fixme:dbghelp_dwarf:dwarf2_get_cie wrong CIE pointer Backtrace: =>0 0xf601e4e1 in fglrx_dri.so (+0xe2d4e1) (0x7c8d4490) That's a bit less helpful than I was hoping for, I'm afraid. It does suggest it's hanging somewhere inside the driver though. I suppose you could try to enable some debug channels (e.g. +d3d9,+d3d,+d3d_draw,+d3d_surface) to try to narrow it down to a specific OpenGL call.
-- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=29194 --- Comment #5 from Daniel Calviño Sánchez <danxuliu(a)gmail.com> 2011-11-29 09:06:30 CST --- Created attachment 37695 --> http://bugs.winehq.org/attachment.cgi?id=37695 Repeated debug (+d3d9,+d3d,+d3d_draw,+d3d_surface) text (In reply to comment #4)
I suppose you could try to enable some debug channels (e.g. +d3d9,+d3d,+d3d_draw,+d3d_surface) to try to narrow it down to a specific OpenGL call.
Running "WINEDEBUG=+d3d9,+d3d,+d3d_draw,+d3d_surface wine ShippingPC-BmGame.exe" gives an output of several MB in just a few seconds. However, once the black screen appears, only 8 lines appear again and again. I have attached those lines (in the same order that they appear the first time). Anyway, if you want the full trace I can upload it, of course. It weights 8MB (after removing 82MB of repeated output ;) ), so I prefer to ask before doing it. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=29194 --- Comment #6 from Daniel Calviño Sánchez <danxuliu(a)gmail.com> 2011-12-19 17:52:34 CST --- Problem still present with Catalyst 11.12 and Wine 1.3.35. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=29194 --- Comment #7 from Daniel Calviño Sánchez <danxuliu(a)gmail.com> 2011-12-20 18:33:49 CST --- Created attachment 38055 --> http://bugs.winehq.org/attachment.cgi?id=38055 Differences between traces from Catalyst 11.5 (working) and Catalyst 11.12 (not working) I have found something that perhaps can give you a hint about the problem. I have executed the demo with Catalyst 11.5 (the last release where it worked) and Catalyst 11.12 (the latest one) with the same version of Wine (1.3.35, the latest one) and compared the trace. There are only three* differences between them. The trace with Catalyst 11.5 was trimmed down manually to the point where the trace with Catalyst 11.12 began to repeat the same output over and over. Then, I replaced all the hexadecimal values in the traces by the word "hexadecimal", as they are mainly memory addresses and thus different in each run, using sed (sed -r "s/0x[0-9a-f]+/hexadecimal/g"). Finally, I got the difference between the Catalyst 11.5 trace and the Catalyst 11.12 trace with diff command. When Catalyst 11.12 was used, the trace showed two errors that did not appear in the Catalyst 11.5 trace: "err:d3d:context_create wglSwapIntervalEXT failed to set swap interval 0 for context 0x1d1d80, last error 0x591" and "err:d3d:context_create wglSwapIntervalEXT failed to set swap interval 0 for context 0x1c6524b8, last error 0x591". The context value in this second error is the same that appears in the lines repeated over and over. The other difference in the trace is that, even before the point where Catalyst 11.12 repeats the same output over and over, Catalyst 11.5 has 1392 lines that do not appear in the Catalyst 11.12 trace. I have attached the diff between both traces and a context of 105 lines. I have used this huge context to reach the "end" (where Catalyst 11.12 starts to output the same 8 lines over and over) of the trace after the bunch of Catalyst 11.5 only lines. *Well, there is another difference, which is a different thread number in ony point, but I think that it changes between executions, like memory addresses. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=29194 Jarkko K <jarkko_korpi(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jarkko_korpi(a)hotmail.com --- Comment #8 from Jarkko K <jarkko_korpi(a)hotmail.com> --- Is this still valid bug?? I can play the full game with 7870 ati 14.3 beta OpenGL vendor string: Advanced Micro Devices, Inc. OpenGL renderer string: AMD Radeon HD 7800 Series OpenGL core profile version string: 4.3.12798 Core Profile Context 13.35.1005 OpenGL core profile shading language version string: 4.30 Also the wine has increased in numbers since the bug has reported. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=29194 --- Comment #9 from Daniel Calviño Sánchez <danxuliu(a)gmail.com> --- (In reply to Jarkko K from comment #8)
Is this still valid bug??
I can play the full game with 7870 ati 14.3 beta
I don't know about the full game. But, for the demo, it is still valid with Wine 1.7.15 and Catalyst 12.4. Note that I can only use an old Catalyst release because the support for my graphic card, a Radeon HD 4890, was dropped in Catalyst 12.7. However, the bug does not appear using the FOSS Mesa driver :) Also, with the (currently) latest Wine CSMT branch, it does work with Catalyst 12.4 too when CSMT is enabled. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=29194 hanska2(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hanska2(a)luukku.com --- Comment #10 from hanska2(a)luukku.com --- Daniel Any update on this? wine is currently at 1.7.24 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=29194 --- Comment #11 from Daniel Calviño Sánchez <danxuliu(a)gmail.com> --- (In reply to hanska2 from comment #10)
Daniel
Any update on this?
wine is currently at 1.7.24
I no longer have the same graphics card used in the original bug report (Radeon 4890). However, my current graphics card is a Radeon 7870, and using the same driver as in my last comment (Catalyst 12.4) the problem is still valid with latest Wine (1.7.27). Also, like in my last comment, with the latest Wine CSMT branch (updated since that last comment), the problem does not appear. Note that Jarkko K stated in comment #8 that the full game works with Catalyst 14.3 and a Radeon 7870 graphics card, which is the same graphics card as my current one. Probably, the demo will work too with Catalyst 14.3, but unfortunately at this time I can't test it to be sure. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=29194 super_man(a)post.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man(a)post.com --- Comment #12 from super_man(a)post.com --- Isnt this basically upstream issue? Also the mesa drivers are pretty good for amd and there has been a new relase of catalyst drivers. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=29194 --- Comment #13 from joaopa <jeremielapuree(a)yahoo.fr> --- This bug could be closed as ABANDONED, I think -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=29194 --- Comment #14 from joaopa <jeremielapuree(a)yahoo.fr> --- What to do with such a bug report? It is hardware dependent and the reporter does not bother to respond. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=29194 --- Comment #15 from Zebediah Figura <z.figura12(a)gmail.com> --- (In reply to joaopa from comment #14)
What to do with such a bug report? It is hardware dependent and the reporter does not bother to respond.
Doesn't bother to respond to what, exactly? I'm not sure what question has been directed at the reporter that they have failed to respond to. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=29194 --- Comment #16 from joaopa <jeremielapuree(a)yahoo.fr> ---
respond to what?
At the implied question: does the bug still occur with the latest wine. Reporter have not been replied to the state of this bug since more 4 years. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=29194 --- Comment #17 from Austin English <austinenglish(a)gmail.com> --- (In reply to joaopa from comment #16)
respond to what?
At the implied question: does the bug still occur with the latest wine. Reporter have not been replied to the state of this bug since more 4 years.
Again, that doesn't make it abandoned. Please stop assuming everyone checks in bugs every few months. If you're worried about a particular bug, then explicitly all rather than assuming everyone knows bugzilla policy. Daniel, do you still see this issue (assuming you still have this hardware)? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=29194 --- Comment #18 from Daniel Calviño Sánchez <danxuliu(a)gmail.com> ---
Daniel, do you still see this issue (assuming you still have this hardware)?
Yes, I still have a Radeon 7870 graphics card. With Catalyst 12.4 and Wine 1.7.44 the described problem is still valid. However, since Wine 1.7.45 and up to Wine 4.0-rc6 (I haven't tested with Wine 4.0-rc7) there is a different problem: now the game crashes even before the splash screen is shown. Here is an excerpt of the console (as it's just three lines I'm pasting it instead of attaching, sorry if I should have attached it anyway :-) ): --------- Backtrace: =>0 0xf5edcfdc in fglrx_dri.so (+0x118afdc) (0x000000c8) 0xf5edcfdc: repne ??? --------- Moreover, it is no longer possible to install the game (the crash happens when running the game with Wine 1.7.45 or later on a Wine prefix with the game installed using Wine 1.7.44); when the installer tries to check the system to get the CPU, graphics memory and so on it shows the following error message: --------- Error number: 0x80040707 Description: DLL function call crashed: BmSysCheckDll.CheckSystem Setup will now terminate --------- I made a bisection and found that these new errors started with https://source.winehq.org/git/wine.git/commit/04c3c970724cae9d16ddaa33732d59... However, with Catalyst 15.12 there is no problem in Wine 1.7.27 (the version I tested in my last comment that with Catalyst 12.4 still showed the original problem), Wine 4.0-rc6 nor in intermediate 2.x and 3.x versions; everything works as expected with Catalyst 15.12. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=29194 Matteo Bruni <matteo.mystral(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG --- Comment #19 from Matteo Bruni <matteo.mystral(a)gmail.com> --- (In reply to Daniel Calviño Sánchez from comment #18)
However, with Catalyst 15.12 there is no problem in Wine 1.7.27 (the version I tested in my last comment that with Catalyst 12.4 still showed the original problem), Wine 4.0-rc6 nor in intermediate 2.x and 3.x versions; everything works as expected with Catalyst 15.12.
Sounds like the drivers were fixed at some point. Thank you for the update! -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=29194 Matteo Bruni <matteo.mystral(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #20 from Matteo Bruni <matteo.mystral(a)gmail.com> --- Closing fixed "upstream" bug. Please open separate bugs for any other issue you're experiencing. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=29194 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |focht(a)gmx.net URL|http://cdn2.netops.eidosint |https://web.archive.org/web |eractive.com/batmanarkhamas |/20120522222803/http://cdn2 |ylum/BMDemo_installer.exe |.netops.eidosinteractive.co | |m/batmanarkhamasylum/BMDemo | |_installer.exe --- Comment #21 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, adding stable download link via Internet Archive for documentation purpose. https://web.archive.org/web/20120522222803/http://cdn2.netops.eidosinteracti... Although multiple snapshots exist, not all are usable. --- snip --- $ wget http://web.archive.org/cdx/search/cdx?url="http://cdn2.netops.eidosinteractive.com/batmanarkhamasylum/BMDemo_installer.exe&output=json&filter=statuscode:200&filter=mimetype:application/x-msdownload" -q -O -| jq [ [ "urlkey", "timestamp", "original", "mimetype", "statuscode", "digest", "length" ], [ "com,eidosinteractive,netops,cdn2)/batmanarkhamasylum/bmdemo_installer.exe", "20110111212534", "http://cdn2.netops.eidosinteractive.com/batmanarkhamasylum/BMDemo_installer....", "application/x-msdownload", "200", "XCHZNOVK6QSISSJXUOSTDO76TRXXFO7T", "2027534948" ], [ "com,eidosinteractive,netops,cdn2)/batmanarkhamasylum/bmdemo_installer.exe", "20120522222803", "http://cdn2.netops.eidosinteractive.com/batmanarkhamasylum/BMDemo_installer....", "application/x-msdownload", "200", "OWBMQ7GDTAYBNR736IIETGO7BB7MZZ5G", "2187287461" ], [ "com,eidosinteractive,netops,cdn2)/batmanarkhamasylum/bmdemo_installer.exe", "20181119144939", "http://cdn2.netops.eidosinteractive.com/batmanarkhamasylum/BMDemo_installer....", "application/x-msdownload", "200", "OWBMQ7GDTAYBNR736IIETGO7BB7MZZ5G", "2187286774" ], [ "com,eidosinteractive,netops,cdn2)/batmanarkhamasylum/bmdemo_installer.exe", "20210221023639", "http://cdn2.netops.eidosinteractive.com/batmanarkhamasylum/BMDemo_installer....", "application/x-msdownload", "200", "OWBMQ7GDTAYBNR736IIETGO7BB7MZZ5G", "2187286819" ] ] --- snip --- The first one with 20110111212534 timestamp is 152 MiB less in size = corrupted. The self-extractor will complain about corrupted .CAB file when executing. $ sha1sum BMDemo_installer.exe 7582c87cc3983016c7fbf2104999df087ecce7a6 BMDemo_installer.exe $ du -sh BMDemo_installer.exe 2.1G BMDemo_installer.exe Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla