From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99403] Graphical glitches in witcher-1 with wine nine and r600g (rv740).
Date: Fri, 06 Apr 2018 15:27:11 +0000 [thread overview]
Message-ID: <bug-99403-502-ngeeSLK8AM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99403-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 575 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99403
--- Comment #7 from iive@yahoo.com ---
It's not driver specific bug.
I should have followed the hint that there is a registry entry to workaround
this problem with wined3d. It turns out that this registry entry is
specifically for this bug. The analysis and possible solutions could be found
here:
https://bugs.winehq.org/show_bug.cgi?id=34052#c42
Also, this bug is also tracked at:
https://github.com/iXit/Mesa-3D/issues/312
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1479 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-04-06 15:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 21:03 [Bug 99403] Graphical glitches in witcher-1 with wine nine and r600g (rv740) bugzilla-daemon
2017-03-21 7:38 ` bugzilla-daemon
2018-04-01 10:16 ` bugzilla-daemon
2018-04-01 12:42 ` bugzilla-daemon
2018-04-01 20:01 ` bugzilla-daemon
2018-04-02 8:48 ` bugzilla-daemon
2018-04-02 19:20 ` bugzilla-daemon
2018-04-06 15:27 ` bugzilla-daemon [this message]
2018-05-09 15:11 ` bugzilla-daemon
2018-05-10 15:25 ` bugzilla-daemon
2018-05-12 5:36 ` bugzilla-daemon
2018-05-12 11:49 ` bugzilla-daemon
2018-05-13 7:12 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-99403-502-ngeeSLK8AM@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox