Bug 7392

Summary: Vertex selection bug with r300 driver in blender
Product: Mesa Reporter: popolon
Component: Drivers/DRI/r300Assignee: Default DRI bug account <dri-devel>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: high    
Version: git   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description popolon 2006-07-02 03:31:15 UTC
I tried the same test with software renderer and r300 accelerated renderer. With
blender-2.41 in native linux code and blender-2.42-rc2 for windows using wine
emulation (works fine too but with the same bug).

The bug is mostly on vertex selection. It occurs on blender only when back
culling is activated (little cube button titled "limit selection to visible
(clipped with depth buffer)"), and only in solid, shaded or textured display
(not in wireframe).

On this screen capture :
http://popolon.free.fr/Selection_bug.png

I selected the vertices with b key (rectangle selection)

* Up picture is the buggy selection in solid mode. only some vertices are
selected more or less randomly.
* Bottom picture is the good behavior in wireframe mode (all vertices are selected).

Face or edge selection works fine in every cases.

There is also a bug with lasso selection, the lasso is drawn on the screen
without selecting vertice, and the stroke don't disappear after move up mouse
button. I believe blender have to catch an event from Mesa/r300 driver that
doesn't come ???



I reported it on bug #6085 first (but with less informations), that was a bug
about blender crash, but this bug is closed as blender doesn't crash anymore.
Comment 1 Jerome Glisse 2006-10-08 09:51:23 UTC
Do you still experience this bug with current cvs ?
Comment 2 Jerome Glisse 2006-11-22 10:14:07 UTC
Closing, should be fixed (we weren't fallbacking on color logical op).
Comment 3 Adam Jackson 2009-08-24 12:24:00 UTC
Mass version move, cvs -> git

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.