selection of face and edges selecting in unpredictable, random locations #45284

New Issue

latt · 2015-07-03T03:20:20+02:00

latt commented

2015-07-03 03:20:20 +02:00

System Information
Linux Mint 17.1 Cinnamon 64-bit version 2.4.8, Core I7, Nvidia GT218 [GeForce 210]

Blender Version
Broken: 2.75.7 c6b042b
Worked: (optional)

Short description of error
with "limit selection to visible" enabled and without any modifiers present, when selecting edge or faces with SHIFT+Right click, or with box selection, or with circle selection, the faces targeted are being selected but so are other areas of the mesh in unpredictable places. This is not happening with vertices selection, and the problem is worse for face selection than it is with the edge selection in that it seems to select a greater number of faces that were unintended. The same issue applies to deselecting as well, when attempting to deselect a face, other faces are being deselected from other areas on the mesh.

Exact steps for others to reproduce the error
Using the default scene, select the cube, enter edit mode, and subdivide 3 times or more. Change selection mode to "face". Use circle select and drag on a corner of the subdivided cube. I see random patches of selection on the cube in different spots.
issue.zip

**System Information** Linux Mint 17.1 Cinnamon 64-bit version 2.4.8, Core I7, Nvidia GT218 [GeForce 210] **Blender Version** Broken: 2.75.7 c6b042b Worked: (optional) **Short description of error** with "limit selection to visible" enabled and without any modifiers present, when selecting edge or faces with SHIFT+Right click, or with box selection, or with circle selection, the faces targeted are being selected but so are other areas of the mesh in unpredictable places. This is not happening with vertices selection, and the problem is worse for face selection than it is with the edge selection in that it seems to select a greater number of faces that were unintended. The same issue applies to deselecting as well, when attempting to deselect a face, other faces are being deselected from other areas on the mesh. **Exact steps for others to reproduce the error** Using the default scene, select the cube, enter edit mode, and subdivide 3 times or more. Change selection mode to "face". Use circle select and drag on a corner of the subdivided cube. I see random patches of selection on the cube in different spots. [issue.zip](https://archive.blender.org/developer/F199855/issue.zip)

latt commented

2015-07-03 03:20:20 +02:00

Changed status to: 'Open'

latt commented

2015-07-03 03:20:20 +02:00

Added subscriber: @lattbox

Bastien Montagne commented

2015-07-03 09:12:02 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2015-07-03 09:12:02 +02:00

This is most probably an OpenGL/driver issue related to selection method. Please try to tweak Selection Method setting in UserPreferences, System tab.

latt commented

2015-07-07 02:06:07 +02:00

hmm. Tried changing the selection preferences without any luck. I tried the install on my laptop with Ubuntu 14 using the exact same .tar file and it worked without any issue, so maybe I am out of luck on this desktop. I updated my drivers on Mint and it didn't solve the problem.

Any other ideas?

hmm. Tried changing the selection preferences without any luck. I tried the install on my laptop with Ubuntu 14 using the exact same .tar file and it worked without any issue, so maybe I am out of luck on this desktop. I updated my drivers on Mint and it didn't solve the problem. Any other ideas?

Sergey Sharybin commented

2015-07-07 21:40:05 +02:00

Added subscriber: @Sergey

Sergey Sharybin commented

2015-07-07 21:40:05 +02:00

This actually smells exactly the same as #45292..

Things to try:

Make sure multisampels are disabled (requires blender restart)
Make sure there's no forces FSAA in the driver options
Try using opengl32.dll from ftp://ftp.blender.org/sergey/softwaregl/ (put it next to blender.exe). This will switch blender to fully software opengl mode, which is slower but will let us understand if it's something to do with opengl or not.

This actually smells exactly the same as #45292.. Things to try: Make sure multisampels are disabled (requires blender restart) Make sure there's no forces FSAA in the driver options Try using opengl32.dll from ftp://ftp.blender.org/sergey/softwaregl/ (put it next to blender.exe). This will switch blender to fully software opengl mode, which is slower but will let us understand if it's something to do with opengl or not.

latt commented

2015-07-08 01:35:11 +02:00

I'm fairly new to Blender, I tried to find the options you mentioned.

multisamples is disabled. Restarted blender. problem persists.
I'm on linux, but I downloaded the dll file and put it in my blender folder. I'm not sure blender is using it. I included a screenshot. I tried removing the blender-softwaregl thinking that may force the executable to use the other resource (not even sure if they're the same). In both cases I had the same result. Things ran but the selection problem was still there.

I'm fairly new to Blender, I tried to find the options you mentioned. - multisamples is disabled. Restarted blender. problem persists. - I'm on linux, but I downloaded the dll file and put it in my blender folder. I'm not sure blender is using it. I included a screenshot. I tried removing the blender-softwaregl thinking that may force the executable to use the other resource (not even sure if they're the same). In both cases I had the same result. Things ran but the selection problem was still there. ![folder.png](https://archive.blender.org/developer/F204483/folder.png)

latt commented

2015-07-08 01:41:29 +02:00

I found the anti-Aliasing option and disabled it. problem is still present.

latt commented

2015-07-08 01:51:52 +02:00

I tried with the 32 bit download for version 2.75 and I tried with 64 bit version of 2.60. All are having the same problem on my OS set up. I boot from an external drive. I tried on a different computer with same graphics card and processor, but different screen, etc. Same issue.

I checked my system's openGL driver version using this:

glxinfo | grep "OpenGL version"

OpenGL version string: 3.0 Mesa 10.1.3

I don't know if any of this is useful.

I tried with the 32 bit download for version 2.75 and I tried with 64 bit version of 2.60. All are having the same problem on my OS set up. I boot from an external drive. I tried on a different computer with same graphics card and processor, but different screen, etc. Same issue. I checked my system's openGL driver version using this: >>> glxinfo | grep "OpenGL version" OpenGL version string: 3.0 Mesa 10.1.3 I don't know if any of this is useful.

latt commented

2015-07-08 01:57:37 +02:00

Found something! If I turn on "smooth" under shading the problem doesn't happen. If I switch it back to "flat" it comes back! With Flat selected, I tested turning off and on the options in the shading panel:
None of these options made a difference.

Setting it to "Smooth" shading, however, seems to prevent the problem.

Found something! If I turn on "smooth" under shading the problem doesn't happen. If I switch it back to "flat" it comes back! With Flat selected, I tested turning off and on the options in the shading panel:![pic.png](https://archive.blender.org/developer/F204498/pic.png) None of these options made a difference. Setting it to "Smooth" shading, however, seems to prevent the problem.

Sergey Sharybin commented

2015-07-08 12:15:17 +02:00

Ah, didn't notice it's linux. Must have been confused with some other report..

On linux you can run blender-softwaregl script which is included into official release archive and see if it makes any difference.

Ah, didn't notice it's linux. Must have been confused with some other report.. On linux you can run blender-softwaregl script which is included into official release archive and see if it makes any difference.

latt commented

2015-07-11 21:08:05 +02:00

I ran using the blender-softwaregl and the problem did not occur.

Bastien Montagne commented

2015-07-18 21:19:01 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2015-07-18 21:19:01 +02:00

Bastien Montagne self-assigned this 2015-07-18 21:19:01 +02:00

Bastien Montagne commented

2015-07-18 21:19:01 +02:00

Well, this shows issue is with your graphic driver. It may be that you are using open source one instead of official NVidia one?

In any case, thanks for the report, but we cannot do much about it here.

Well, this shows issue is with your graphic driver. It may be that you are using open source one instead of official NVidia one? In any case, thanks for the report, but we cannot do much about it here.

latt commented

2015-07-19 21:09:53 +02:00

thanks. Keep up the good work.

Mediaklan commented

2017-02-09 01:24:15 +01:00

Added subscriber: @mediaklan

Mediaklan commented

2017-02-09 01:24:15 +01:00

Changed status from 'Archived' to: 'Open'

Mediaklan reopened this issue

2017-02-09 01:24:15 +01:00

Mediaklan commented

2017-02-09 01:24:15 +01:00

Hi everyone !
While I'm a bit reluctant to reopen a closed case, I can't see another solution since I'm still having the exact same issue, with the exact same conditions (replace Linux Mint by Fedora 25 x64, nvidia GTX 750 Ti, NVIDIA-Linux-x86_64-378.09 proprietary drivers and Blender 2.78a).
The blender-softwaregl script is a workaround, but both prevents the use of opensubdiv compute and provokes glitches on meshes and UI.
I think I've tried almost every settings (along with the ones suggests here, even those not supposed to work) in both Blender and Nvidia settings, but I'm clearly open to others suggestions to try ^^ (this bug has a serious way to hurt a workflow, even for an amateur like me).
If you need anything to investigate further, please ask.
Thank you and sorry again for the 2 years old deep bug renaissance - -'

Hi everyone ! While I'm a bit reluctant to reopen a closed case, I can't see another solution since I'm still having the exact same issue, with the exact same conditions (replace Linux Mint by Fedora 25 x64, nvidia GTX 750 Ti, NVIDIA-Linux-x86_64-378.09 proprietary drivers and Blender 2.78a). The blender-softwaregl script is a workaround, but both prevents the use of opensubdiv compute and provokes glitches on meshes and UI. I think I've tried almost every settings (along with the ones suggests here, even those not supposed to work) in both Blender and Nvidia settings, but I'm clearly open to others suggestions to try ^^ (this bug has a serious way to hurt a workflow, even for an amateur like me). If you need anything to investigate further, please ask. Thank you and sorry again for the 2 years old deep bug renaissance - -'

Sergey Sharybin commented

2017-02-09 09:09:56 +01:00

First of all, please submit new report instead of re-opening the issue. Otherwise trying to dig relevant information becomes quite tedious.

Second of all, make sure you don't force FSAA in the video driver settings. Also try disabling multisample in viewport (you'll need to restart blender after that).

First of all, please submit new report instead of re-opening the issue. Otherwise trying to dig relevant information becomes quite tedious. Second of all, make sure you don't force FSAA in the video driver settings. Also try disabling multisample in viewport (you'll need to restart blender after that).

