From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 57918] New: Amnesia causes shader compiler errors on RV350 with high graphics settings
Date: Wed, 05 Dec 2012 18:16:25 +0000 [thread overview]
Message-ID: <bug-57918-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1180 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=57918
Priority: medium
Bug ID: 57918
Assignee: dri-devel@lists.freedesktop.org
Summary: Amnesia causes shader compiler errors on RV350 with
high graphics settings
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: oreaus@gmail.com
Hardware: All
Status: NEW
Version: git
Component: Drivers/Gallium/r300
Product: Mesa
Created attachment 71034
--> https://bugs.freedesktop.org/attachment.cgi?id=71034&action=edit
Amnesia output with RADEON_DEBUG=fp using Shadow Quality = High
Testing Amnesia on RV350, I've found that setting 'Shadow Quality' to 'High' in
game settings causes the error:
r300 FP: Compiler Error:
compiler/r300_fragprog_emit.c::emit_alu(): Too many ALU instructions
More information:
Distro: Xubuntu 12.04 32bit
Kernel: 3.5.0-18-generic
Mesa: ec83535c83c748b067ecf4548e5396fef8719725
libtxc_dxtn.so installed
I have attached the output with RADEON_DEBUG=fp.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2707 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 reply other threads:[~2012-12-05 18:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 18:16 bugzilla-daemon [this message]
2019-09-18 18:51 ` [Bug 57918] Amnesia causes shader compiler errors on RV350 with high graphics settings 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-57918-502@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