From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107694] [wine] RAGE: texture problems
Date: Fri, 31 Aug 2018 01:24:54 +0000 [thread overview]
Message-ID: <bug-107694-502-ZSk8a6lDfI@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107694-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 805 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107694
Timothy Arceri <t_arceri@yahoo.com.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |NOTOURBUG
Status|NEW |RESOLVED
--- Comment #1 from Timothy Arceri <t_arceri@yahoo.com.au> ---
As far as I can tell this is a game bug that was never actually fixed. It seems
they did some transcoding on Nvidia via CUDA which helped reduce the problem
there but never bothered to fix it for AMD cards.
There are other config settings suggested I'm afraid you will just have to
experiment.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2265 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-08-31 1:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 18:58 [Bug 107694] [wine] RAGE: texture problems bugzilla-daemon
2018-08-31 1:24 ` bugzilla-daemon [this message]
2018-08-31 13:42 ` bugzilla-daemon
2018-08-31 15:23 ` bugzilla-daemon
2018-09-20 1:01 ` bugzilla-daemon
2018-09-20 8:40 ` bugzilla-daemon
2018-09-20 10:31 ` bugzilla-daemon
2018-09-20 10:49 ` bugzilla-daemon
2018-09-24 21:16 ` bugzilla-daemon
2019-01-06 13:50 ` bugzilla-daemon
2019-01-06 13:54 ` bugzilla-daemon
2019-07-15 12:32 ` bugzilla-daemon
2019-09-25 18:09 ` 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-107694-502-ZSk8a6lDfI@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