From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 34495] Selecting objects in Blender 2.56 slow with gallium r600
driver
Date: Fri, 1 Jul 2011 10:33:22 -0700 (PDT)
Message-ID: <20110701173322.ACF5413004F@annarchy.freedesktop.org>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
Received: from annarchy.freedesktop.org (annarchy.freedesktop.org
[131.252.210.176])
by gabe.freedesktop.org (Postfix) with ESMTP id BEDCA9E7DB
for ;
Fri, 1 Jul 2011 10:33:22 -0700 (PDT)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=34495
--- Comment #31 from Pierre-Eric Pelloux-Prayer 2011-07-01 10:33:20 PDT ---
(In reply to comment #29)
> More food for thought:
>
> Using an fbo which is bigger than 1x1 is a waste of space since we only want to
> know Z values. Using a 32x32 fbo with some custom shaders we could handle 32*32
> entries and so on.
>
> With some more shader magic maybe we could have the left half of the fbo for
> minZ values and the other half for maxZ values?
>
> Am I dreaming or is this doable?
I tried smaller FBO (8x8 I think), but the selection in Blender worked less
reliably. But maybe that was related to wrong Z values being returned, and thus
causing problem to Blender's selection algorithm.
And, using 2 FBO might not be that expensive 1) if they are small 2) if state
changes and read back are batched
But I'm far from being an expert, so I guess we'll need to build it first to
see if how well it performs.
Thanks for the help !
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.