[Bug 58064] New: Unreal 2 hangs with a black screen when switching to 1440X900 resolution
https://bugs.winehq.org/show_bug.cgi?id=58064 Bug ID: 58064 Summary: Unreal 2 hangs with a black screen when switching to 1440X900 resolution Product: Wine Version: 10.5 Hardware: x86-64 URL: https://community.pcgamingwiki.com/files/file/265-unre al-ii-the-awakening-single-player-demo/?do=download&cs rfKey=dbe29bc7b5c23e8ee79b15e743414902 OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: ab2b7ebfcd78f6a74068a5a79d90ee6fcf235a12 Distribution: ArchLinux Unreal 2 starts in 1024X768 resolution and switching between 640X480, 800X600 or 1024X768 modes works properly, however when I try to switch to 1440X900 in the video options menu, the game hangs with a black screen and Unreal2.exe is consuming 100% CPU. 1440X900 is the max. resolution that my monitor supports. Used to work before commit ab2b7ebfcd78f6a74068a5a79d90ee6fcf235a12 winex11: Use win32u generic wgl(Get|Set)PixelFormat(WINE). The same commit causes similar issue (black screen and game .exe pegging the CPU) when trying to start the following games: Art of Murder: Cards of Destiny https://store.steampowered.com/app/836770/Art_of_Murder__Cards_of_Destiny/ Art of Murder - Hunt for the Puppeteer https://store.steampowered.com/app/832540/Art_of_Murder__Hunt_for_the_Puppet... Chronicles of Mystery: The Scorpio Ritual https://store.steampowered.com/app/34800/Chronicles_of_Mystery_The_Scorpio_R... OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 570.133.07 -- 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=58064 --- Comment #1 from Rémi Bernon <rbernon(a)codeweavers.com> --- I'm not able to reproduce the issue, could you attach a log file with WINEDEBUG=+pid,+loaddll,+seh,+unwind,+d3d,+opengl,+wgl,+system,+win,+x11drv ? -- 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=58064 --- Comment #2 from Béla Gyebrószki <gyebro69(a)gmail.com> --- (In reply to Rémi Bernon from comment #1)
I'm not able to reproduce the issue, could you attach a log file with WINEDEBUG=+pid,+loaddll,+seh,+unwind,+d3d,+opengl,+wgl,+system,+win,+x11drv ?
The log is huge (almost 500 MB uncompressed) and I can't compress it further to make Bugzilla accept it. https://drive.google.com/file/d/1pgjhIt92l6GP4HGGWhrFur0eGIomx5aj/view?usp=s... Unreal2_debug.log.xz (13 MB) -- 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=58064 --- Comment #3 from Béla Gyebrószki <gyebro69(a)gmail.com> --- Created attachment 78324 --> https://bugs.winehq.org/attachment.cgi?id=78324 HoMM V debug log Here is a debug log from Heroes of Might & Magic V: the game hangs with a black screen when I try to change resolution to 1440X900. The size of the log is more manageable, only 54 MB uncompressed. Changing resolution works properly with the previous commit. Demo: https://archive.org/details/HeroesOfMightMagicV -- 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=58064 --- Comment #4 from Rémi Bernon <rbernon(a)codeweavers.com> --- Thanks! I still haven't found what is wrong but would you mind making the same HoMM log with the change reverted? Maybe comparing the two will make it obvious. -- 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=58064 --- Comment #5 from Béla Gyebrószki <gyebro69(a)gmail.com> --- (In reply to Rémi Bernon from comment #4)
Thanks! I still haven't found what is wrong but would you mind making the same HoMM log with the change reverted? Maybe comparing the two will make it obvious.
Sorry, but I don't know how to revert the patch on 10.5 :( Doesn't revert cleanly. -- 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=58064 --- Comment #6 from Rémi Bernon <rbernon(a)codeweavers.com> --- I cannot reproduce any issue with HOMM on my desktop either... though I have an AMD GPU, maybe it's related to some specific pixel formats.
Sorry, but I don't know how to revert the patch on 10.5 :( Doesn't revert cleanly.
Could you make the same log with the commit before the one that breaks it? -- 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=58064 --- Comment #7 from Béla Gyebrószki <gyebro69(a)gmail.com> --- Created attachment 78333 --> https://bugs.winehq.org/attachment.cgi?id=78333 HoMMV debug log before breakage (uncompressed 293 MB) This is the same debug log with the commit prior to ab2b7ebfcd78f6a74068a5a79d90ee6fcf235a12. It is much bigger because the game can actually load the main menu. -- 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=58064 --- Comment #8 from Rémi Bernon <rbernon(a)codeweavers.com> --- Thanks for the log, I can see a difference indeed and it looks like that in the broken case execution gets stuck within X11DRV_wglCreateContextAttribsARB, but comparing both logs they seem to be using the same pixel formats so I don't really understand why it gets stuck there. Fwiw I have tried with an NVIDIA GPU as well, (GTX 1070 but with older driver versions), and I cannot reproduce the problem either. -- 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=58064 --- Comment #9 from Béla Gyebrószki <gyebro69(a)gmail.com> --- (In reply to Rémi Bernon from comment #8)
Thanks for the log, I can see a difference indeed and it looks like that in the broken case execution gets stuck within X11DRV_wglCreateContextAttribsARB, but comparing both logs they seem to be using the same pixel formats so I don't really understand why it gets stuck there.
Fwiw I have tried with an NVIDIA GPU as well, (GTX 1070 but with older driver versions), and I cannot reproduce the problem either.
It could be something configured incorrectly on my system then. The fact is that the problem doesn't occur with the open source nouveau driver, but reproducible with Nvidia 570.133.07, 570.123.01 (Vulkan dev), 565.77, 550.144.03. Btw. the bug title might be misleading: by '1440X900 resolution' I meant the highest resolution that your monitor supports or the resolution at which your desktop runs. Yours might be higher. It is interesting that the bug doesn't occur when switching between any lower resolutions in the game. -- 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=58064 Dmytro Bagrii <dimich.dmb(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimich.dmb(a)gmail.com -- 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=58064 --- Comment #10 from Béla Gyebrószki <gyebro69(a)gmail.com> --- Still an issue in wine-10.6-109-ge646263a6f0. I'm currently on NVIDIA 575.51.02 driver. What I found that works as a solution: - CSMT=off - using DXVK instead of wined3d. Is there anything I can do to help ? I keep coming across more and more games that are affected (I'm trying mostly old DX7/8/9 games). -- 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=58064 --- Comment #11 from Rémi Bernon <rbernon(a)codeweavers.com> --- Created attachment 78484 --> http://bugs.winehq.org/attachment.cgi?id=78484 Additional traces Could you make another log with the same channels as above, on latest git HEAD and with the attached patch? -- 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=58064 --- Comment #12 from Béla Gyebrószki <gyebro69(a)gmail.com> --- Created attachment 78487 --> http://bugs.winehq.org/attachment.cgi?id=78487 debug log with additional traces Created with wine-10.6-123-gf37d05ebbb4. -- 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=58064 --- Comment #13 from Rémi Bernon <rbernon(a)codeweavers.com> --- Thanks, sadly I don't see anything obviously wrong here or any reason why context creation suddenly gets stuck :/ -- 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=58064 --- Comment #14 from Béla Gyebrószki <gyebro69(a)gmail.com> --- (In reply to Rémi Bernon from comment #13)
Thanks, sadly I don't see anything obviously wrong here or any reason why context creation suddenly gets stuck :/
I see. Anyway, thank you for all the work you have put in so far. Is this commit merged in Proton 10 in some way or other? Proton has a wider user base and the bug may eventually show up in their bug tracker too. I wonder if this is really just an isolated bug I'm 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.
http://bugs.winehq.org/show_bug.cgi?id=58064 --- Comment #15 from Rémi Bernon <rbernon(a)codeweavers.com> --- No, it's only in Wine for now. -- 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=58064 Béla Gyebrószki <gyebro69(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |260346a9160568004b9cb123608 | |fb988c30623f1 Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #16 from Béla Gyebrószki <gyebro69(a)gmail.com> --- Fixed with https://gitlab.winehq.org/wine/wine/-/commit/260346a9160568004b9cb123608fb98... Thank you Rémi! -- 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=58064 --- Comment #17 from Rémi Bernon <rbernon(a)codeweavers.com> --- Uh... this change is supposed to be no-op... I don't understand how it made any difference. -- 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=58064 --- Comment #18 from Dmytro Bagrii <dimich.dmb(a)gmail.com> --- (In reply to Béla Gyebrószki from comment #16)
Fixed with https://gitlab.winehq.org/wine/wine/-/commit/ 260346a9160568004b9cb123608fb988c30623f1
This commit also fixed https://bugs.winehq.org/show_bug.cgi?id=58078. Thanks. -- 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=58064 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #19 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 10.10. -- 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=58064 --- Comment #20 from Béla Gyebrószki <gyebro69(a)gmail.com> --- This bug resurfaced after 79eb50683f56e55a1ce485f3d288983ed33f1c34 I just want to let you know that MR8383 looks promising as it fixes the problem, hopefully for good. Keep up the good work Rémi Bernon :) -- 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 (1)
-
WineHQ Bugzilla