http://bugs.winehq.org/show_bug.cgi?id=2082
--- Comment #104 from Murray Colpman muzerakascooby@gmail.com 2012-12-08 04:26:32 CST --- (In reply to comment #103)
(In reply to comment #96)
For what it's worth, running Fedora 16 with gnome shell and wine 1.5.2 Running Diablo, menu screen doesn't get rendered (black screen) but if use the hotcorner and display all running windows in the workspace the menu screen is rendered. Clicking back on the Diablo window still result in black screen.
Interesting! Your find inspired me to go look for some similar effect that could be used to work around the problem, and I found it could be done trough KDE's settings for the translucency effect.
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).
I also don't believe this would work in a virtual desktop, which people with multiple monitors (well, on my setup at least) pretty much require because otherwise nothing can get the damn resolution correct.
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.
-
wine-bugs＠winehq.org