March 2013 - Wine-bugs - list.winehq.org

[Bug 2082] DirectDraw games only showing black screen
by wine-bugs＠winehq.org 14 Mar '13

14 Mar '13

http://bugs.winehq.org/show_bug.cgi?id=2082 --- Comment #109 from Murray Colpman <muzerakascooby(a)gmail.com> 2013-03-14 18:26:39 CDT --- (In reply to comment #106) > Could you maybe elaborate on how that can be achieved? What do you mean by > "ingame minimisation"? Would be happy to try out your suggestion. Well, the maintainers for the game added an option to change the SetCooperativeLevel call to pass the desktop window as the parameter. This breaks ingame minimisation because the only way to minimise ingame due to other weirdness with the game itself is to set the desktop window as the currently active window. > It may be worthwhile posting the other workarounds here anyway. They may be > useful to users or developers looking at the problem. I believe Windows 8 essentially has a registry key to enable old ddraw behaviour/emulation/something special at least, which is what this workaround does (sets that key). Here's the reg file: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers] "C:\\Team17\\Worms Armageddon\\WA.exe"="$ DWM8And16BitMitigation Layer_ForceDirectDrawEmulation" So, if Windows has a registry workaround, wine might benefit one too ;) Weirdly enough, WA has implemented new renderers recently - DirectDraw 32-bit (previous was 8-bit), Direct3D 7, Direct3D 9 with CPU palette conversion, and Direct3D 9 with Shader palette conversion. The weird thing is, these also exhibit a black screen in wine, and there appears to be no workaround (apart from DirectDraw 32-bit which has the same workaround as the old 8-bit renderer, that is the SetCooperativeLevel thing described above). I don't know if this is the same bug - if there's some legacy function in DirectDraw that enables the same sort of behaviour - or something completely unrelated, but they do definitely work in Win8. I could have sworn there used to be some debug output that looks related but I can't find it now (the only seemingly-relevant line is fixme:d3d:wined3d_get_adapter_raster_status wined3d 0x14f8e0, adapter_idx 0, raster_status 0x33ef40 semi-stub!). However, I digress, this probably belongs in a new bug. -- 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.

1 0

[Bug 2082] DirectDraw games only showing black screen
by wine-bugs＠winehq.org 14 Mar '13

14 Mar '13

http://bugs.winehq.org/show_bug.cgi?id=2082 Vincent Povirk <madewokherd(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|madewokherd(a)gmail.com | -- 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.

1 0

[Bug 2082] DirectDraw games only showing black screen
by wine-bugs＠winehq.org 14 Mar '13

14 Mar '13

http://bugs.winehq.org/show_bug.cgi?id=2082 --- Comment #108 from Ben Klein <shacklein(a)gmail.com> 2013-03-14 18:14:32 CDT --- (In reply to comment #101) > (In reply to comment #100) > > But i still fail to understand how a bug that was reported in year 2004 has its > > status named NEW. > > I have been asking myself the same kind of questions. But it's the wine > project, they are beyond our logic. Wine does not typically use the ASSIGNED status in bugzilla. It's only in cases where there is a single, definitive developer responsible for that component. http://bugs.winehq.org/buglist.cgi?query_format=advanced&order=Importance&l… (In reply to comment #104) > (In reply to comment #103) > > By configuring general translucency settings for dialogs to something like 50% > > I could see the game's directdraw area(?) trough the covering dialog-window. > > > > I settled for 50% because when I need to undo the workaround, it's not nice to > > work with completely transparent dialogues. (And for diablo it only matters > > while navigating the menu. YMMV for other games.) > > Interestingly enough, this is pretty much the same workaround people came up > with for getting Worms Armageddon to work in Windows 8. I don't think that's a > coincidence. (However, there are now better workarounds that have been > discovered but they look Windows-specific). It may be worthwhile posting the other workarounds here anyway. They may be useful to users or developers looking at the problem. > I also don't believe this would work in a virtual desktop There's no obvious reason why it shouldn't. Please test it. (In reply to comment #106) > As to the Wine development and the question on why a 9 year old bug (!) is > marked as NEW: It appears Wine is dead. No matter what they claim, action speak > more than words. Does anyone know of a Wine fork by someone who actually gives > a #$%&? Mind your language. This bug is more complicated than it seems on the face of it. It's an incongruence between the way Windows draws its windows and the way X11 draws its windows, caused essentially by a bug in native Windows. Implementing the "hacks" to get it fixed presents two major problems: 1) It would definitely break other programs (solved by making it an app-specific registry flag) 2) It's simply the "wrong way" to do it The truth is apps affected by this bug are incorrectly using the desktop window, triggering the bug that makes them display on native Windows. Wine's current behaviour is the technically "correct" way; Windows 8 reportedly suffers from the same problem running these apps. That's not to say that this bug can't be fixed; it's just a highly complicated and very low priority issue. There are only four apps reported to suffer from this bug. http://appdb.winehq.org/viewbugs.php?bug_id=2082 As much as I'd love to see it get fixed, for the one people are most vocal about (Diablo) it's a minor issue that does not effect main gameplay (the menu scheme can be memorised/transcribed from a Windows system if you so wish), and the second most popular app (Worms Armageddon) has received an official patch that includes a workaround. -- 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.

