All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 56534] [r600g] cayman msaa/fxaa buggy
Date: Mon, 16 Dec 2013 13:58:30 +0000	[thread overview]
Message-ID: <bug-56534-502-tlM0RrY83A@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-56534-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1166 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=56534

--- Comment #16 from Thomas Rohloff <v10lator@myway.de> ---
(In reply to comment #12)
> Is it any better with Catalyst?

Yes. With catalyst the FPS goes down while the scene looks anti-aliased. With
r600g the FPS and the scene stay the same.

(In reply to comment #13)
> is it also any better with current Mesa
> master?
I would love to answer you that question but master is currently a crash party
for me (3 of 4 tested games crashed at launch, with the one that worked it's
really hard to tell if anti-aliasing is working. So my only answer right now
can be a "maybe"). I might have to investigate more into this later and open a
new bug report.

(In reply to comment #14)
> Created attachment 90778 [details] [review]
> sRGB fix
> 
> Also, does this patch for Mesa improve MSAA?

Yes! But there are new bugs with it (tested with gary's mod: Colors are
generally darker, sometimes when looking at some things they get even more
dark. But screenshots look normal. Should I open a new bug report for it or is
that already known/fixed?).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2389 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2013-12-16 13:58 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-29 17:50 [Bug 56534] New: All anti-aliasing methods buggy at cayman bugzilla-daemon
2012-10-29 17:51 ` [Bug 56534] " bugzilla-daemon
2012-10-29 17:51 ` bugzilla-daemon
2012-10-29 17:52 ` bugzilla-daemon
2012-10-29 17:57 ` bugzilla-daemon
2012-10-29 18:09 ` bugzilla-daemon
2012-10-29 18:09 ` bugzilla-daemon
2012-10-29 18:10 ` bugzilla-daemon
2012-10-29 18:10 ` bugzilla-daemon
2013-01-21  2:20 ` bugzilla-daemon
2013-01-21 20:10 ` bugzilla-daemon
2013-04-24 18:31 ` [Bug 56534] [r600g] cayman msaa/mlaa/fxaa buggy bugzilla-daemon
2013-04-24 18:43 ` bugzilla-daemon
2013-05-17  3:42 ` bugzilla-daemon
2013-05-17 12:25 ` bugzilla-daemon
2013-12-04 22:40 ` bugzilla-daemon
2013-12-05 17:46 ` bugzilla-daemon
2013-12-05 17:46 ` bugzilla-daemon
2013-12-05 17:52 ` bugzilla-daemon
2013-12-13 21:35 ` bugzilla-daemon
2013-12-14 17:32 ` bugzilla-daemon
2013-12-14 17:34 ` bugzilla-daemon
2013-12-14 22:51 ` [Bug 56534] [r600g] cayman msaa/fxaa buggy bugzilla-daemon
2013-12-14 22:51 ` bugzilla-daemon
2013-12-16 13:58 ` bugzilla-daemon [this message]
2014-01-14 11:37 ` bugzilla-daemon
2014-02-01  0:53 ` bugzilla-daemon
2014-02-04  0:24 ` bugzilla-daemon
2014-02-04  4:59 ` bugzilla-daemon
2014-02-04 12:00 ` 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-56534-502-tlM0RrY83A@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.