Region selection tools (box, circle, lasso) select extra vertices #47204

New Issue

Stanislav Blinov · 2016-01-18T20:08:42+01:00

Stanislav Blinov commented

2016-01-18 20:08:42 +01:00

System Information
Linux 64bit, NVIDIA GTS 450, driver 355.11

Blender Version
Broken: 2.76b, 2.76 c6bc236

This video (0.6Mb, 35 seconds) shows the erroneous behaviour:
https://www.dropbox.com/s/2ra3drex8ivah22/selection.mp4?dl=0

Note, this happens when multisampling is off. On my system, if I turn multisampling on, the tools behave normally.
The issue is originally mentioned in http://blenderartists.org/forum/showthread.php?390359-Box-and-circle-select-acting-strange-in-solid-drawing-mode

**System Information** Linux 64bit, NVIDIA GTS 450, driver 355.11 **Blender Version** Broken: 2.76b, 2.76 c6bc236 This video (0.6Mb, 35 seconds) shows the erroneous behaviour: https://www.dropbox.com/s/2ra3drex8ivah22/selection.mp4?dl=0 Note, this happens when multisampling is **off**. On my system, if I turn multisampling on, the tools behave normally. The issue is originally mentioned in http://blenderartists.org/forum/showthread.php?390359-Box-and-circle-select-acting-strange-in-solid-drawing-mode

Stanislav Blinov commented

2016-01-18 20:08:42 +01:00

Changed status to: 'Open'

Stanislav Blinov commented

2016-01-18 20:08:42 +01:00

Added subscriber: @Stan_Pancakes

Campbell Barton commented

2016-01-20 02:00:40 +01:00

Added subscriber: @ideasman42

Campbell Barton commented

2016-01-20 02:00:40 +01:00

Do you have multi-sampling enabled in the nvidia-settings, but disabled in Blender?
I've seen this cause issues before.

If all MSAA settings are off from the driver side, and off from Blender's preferences, this should always work properly.

Note that Blender requests no MSAA, if the graphics card is giving us a multi-sampled buffer its unlikely we can fix this - unless theres some known workaround.

Do you have multi-sampling enabled in the nvidia-settings, but disabled in Blender? I've seen this cause issues before. If all MSAA settings are off from the driver side, and off from Blender's preferences, this should always work properly. Note that Blender requests no MSAA, if the graphics card is giving us a multi-sampled buffer its unlikely we can fix this - unless theres some known workaround.

Bastien Montagne commented

2016-01-20 09:06:21 +01:00

Added subscriber: @mont29

Stanislav Blinov commented

2016-01-20 10:52:34 +01:00

I have no overrides in nvidia-settings:

If the driver was giving a multi-sampled buffer, wouldn't the resulting image reflect that? Perhaps it's not clear in the video, but there's no AA in viewport.

Also, I should mention that I went and checked with both selection methods (Select and Occlusion Queries), it still behaves like that.