1 0

[Bug 2082] DirectDraw games only showing black screen
by wine-bugs＠winehq.org 14 Mar '13

14 Mar '13

http://bugs.winehq.org/show_bug.cgi?id=2082 --- Comment #107 from Dan Kegel <dank(a)kegel.com> 2013-03-14 18:05:00 CDT --- Wine's still very much under active development. Just because your favorite bug hasn't been fixed doesn't mean a project is dead. See also comments 35-39 above. -- 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.

1 0

[Bug 2082] DirectDraw games only showing black screen
by wine-bugs＠winehq.org 14 Mar '13

14 Mar '13

http://bugs.winehq.org/show_bug.cgi?id=2082 --- Comment #106 from Johannes Bauer <JohannesBauer(a)gmx.de> 2013-03-14 17:41:18 CDT --- (In reply to comment #104) > However, it's worth noting if nobody has already that the Worms Armageddon > maintainers have implemented the "Use DesktopWindow" workaround (essentially > the same effect as the wine patches that were going around ages ago) into Worms > Armageddon itself (the game suggests you enable it when you first start it with > the newest update) so that the game will work in wine, at the cost of ingame > minimisation. Could you maybe elaborate on how that can be achieved? What do you mean by "ingame minimisation"? Would be happy to try out your suggestion. As to the Wine development and the question on why a 9 year old bug (!) is marked as NEW: It appears Wine is dead. No matter what they claim, action speak more than words. Does anyone know of a Wine fork by someone who actually gives a fuck? Johannes -- 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.

1 0

[Bug 2082] DirectDraw games only showing black screen
by wine-bugs＠winehq.org 14 Mar '13

14 Mar '13

http://bugs.winehq.org/show_bug.cgi?id=2082 Bob Johnson <muleyryan(a)fastmail.fm> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |muleyryan(a)fastmail.fm --- Comment #105 from Bob Johnson <muleyryan(a)fastmail.fm> 2013-03-14 16:51:18 CDT --- Any chance we can get a registry key put into mainline for this yet? -- 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.

1 0

[Bug 8854] Unable to get keyboard / mouse input in multiple games
by wine-bugs＠winehq.org 13 Mar '13

13 Mar '13

http://bugs.winehq.org/show_bug.cgi?id=8854 --- Comment #85 from Claudio <sick_soul(a)yahoo.it> 2013-03-13 14:52:29 CDT --- (In reply to comment #81) > (In reply to comment #80) > > Created attachment 40584 [details] > > Patch reverts code to earlier, working version > > > > This works for me with Morrowind; please could other users test. > > When is this going upstream? :) Any day now. This projects' approach to regressions is ridiculous. First the app works fine. Then someone decides to rewrite something in the Name of Progress(tm). The rewrite utterly breaks the applications. The actual reason why wine exists at all. Anyone with some sanity left in his brain at this point would just revert the patch: "sorry guys, we tried to make it better but we failed, we'll try again". Signal the developer that his patch does not work as it breaks the applications, and the developer would go back to the board to figure out how to reach his goals without breaking everything else in the process. And this, make no mistake, is how it works in less dysfunctional and pathological open source projects, the linux kernel in primis. But not here. Here patches that restore functionality for the users are vilified, complaints are ignored, and the code remains broken in the hope that eventually the users will go away. Do not worry, they (we) do. I am disgusted. -- 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.

1 0

[Bug 8854] Unable to get keyboard / mouse input in multiple games
by wine-bugs＠winehq.org 13 Mar '13

13 Mar '13

http://bugs.winehq.org/show_bug.cgi?id=8854 Miguel Sanjurjo <miguel(a)sanjurjo.eu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |miguel(a)sanjurjo.eu -- 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.

1 0

[Bug 33183] New: Lords of the Real fail to install
by wine-bugs＠winehq.org 12 Mar '13

12 Mar '13

http://bugs.winehq.org/show_bug.cgi?id=33183 Bug #: 33183 Summary: Lords of the Real fail to install Product: Wine Version: 1.5.25 Platform: x86 OS/Version: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: macmolder(a)gmail.com Classification: Unclassified Created attachment 43892 --> http://bugs.winehq.org/attachment.cgi?id=43892 BackTrace Lords of the Real fail to install -- 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.

1 2

[Bug 33181] New: Transcendence v1.1 : "MCIQTZ_mciSeek MCI_TO not implemented yet / Segmentation Fault"
by wine-bugs＠winehq.org 12 Mar '13

12 Mar '13

http://bugs.winehq.org/show_bug.cgi?id=33181 Bug #: 33181 Summary: Transcendence v1.1 : "MCIQTZ_mciSeek MCI_TO not implemented yet / Segmentation Fault" Product: Wine Version: 1.5.25 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: quartz AssignedTo: wine-bugs(a)winehq.org ReportedBy: moses-winehq(a)mozai.com Classification: Unclassified Created attachment 43889 --> http://bugs.winehq.org/attachment.cgi?id=43889 stdout/stderr output Transcendence 1.1 - http://neurohack.com/downloads/Trans110.zip Wine 1.5.25 - http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu/pool/main/w/wine1.5/wine1.5… program halts with a segfault. Console output attached. -- 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.

1 3