[Bug 34704] New: Duel of the Planeswalkers 2014 - eventual UI corruption
http://bugs.winehq.org/show_bug.cgi?id=34704 Bug #: 34704 Summary: Duel of the Planeswalkers 2014 - eventual UI corruption Product: Wine Version: 1.7.4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: Goblinstomper(a)gmail.com Classification: Unclassified This is a rather minor problem, but in case it is a symptom of a problem effecting other applications I'm reporting it anyway. What happens: During the loading/process of setting up the 'table' my screen will first go black momentarily and once the loading process is actually complete, the "board" will be displayed however certain elements of the UI will be missing, such as buttons, text and some graphical effects. How to reproduce: (Steam version, demo available, using FGLRX and wine 1.7.4) Start a game as normal, when the actual 'virtual table' has loaded and you're able to decide between keeping your seven cards or draw new ones - press escape and select "Restart Duel" (it is not limited to restarting, any new match will do, restarting is merely quicker) about 20 times >_> eventually the UI will become corrupt. The corruption will coincide with two lines of err:d3d, and a trace yields: trace:d3d:context_set_current Switching to D3D context 0x190396a0, GL context 0x10003, device context 0x2006a. trace:d3d:swapchain_get_backup_dc Creating the backup window for swapchain 0x1bb3b8. err:d3d:context_set_gl_context Fallback to backup window (dc 0xc0087) failed too, last error 0x6. trace:d3d:context_set_current Already using D3D context (nil). err:d3d:context_acquire Failed to activate the new context. trace:d3d:context_bind_texture glBindTexture call ok context.c / 2027 trace:d3d:context_release Releasing context 0x190396a0, level 1. now, if that's actually relevant... -- 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.
https://bugs.winehq.org/show_bug.cgi?id=34704 christian.erdmann(a)tu-dortmund.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |christian.erdmann(a)tu-dortmu | |nd.de --- Comment #1 from christian.erdmann(a)tu-dortmund.de --- Created attachment 50290 --> https://bugs.winehq.org/attachment.cgi?id=50290 Text and texture corruption in Magic 2014 -- 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=34704 --- Comment #2 from christian.erdmann(a)tu-dortmund.de --- Created attachment 50291 --> https://bugs.winehq.org/attachment.cgi?id=50291 Text corruption in Dark Messiah of Might and Magic -- 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=34704 --- Comment #3 from christian.erdmann(a)tu-dortmund.de --- I can confirm this. It started happening on both of my systems recently: Desktop PC: 3.16.3-gentoo x86_64 Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz GenuineIntel GNU/Linux Nvidia GeForce GTX660 Ti (proprietary driver version 346.22) Wine 1.7.29 Laptop: 3.14.27-gentoo x86_64 Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz GenuineIntel GNU/Linux Intel HD4000 integrated GPU Wine 1.7.29 I tested: Duels of the Planeswalkers 2013, Magic 2014, Dark Messiah of Might and Magic. Symptoms are: Gradual UI and texture corruption, corruption after changing graphics settings, garbled fonts, missing text, black textures (screenshots attached). On both of my systems libtxc_dxtn (1.0.1) is installed. Unfortunately I don't know what I changed, that causes 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=34704 --- Comment #4 from christian.erdmann(a)tu-dortmund.de --- Created attachment 50292 --> https://bugs.winehq.org/attachment.cgi?id=50292 Text and texture corruption in Magic 2014 example 2 -- 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=34704 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian(a)fds-team.de --- Comment #5 from Sebastian Lackner <sebastian(a)fds-team.de> --- Try with the latest wine development version, there was a texture corruption regression a couple of releases ago, which was already fixed in the meantime. -- 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=34704 --- Comment #6 from christian.erdmann(a)tu-dortmund.de --- Confirmed fixed on wine-1.7.33-64-g299a480, let's hope this makes it into the portage tree quickly then. -- 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=34704 Bruno Jesus <00cpxxx(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Bruno Jesus <00cpxxx(a)gmail.com> --- (In reply to christian.erdmann from comment #6)
Confirmed fixed on wine-1.7.33-64-g299a480, let's hope this makes it into the portage tree quickly then.
Resolving fixed. -- 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=34704 --- Comment #8 from Goblinstomper(a)gmail.com --- Original issue still present in 1.7.33.20141224.1557-1.1 (latest I can get from available repo's and I can't figure out what build it is based on) but at least it appears to be later than the build used in #6. -- 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=34704 Bruno Jesus <00cpxxx(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #9 from Bruno Jesus <00cpxxx(a)gmail.com> --- (In reply to Goblinstomper from comment #8)
Original issue still present in 1.7.33.20141224.1557-1.1 (latest I can get from available repo's and I can't figure out what build it is based on) but at least it appears to be later than the build used in #6.
Since you are the OP and is still able to reproduce I'm reopening. -- 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=34704 super_man(a)post.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Goblinstomper(a)gmail.com, | |super_man(a)post.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.
https://bugs.winehq.org/show_bug.cgi?id=34704 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest(a)luukku.com --- Comment #10 from winetest(a)luukku.com --- (In reply to Goblinstomper from comment #8)
Original issue still present in 1.7.33.20141224.1557-1.1 (latest I can get from available repo's and I can't figure out what build it is based on) but at least it appears to be later than the build used in #6.
So much time has passed meanwhile that you should retest this bug against newer wine. I would it myself but I don't own this 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.
participants (1)
-
wine-bugs＠winehq.org