From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93767] Glitches with soft shadows and MSAA in Knights of the Old Republic 2
Date: Thu, 31 Mar 2016 23:23:48 +0000 [thread overview]
Message-ID: <bug-93767-502-hKGc7PF3oS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93767-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 600 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93767
--- Comment #2 from Daniel Scharrer <daniel@constexpr.org> ---
> Note that Steam only offers the remastered version of KotOR2 now, which
> doesn't use ATI_fs anymore.
Yes, I'm talking about the remastered version (the only one that has a native
linux release). Did you test the original?
Anyway, I'm still seeing the glitches here. Soft shadows aren't any fainter
than hard shadows as far as I can tell.
GPU: R9 380X (tonga)
Mesa 11.3.0-devel (git-9076e04)
LLVM r265023
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1441 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:[~2016-03-31 23:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 6:28 [Bug 93767] Glitches with soft shadows and MSAA in Knights of the Old Republic 2 bugzilla-daemon
2016-01-19 6:35 ` bugzilla-daemon
2016-03-31 21:08 ` bugzilla-daemon
2016-03-31 23:23 ` bugzilla-daemon [this message]
2016-04-01 14:54 ` bugzilla-daemon
2016-04-01 15:48 ` bugzilla-daemon
2016-04-06 4:06 ` bugzilla-daemon
2016-04-06 6:22 ` bugzilla-daemon
2016-04-06 7:04 ` bugzilla-daemon
2016-04-06 14:36 ` bugzilla-daemon
2016-04-23 12:58 ` bugzilla-daemon
2016-04-23 15:42 ` bugzilla-daemon
2016-04-27 16:18 ` 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-93767-502-hKGc7PF3oS@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;
as well as URLs for NNTP newsgroup(s).