From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 32888] [r600g] GL_EXT_texture_compression_s3tc support
Date: Tue, 15 Feb 2011 02:08:06 -0800 (PST) [thread overview]
Message-ID: <20110215100806.0F6052DC012@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-32888-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=32888
--- Comment #5 from Tobias Jakobi <liquid.acid@gmx.net> 2011-02-15 02:08:05 PST ---
Results with:
(i) new git master (including Dave's recent patches)
(ii) CS texture checking disabled
(iii) R600_ENABLE_S3TC=1
1) quake4 works flawlessly now, even with R600_FORCE_TILING=1
2) Max Payne 2 (through wine), where s3tc support is mandatory, also works.
Both tested in menu and ingame.
Enabling R600_FORCE_TILING doesn't show any obvious artifacts.
3) FEAR is still triggering GPU resets once you get ingame.
However this doesn't have to be related to texture compression support.
At least some textures are now visible, shortly before the driver
resets the GPU.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-02-15 10:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 2:22 [Bug 32888] New: [r600g] GL_EXT_texture_compression_s3tc support bugzilla-daemon
2011-02-01 21:57 ` [Bug 32888] " bugzilla-daemon
2011-02-06 15:50 ` bugzilla-daemon
2011-02-06 16:14 ` bugzilla-daemon
2011-02-09 10:39 ` bugzilla-daemon
2011-02-15 10:08 ` bugzilla-daemon [this message]
2011-02-17 8:06 ` bugzilla-daemon
2011-02-17 8:22 ` bugzilla-daemon
2011-02-17 12:10 ` bugzilla-daemon
2011-08-19 5:21 ` 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=20110215100806.0F6052DC012@annarchy.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).