I have no overrides in nvidia-settings: ![Screenshot from 2016-01-20 12-47-53.png](https://archive.blender.org/developer/F275296/Screenshot_from_2016-01-20_12-47-53.png) If the driver was giving a multi-sampled buffer, wouldn't the resulting image reflect that? Perhaps it's not clear in the video, but there's no AA in viewport. Also, I should mention that I went and checked with both selection methods (Select and Occlusion Queries), it still behaves like that.

Stanislav Blinov commented

2016-01-20 16:38:11 +01:00

Another update: I tried replicating this behavior with 2.75a on the same system, but with that version selection tools operate normally.

Bastien Montagne commented

2016-01-27 18:20:21 +01:00

Added subscribers: @MikeErwin, @brecht

Bastien Montagne commented

2016-01-27 18:20:21 +01:00

Did you try playing with other settings, e.g. disabling that 'texture sharpening' option, or if you have some global 'performance vs. quality' slider, etc?

Otherwise, unless some of our OpenGL team dev (@brecht, @MikeErwin, etc.) can replicate the issue, I doubt we can do much. :/

Did you try playing with other settings, e.g. disabling that 'texture sharpening' option, or if you have some global 'performance vs. quality' slider, etc? Otherwise, unless some of our OpenGL team dev (@brecht, @MikeErwin, etc.) can replicate the issue, I doubt we can do much. :/

Erick Tukuniata commented

2016-01-27 19:58:42 +01:00

Added subscriber: @ErickNyanduKabongo

Erick Tukuniata commented

2016-01-27 19:58:42 +01:00

I m having about the same problem in sculpt mode with mask lasso selection, I have win7 gtx 550ti and amd64 win 8, in both i have the same behavior. Hash c292b4e

Check video https://youtu.be/iAlmA1neGFo

I m having about the same problem in sculpt mode with mask lasso selection, I have win7 gtx 550ti and amd64 win 8, in both i have the same behavior. Hash c292b4e Check video https://youtu.be/iAlmA1neGFo

Stanislav Blinov commented

2016-01-28 14:11:21 +01:00

Neither 'Texture Sharpening' nor the OpenGL performance slider in nvidia-settings have an effect on this.

Erick Tukuniata commented

2016-01-28 19:16:22 +01:00

Here is with bones selection

https://youtu.be/7Er-Rcq3Z7A

Here is with bones selection https://youtu.be/7Er-Rcq3Z7A

Brecht Van Lommel commented

2016-01-30 16:28:04 +01:00

@ideasman42, looking for suspicious commits between 2.75 and 2.76, I found this one:

53d73c51a7. There is a glEnable(GL_MULTISAMPLE) without a restore of the previous state, which seems wrong to me. I'm not sure if there actually exist conditions under which this will cause trouble, but maybe something like .blend thumbnail save.

There were also lots of changes to ghost though, so it might be there too.

@ideasman42, looking for suspicious commits between 2.75 and 2.76, I found this one: 53d73c51a7. There is a `glEnable(GL_MULTISAMPLE)` without a restore of the previous state, which seems wrong to me. I'm not sure if there actually exist conditions under which this will cause trouble, but maybe something like .blend thumbnail save. There were also lots of changes to ghost though, so it might be there too.

Brecht Van Lommel commented

2016-01-30 16:31:47 +01:00

@Stan_Pancakes, does the problem happen after loading factory settings? It would be useful to know if perhaps some particular setting or addon is influencing this, besides the multisample setting.

@ErickNyanduKabongo, can you redo the problem in the original bug report? Can you redo the bugs you found in Blender 2.75, or do things work correctly there? It would be good to confirm if what you are seeing is actually the same bug.

@Stan_Pancakes, does the problem happen after loading factory settings? It would be useful to know if perhaps some particular setting or addon is influencing this, besides the multisample setting. @ErickNyanduKabongo, can you redo the problem in the original bug report? Can you redo the bugs you found in Blender 2.75, or do things work correctly there? It would be good to confirm if what you are seeing is actually the same bug.

Stanislav Blinov commented

2016-01-31 10:56:54 +01:00

@brecht, yes, it's factory settings. In fact, the video was recorded with factory settings as well. Sorry, I should have stated that more clearly to begin with.

Stanislav Blinov commented

2016-01-31 13:54:59 +01:00

@ErickNyanduKabongo, regarding lasso masking, AFAIK it always behaved this way: mask lasso always masks both front- and backfacing polygons, and with symmetry enabled, this results in what you show in your video.

The bone selection you're showing is also normal: selecting whole bone selects both its head and tail (and vice-versa). So, when you select the upper bone, its head is selected (which is also the head of middle bone). Then you select the lower bone, and its head gets selected (which is also the tail of middle bone). Thus, after selecting both of those bones, both the head and tail of middle bone are selected, so it's selected as well.

@ErickNyanduKabongo, regarding lasso masking, AFAIK it always behaved this way: mask lasso always masks both front- and backfacing polygons, and with symmetry enabled, this results in what you show in your video. The bone selection you're showing is also normal: selecting whole bone selects both its head and tail (and vice-versa). So, when you select the upper bone, its head is selected (which is also the head of middle bone). Then you select the lower bone, and its head gets selected (which is also the tail of middle bone). Thus, after selecting both of those bones, both the head and tail of middle bone are selected, so it's selected as well.

Erick Tukuniata commented

2016-01-31 16:29:16 +01:00

@brecht, now I couldn't redo the same behavior like op did. I remember I did reproduce something similar in my own old build and it is gone. The behavior comes randomly.

@Stan_Pancakes You are right i tried old Blender version, mask in sculpt mode and bone selection is like buggy normal behavior, my bad. :( One more thing that pushed me to show the video is the quick select and deselect that happen in my video about 23 sec, it is the same as photox showed in BA post#7. Probably it is an other problem here.

@brecht, now I couldn't redo the same behavior like op did. I remember I did reproduce something similar in my own old build and it is gone. The behavior comes randomly. @Stan_Pancakes You are right i tried old Blender version, mask in sculpt mode and bone selection is like buggy normal behavior, my bad. :( One more thing that pushed me to show the video is the quick select and deselect that happen in my video about 23 sec, it is the same as photox showed in BA post#7. Probably it is an other problem here.

Stanislav Blinov commented

2016-02-01 14:44:12 +01:00

Another update: on my system, but with a much older driver (340.96) the behaviour is still the same.

Campbell Barton commented

2016-02-03 08:29:59 +01:00

In #47204#355505, @brecht wrote:
@ideasman42, looking for suspicious commits between 2.75 and 2.76, I found this one:

53d73c51a7. There is a glEnable(GL_MULTISAMPLE) without a restore of the previous state, which seems wrong to me. I'm not sure if there actually exist conditions under which this will cause trouble, but maybe something like .blend thumbnail save.

Double checked and this commit wasn't in any of the 2.76 releases (timelines overlap, but wasn't merged into release branch).

The multi-sample state is stored/restored by glPushAttrib(GL_ENABLE_BIT...), which is popped on un-binding, and will restore the multi-sample state.

> In #47204#355505, @brecht wrote: > @ideasman42, looking for suspicious commits between 2.75 and 2.76, I found this one: > > 53d73c51a7. There is a `glEnable(GL_MULTISAMPLE)` without a restore of the previous state, which seems wrong to me. I'm not sure if there actually exist conditions under which this will cause trouble, but maybe something like .blend thumbnail save. Double checked and this commit wasn't in any of the 2.76 releases *(timelines overlap, but wasn't merged into release branch)*. The multi-sample state is stored/restored by `glPushAttrib(GL_ENABLE_BIT...)`, which is popped on un-binding, and will restore the multi-sample state.

Campbell Barton commented

2016-02-04 05:48:13 +01:00

@ErickNyanduKabongo, Please submit a new bug report with a file that has problems selecting armatures - its quite likely these bugs are unrelated.

Campbell Barton commented

2016-02-04 05:50:04 +01:00

In #47204#354307, @Stan_Pancakes wrote:
If the driver was giving a multi-sampled buffer, wouldn't the resulting image reflect that? Perhaps it's not clear in the video, but there's no AA in viewport.

Not necessarily, I've found with nvidia drivers on Linux - Blender disables multi-sampling which shows without any visible FSAA, but still causes problems with selection.

> In #47204#354307, @Stan_Pancakes wrote: > If the driver was giving a multi-sampled buffer, wouldn't the resulting image reflect that? Perhaps it's not clear in the video, but there's no AA in viewport. Not necessarily, I've found with nvidia drivers on Linux - Blender disables multi-sampling which shows without any visible FSAA, but still causes problems with selection.

Stanislav Blinov commented

2016-02-04 18:57:52 +01:00

@ideasman42, I've verified your suggestion. In all my test cases, I did Load Factory Settings in a Blender session that first loads my defaults (multisampling on, etc). I made a clean setup (removed startup.blend and userpref.blend), and the problem doesn't occur with it.

So, given the above, the actual reproduction route is:

Enable multisampling and save user preferences
Restart Blender (so that multisampling is actually enabled)
Load Factory Settings (or just disable multisampling)
Zoom out with mouse wheel two clicks
Edit mode, try to box/circle select vertices on the top edge of the nearest face - vertices in the opposing corners also get selected.

This doesn't happen in wireframe view, or with Limit Selection to Visible disabled.

Tested with two GPUs: GTS450 and GTX560, and two driver versions: 340.96 and 355.11. In all combinations the selection behaviour is the same.
The problem did not occur in 2.75a because for that version my user preferences don't have multisampling enabled by default, I've just verified that it does reproduce the issue as per steps above.
However, just to make sure, I went further back and tested with 2.74, and on that version, I cannot reproduce the problem at all.

If this is indeed a Linux driver issue then this particular problem should be documented somewhere (since people use Load Factory Settings to verify issues, it's pretty bad if it actually introduces a problem). I could do this if someone would point me in the right direction. Wiki?

@ideasman42, I've verified your suggestion. In all my test cases, I did Load Factory Settings in a Blender session that first loads my defaults (multisampling on, etc). I made a clean setup (removed startup.blend and userpref.blend), and the problem doesn't occur with it. So, given the above, the actual reproduction route is: 1. Enable multisampling and save user preferences 2. Restart Blender (so that multisampling is actually enabled) 3. Load Factory Settings (or just disable multisampling) 4. Zoom out with mouse wheel two clicks 5. Edit mode, try to box/circle select vertices on the top edge of the nearest face - vertices in the opposing corners also get selected. This doesn't happen in wireframe view, or with Limit Selection to Visible disabled. Tested with two GPUs: GTS450 and GTX560, and two driver versions: 340.96 and 355.11. In all combinations the selection behaviour is the same. The problem did not occur in 2.75a because for that version my user preferences don't have multisampling enabled by default, I've just verified that it does reproduce the issue as per steps above. However, just to make sure, I went further back and tested with **2.74**, and on that version, I cannot reproduce the problem at all. If this is indeed a Linux driver issue then this particular problem should be documented somewhere (since people use Load Factory Settings to verify issues, it's pretty bad if it actually introduces a problem). I could do this if someone would point me in the right direction. Wiki?

blender-admin commented

2016-02-06 12:21:41 +01:00

This issue was referenced by 6081f6c387

This issue was referenced by 6081f6c3870718660e984da3fbfcd44c55abcc20

Brecht Van Lommel commented

2016-02-06 12:22:52 +01:00

Changed status from 'Open' to: 'Resolved'

Brecht Van Lommel closed this issue

2016-02-06 12:22:52 +01:00

Brecht Van Lommel commented

2016-02-06 12:24:33 +01:00

Ok, if that's the issue then it should be fixed now, thanks for tracking this down.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Region selection tools (box, circle, lasso) select extra vertices #47204