All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36236] Problems with lights in Trine game from www.humblebundle.com
Date: Sun, 24 Apr 2011 05:21:00 -0700 (PDT)	[thread overview]
Message-ID: <20110424122100.BEE6713004F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-36236-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=36236

--- Comment #35 from Sven Arvidsson <sa@whiz.se> 2011-04-24 05:21:00 PDT ---
(In reply to comment #34)
> 
> That's odd, at least on r300g the bug is still there, and I'm using Trine 1.32.

Actually, forget that. I should learn to do a git pull before commenting on
bugs. It looks like a fix was commited:

commit d7f4c4e1b187552ede397f00fb56a6f0bb724ce1
Author: Eric Anholt <eric@anholt.net>
Date:   Wed Apr 20 16:49:19 2011 -0700

    mesa: Fix fragment.color (no index) writes with OPTION ARB_draw_buffers.

    Fixes a bug in Trine where fragment.color would write
    FRAG_RESULT_COLOR (which is interpreted by drivers as being the "write
    this to all color buffers" option) instead of FRAG_RESULT_DATA0 (just
    the first target).

    Fixes piglit ATI_draw_buffers/arbfp-no-index.


The game renders fine, so I guess this bug report can be closed now.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2011-04-24 12:21 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14 14:56 [Bug 36236] New: Problems with lights in Trine game from www.humblebundle.com bugzilla-daemon
2011-04-14 15:39 ` [Bug 36236] " bugzilla-daemon
2011-04-14 16:02 ` bugzilla-daemon
2011-04-14 20:28 ` bugzilla-daemon
2011-04-14 22:47 ` bugzilla-daemon
2011-04-15 10:24 ` bugzilla-daemon
2011-04-15 10:26 ` bugzilla-daemon
2011-04-15 10:29 ` bugzilla-daemon
2011-04-15 10:37 ` bugzilla-daemon
2011-04-15 12:56 ` bugzilla-daemon
2011-04-15 12:57 ` bugzilla-daemon
2011-04-15 13:19 ` bugzilla-daemon
2011-04-15 13:35 ` bugzilla-daemon
2011-04-15 14:06 ` bugzilla-daemon
2011-04-15 16:34 ` bugzilla-daemon
2011-04-16 14:02 ` bugzilla-daemon
2011-04-19  4:10 ` bugzilla-daemon
2011-04-19  9:59 ` bugzilla-daemon
2011-04-19 11:48 ` bugzilla-daemon
2011-04-19 11:48 ` bugzilla-daemon
2011-04-19 13:34 ` bugzilla-daemon
2011-04-20  9:59 ` bugzilla-daemon
2011-04-20 10:54 ` bugzilla-daemon
2011-04-20 10:54 ` bugzilla-daemon
2011-04-20 11:51 ` bugzilla-daemon
2011-04-20 12:08 ` bugzilla-daemon
2011-04-20 13:03 ` bugzilla-daemon
2011-04-20 15:48 ` bugzilla-daemon
2011-04-20 16:08 ` bugzilla-daemon
2011-04-20 16:19 ` bugzilla-daemon
2011-04-20 16:47 ` bugzilla-daemon
2011-04-20 16:58 ` bugzilla-daemon
2011-04-21  1:06 ` bugzilla-daemon
2011-04-24  1:25 ` bugzilla-daemon
2011-04-24 12:13 ` bugzilla-daemon
2011-04-24 12:21 ` bugzilla-daemon [this message]
2011-04-24 15:51 ` bugzilla-daemon
2011-04-24 16:48 ` bugzilla-daemon
2011-05-06 16:11 ` bugzilla-daemon
2011-05-07 14:59 ` bugzilla-daemon
2011-05-07 15:07 ` bugzilla-daemon
2011-05-08 14:09 ` 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=20110424122100.BEE6713004F@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 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.