From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29363] New: [r300g] Starcraft 2: "r300 VP: Compiler error"
Date: Mon, 2 Aug 2010 09:14:21 -0700 (PDT) [thread overview]
Message-ID: <bug-29363-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=29363
Summary: [r300g] Starcraft 2: "r300 VP: Compiler error"
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: drakkk@centrum.cz
Created an attachment (id=37527)
--> (https://bugs.freedesktop.org/attachment.cgi?id=37527)
terminal output
When running with Wine 1.3.0 patched with slightly modified hack from bug
29137, I'm now able to start Starcraft 2, menus are working OK, however in game
almost everything is black.
mesa: afa925066c158ac49e3b0f883f67debd8545bf26
GPU: RV530
kernel: 2.6.35
Some chosen terminal output, full log attached:
r300 VP: Compiler error:
Vertex program has too many instructions
Using a dummy shader instead.
If there's an 'unknown opcode' message, please file a bug report and attach
this log.
fixme:d3d_shader:print_glsl_info_log Error received from GLSL shader #27:
fixme:d3d_shader:print_glsl_info_log Note: 'for (tmpInt0 ... )' body is too
large/complex to unroll
I'm not sure if this is only r300g bug, because some users with intel graphic
cards reported similar issues at Wine bugzilla,
http://bugs.winehq.org/show_bug.cgi?id=22971.
BTW disabling use of GLSL in Wine allows the terrain to be displayed more or
less properly, however units and buildings are still invisible
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-08-02 16:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 16:14 bugzilla-daemon [this message]
2010-08-02 16:15 ` [Bug 29363] [r300g] Starcraft 2: "r300 VP: Compiler error" bugzilla-daemon
2010-08-02 16:22 ` bugzilla-daemon
2010-08-02 16:50 ` bugzilla-daemon
2010-08-06 4:43 ` bugzilla-daemon
2010-08-06 5:10 ` bugzilla-daemon
2010-08-06 5:22 ` bugzilla-daemon
2010-08-06 15:03 ` bugzilla-daemon
2010-08-06 18:18 ` bugzilla-daemon
2010-08-06 19:24 ` bugzilla-daemon
2010-08-06 19:25 ` bugzilla-daemon
2010-08-06 19:28 ` bugzilla-daemon
2010-08-10 5:35 ` bugzilla-daemon
2010-08-10 8:16 ` bugzilla-daemon
2010-08-10 8:17 ` bugzilla-daemon
2010-08-11 10:29 ` bugzilla-daemon
2010-08-21 19:58 ` bugzilla-daemon
2010-08-23 13:01 ` bugzilla-daemon
2010-09-10 22:17 ` bugzilla-daemon
2010-09-23 7:11 ` bugzilla-daemon
2011-02-17 2:08 ` bugzilla-daemon
2011-02-17 2:11 ` bugzilla-daemon
2011-02-17 2:13 ` bugzilla-daemon
2011-02-17 2:18 ` bugzilla-daemon
2011-02-27 13:22 ` bugzilla-daemon
2011-02-28 0:58 ` bugzilla-daemon
2011-02-28 1:15 ` bugzilla-daemon
2011-02-28 10:52 ` bugzilla-daemon
2011-03-02 15:35 ` bugzilla-daemon
2011-03-02 15:40 ` bugzilla-daemon
2011-03-02 17:33 ` bugzilla-daemon
2011-03-05 2:16 ` bugzilla-daemon
2011-03-05 2:49 ` bugzilla-daemon
2011-03-05 12:19 ` 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-29363-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 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.