[Bug 34495] Selecting objects in Blender 2.56 slow with gallium r600 driver

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Jul 1 08:10:17 PDT 2011


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

--- Comment #26 from Micael Dias <kam1kaz3 at gmail.com> 2011-07-01 08:10:16 PDT ---
@Pierre: After looking at your patch for a while I have the following
doubts/suggestions:

1) on _mesa_exec_select_batch() why would you loop through buffer[..] for each
batch entry? at first sight it seems to me that if there is more than one
entry, the minZ and maxZ values written by write_hit_record would be the same
for every entry.

2) What happens if the user changes the fbo or any state needed (depth and
scissor) after calling "glRenderMode(GL_SELECT)"? Maybe we should create our
st_select_draw_vbo that makes sure to have the correct state->render using
st_draw_vbo->restore state. It is possible that this could be a little heavy on
state changes but it feels safer... Maybe we could implement some kind of
"state-override" later to make sure we only restore states after exiting
GL_SELECT mode and still be sure that the end user isn't interfering with our
GL_SELECT implementation.

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


More information about the dri-devel mailing list