From: Paul Menzel <paulepanter@users.sourceforge.net>
To: dri-devel@lists.freedesktop.org
Cc: Mike Mestnik <cheako@mikemestnik.net>
Subject: Re: r600: In Diablo III when the ground is covered in water, it's all messed-up.
Date: Thu, 10 May 2012 08:57:34 +0200 [thread overview]
Message-ID: <1336633054.4066.4.camel@mattotaupa> (raw)
In-Reply-To: <4FAB171B.6030305@mikemestnik.net>
[-- Attachment #1.1: Type: text/plain, Size: 903 bytes --]
Dear Mike,
I have to remarks that unfortunately will not give a solution.
Am Mittwoch, den 09.05.2012, 20:17 -0500 schrieb Mike Mestnik:
> I found a rendering error in Diablo III, in a well there ground is
> covered in water and it's all red and flickers.
>
> http://c566453.r53.cf2.rackcdn.com/DiabloIII-well-wine-preloader.trace.xz 3.5G,
> 234665296 Bytes compressed ~234M.
>
> EE r600_shader.c:1605 r600_shader_from_tgsi - GPR limit exceeded -
> shader requires 181 registers
> EE r600_shader.c:140 r600_pipe_shader_create - translation from TGSI
> failed !
> Rendered 621 frames in 80.724 secs, average of 7.69288 fps
1. Please turn off line wrapping for paragraphs were you paste code.
2. I guess the developers need more information what your system set up
is. That means your distribution and the program versions you are
running.
Thanks and good luck,
Paul
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 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
prev parent reply other threads:[~2012-05-10 7:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 1:17 In Diablo III when the ground is covered in water, it's all messed-up Mike Mestnik
2012-05-10 6:57 ` Paul Menzel [this message]
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=1336633054.4066.4.camel@mattotaupa \
--to=paulepanter@users.sourceforge.net \
--cc=cheako@mikemestnik.net \
--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).