Mediaklan commented

2017-02-09 11:19:11 +01:00

This comment was removed by @mediaklan

*This comment was removed by @mediaklan*

Mediaklan commented

2017-02-09 11:22:12 +01:00

Changed status from 'Open' to: 'Resolved'

Mediaklan closed this issue

2017-02-09 11:22:12 +01:00

Mediaklan commented

2017-02-09 11:22:12 +01:00

OK, I'm going to submit a new report if it's not redundant. Thank you Sergey (and again sorry about that, I was unsure about the benefit of creating new bug against reusing a closed one, now I know why its better to create a new one). Should I still mention this closed bug into the new one as a reference ?
FSAA and multisample both disabled, blender restarted, issue still there (that was my first thing tried I think).

OK, I'm going to submit a new report if it's not redundant. Thank you Sergey (and again sorry about that, I was unsure about the benefit of creating new bug against reusing a closed one, now I know why its better to create a new one). Should I still mention this closed bug into the new one as a reference ? FSAA and multisample both disabled, blender restarted, issue still there (that was my first thing tried I think).

Bastien Montagne commented

2017-02-09 12:00:18 +01:00

Changed status from 'Resolved' to: 'Archived'

Bastien Montagne commented

2017-02-09 12:00:18 +01:00

Yes, mentionning older similar bugs in new one is totally worth it, good practice.

Closing this one now.

Yes, mentionning older similar bugs in new one is totally worth it, good practice. Closing this one now.

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

selection of face and edges selecting in unpredictable, random locations #45284