Smart Select - 1.4.0_beta_2 updated by Nburn is now out!


(Chris Sharp) #182

Just Purchased. Lots of cool potential. I can’t get loop and fill selections to work predictably though. It takes many attempts to get my actual intended selection. Often it’s selecting edges or faces on the backside or just other random loops. I’m trying this on pretty basic meshes like extruded cubes and cylinders. Unfortunately it’s not to the point where I could use it in production, but I’m happy to help work out the bugs. Love the Paint select.

(jimpaw80) #183

Thanks for the feedback! Hopefully this can be fixed rather soon, anyone know when the fully official Blender 2.8 version are suppose to be released?

(Chris Sharp) #184

I don’t think any one can say exactly, but I’ve heard May-June timeframe several times.

(JTenebrous) #185

Just an idea, but maybe if you could implement a way to selectively enable/disable features of the Smart Select suite in a modular fashion (through the Addons preferences panel), we could enable the features that are working for us while disabling the features that aren’t… it seems like bugfixing for 2.8 is something of a moving target. Smart Select’s Loop-Select features are currently an area with issues… personally, I could live with disabling them for a time. For me, the real every-day workflow killer features are mainly 1.) autofill of an area defined by manual “border” selections (where I select the outline and let Smart Select select all the geometry within) and 2.) “paint select”. Secondary (but still awesome) features include auto selection of coplanar surfaces (or defined by the surface derivation angle parameter) and auto selection using defined UV seams and “hard” edges, etc. Obviously, I like all the features of Smart Select, but I would be happy to just be getting on with a subset of those that are currently most stable in 2.8 beta.

(nBurn) #186

I noticed this myself over the weekend when I used a newer 2.80 build to try to solve another Smart Select bug. One of the Blender devs made a large number of API changes over the last few days and that seems to have broken a lot of stuff. I didn’t have these errors in the 2.80 builds from a week ago. I plan on having a fix for this with the next Smart Select update.

I’m not sure this is fixable. The reason this doesn’t is Blender changes how selections work when in wireframe mode. For example, if you double click on a face in solid mode, the selection stays the same, but if you double click on a face in wireframe mode, Blender will check to see if another face is behind the current selected face and selects that one instead.

Yes, current selection handling is problematic, I’m still looking into a fix for this one. As for disabling features, that’s a possibility, but I’m currently prioritizing fixing broken features. Hopefully that will not require too much work, but if it does I could add a disable option as a workaround.

(Dheim) #187

Any chance that the file I sent you via private message 8 days ago was helpful in tracking down the issue I’m running into? :slight_smile:

(nBurn) #188

I looked into this a little over the weekend, but still could not recreate the bug. :frowning:
Even with using the custom preferences files, Smart Select wasn’t throwing any errors to the console when activated or during use. What I think that may be causing that error is a conflict with another add-on.

(jimpaw80) #189

smart_select_1.4.0_beta_2 is out now, all buyers check your mailboxes!

(JTenebrous) #190

Him jimpaw80 - I’ve just opened up the 1.4.0_beta_2 and am using today’s build (28Feb19) of Blender 2.8 beta. I’m still experiencing the same issues with loop selection that I (and others) described in my last post. I even manually disabled Windows Display Scaling for Blender on my 4k display to make sure that wasn’t the issue (it made no difference). Basically, unless my attempt loop selection is pixel-perfect, it will loop select a random loop far away from the one I was trying to select. Will try again on the next addon beta update - good luck cracking this tricky one :).

(nBurn) #191

This update was just a quick fix for the tweak_threshold bug that showed up in recent builds. I’m still looking into the loop select issue, but I’ve not had much time to look into it this last week.