- User Since
- Mar 20 2015, 9:43 AM (234 w, 6 d)
Feb 9 2017
I'll be damned. Now that's a first : no bug if I turn on multisample in Blender (2 to 16). From the moment it is turned on, I can do whatever I want with the nvidia settings and blender settings, no issues. There's a little catch (would have been too easy): edges/faces are a little "blurry" especially when looking at from a distance and/or rotating around them. Not that annoying.
Testing procedure was to reset everything, starting with a default blender configuration and default nvidia settings in both Fedora 25 (system described here) and a laptop (Thinkpad T530 with Quadro NVS 5400M, xubuntu xenial x64, using nvidia-proprietary drivers from package manager). While the Fedora 25 setup was still subject to the bug, the laptop setup had no problem whatsoever, whatever settings I've tried with it.
Same results with both new and old blender settings. Turning multisample on in the Fedora 25 setup solves the issue in both default and old blender settings.
So, my guess here, to be taken with caution : it's an hardware issue, or maybe specifically the geforce GTX 750 Ti will only work with multisample on.
Thing is, I already had this issue for (a little more) than 8 months, so nvidia drivers used are way back. I'm quite certain you're absolutely right when you say it's related to the driver, and my guess is that it could be related to both nvidia+blender settings own configuration.
Now that I've tried disable everything (FSAA, multisample, v-blank etc etc) maybe I should try enabling everything (AA, etc etc).
I'm also gonna try on a different but close configuration with a new blender default configuration (latest xubuntu with nvidia GT 540).
Still, maybe it could help to know your own personal settings (both with nvidia and blender) please ? Is there a way to share efficiently these settings without being annoying for you ?
PS : if not, don't mind me, I wil investigate more on my own.
And here's my blender philosophical quotes of the day : you don't know how much useful lasso/circle selection is until you can't use them. Mark my words.
Thank you for the clarification. I was unsure myself about a high/normal priority, and unsure too about the bug assignment (I thought I should ask both Sergey and you, based on your involvement with T45284). So, again, thank you for your help !
As mentionned earlier for reference in T45284, using blender-softwaregl script is a workaround around the bug, but prevents both the use of opensubdiv compute and provokes glitches on meshes and UI.
Now, FSAA is disabled in nvidia-settings (linux proprietary nvidia control panel) and Multisample is disabled in Blender User Preferences. Triple Buffer is enabled, OpenGL threaded optimizations is enabled by nvidia (per se, since this latest nvidia driver has introduced an automatic switch based on performance/software requirements). Issue will occur whether I choose OpenGL Select or OpenGL Occlusion Queries in Blender User Preferences in System/Selection.
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).
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 - -'
Dec 17 2015
Very interesting option ! I can't find it anywhere thought.
Mar 20 2015
hmm ... indeed, no problem with Blender in factory settings, with "Tweak"/"Action" as default. I copied my settings from 2.73 to 2.74 so I'm not sure what went wrong there. For now I'm going to revert back to 2.73 official release see if anything changes, in the mean time, this bug report should be close as the problem seems to be specific to my setup (sorry about that !).
Thank you for your help and your quick answer.