From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 59322] r300g MSAA breaks Half-Life 2 in Wine
Date: Mon, 14 Jan 2013 19:02:28 +0000 [thread overview]
Message-ID: <bug-59322-502-SQZdXsMRsh@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-59322-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 586 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=59322
--- Comment #7 from Marek Olšák <maraeo@gmail.com> ---
Yes, the GALLIUM_MSAA environment variable might break some apps, because it
changes the default framebufer to MSAA, which adds lots of limitations to
BlitFramebuffer. For example, you can no longer use BlitFramebuffer to do a
stretched blit, because the ARB_fbo specification doesn't allow it if either
src or dst is multisample, etc.
That's why GALLIUM_MSAA should be used carefully.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1353 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
next prev parent reply other threads:[~2013-01-14 19:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 16:43 [Bug 59322] New: r300g MSAA breaks Half-Life 2 in Wine bugzilla-daemon
2013-01-13 16:57 ` [Bug 59322] " bugzilla-daemon
2013-01-13 19:05 ` bugzilla-daemon
2013-01-14 0:15 ` bugzilla-daemon
2013-01-14 10:51 ` bugzilla-daemon
2013-01-14 14:13 ` bugzilla-daemon
2013-01-14 14:36 ` bugzilla-daemon
2013-01-14 19:02 ` bugzilla-daemon [this message]
2013-07-15 2:54 ` bugzilla-daemon
2013-07-22 16:55 ` bugzilla-daemon
2013-07-22 16:57 ` bugzilla-daemon
2013-07-22 18:20 ` bugzilla-daemon
2013-07-30 20:44 ` 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-59322-502-SQZdXsMRsh@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