Could you guys please state what OS and build versions you’re using? (you can see that in the splash screen, it’s on the top menu -> Help -> Splash Screen).
I’m now seeing that it’ll be safer, the next time a build changes in a way that breaks addons, to code the script in a flexible way that works with both the old and new ways, at least while 2.80 is in Beta.
I mean something like this. Green is the curve. Red - imaginary face. center is on curve, normal depends on curve tangent. Yellow - vertexes in falloff range. When snapping occur - they should move into direction of snapping (proportionally) - projecting position on corresponding imaginary face. dotted yellow - vertex from other side of mesh
may be this is not good suggestion. But snapping still need an option (not always!) to smooth surrounding mesh according to snapping. to avoid such distorted (after snapping) edges. sometimes such edges is exactly what is needed… sometimes not
I’m on Win10.
Just tried the March 21 build. It seems that this issue has nothing to do with the Blender version but with the keymap. It works just fine with Blender’s default keymap but as soon as I switch to my own and try to use the addon I get this error. Both use Left Click select so I have no idea why there’s a problem…
@bassig Thanks for the report. I’m on a different computer right now with only 2.79, but it seems to work in here. I can look at 2.80 tomorrow.
- Can you map the wheel-up/wheel-down to any of the other tools (like Mesh Extrude, Bevel etc.), does it give any warnings?
- Is there anything useful in the system console (top menu -> Window -> System Console)? Just remember to use that same menu to hide the console, 'cause if you try to close the window it will close Blender.
Thanks. I can’t say I know that one (I never used Softimage, but I heard great things about it).
A foreign tool that did inspire me was the Adjust Weights from Modo, it became my Adjust Vertex Weights, it’s just genious.
Looks like that wm.keyitem_restore operator changed namespace to preferences.keyitem_restore. Thanks for looking the information.
Besides that fix, I also added a couple of new actions to the Snap To Curve menu: instead of distributing things evenly, they use the original distance from one vertex to the next (AKA “chordal length”):
Nice, that works like a charm.
Another thing that comes to mind: could we be allowed to remap the cancel button too? ESC instead of RMB (or simply RMB-click instead of RMB-press) would be nice for me since I’ve set RMB-Tweak to rotate viewport.
I noticed a bug - if I click snap smooth(proportional) it works.
But if I first unbound a curve, modify it, rebound it and than click snap smooth (proportional), is says “force primary vertices must be on” even though it is already on.
Hi @bassig, you can do a text replacement to change that, if that’s okay.
Open the script file in a text editor like Notepad, press Ctrl + H to bring the text replacement dialog, then copy these lines as they are.
The search text: self.rightMouseCancel = 'RIGHTMOUSE'
The replacement is: self.rightMouseCancel = ''
After you save the script and install it, this will ignore the cancelling from the right-button presses. If you want, I can send you a copy with this change.
If you find that this change works well then we can put it as a new setting =D
Hi @JLBohm, thanks bringing this up. It’s kind of a paradox, I’ll explain.
After you unbind the curve --so you’re able to move it by itself, without affecting the mesh-- the primary vertices are forgotten, like they don’t exist anymore. This is on purpose.
So you have a mesh:
You select a sequence of vertices:
(Or you select separate vertices and the shortest path between them is selected for you automatically at startup, giving the same result as above).
A curve is created and fit to that selection, like this:
Right now, snapping works on primary vertices only. Since they don’t exist anymore, finding new ones would be difficult because we’d have to do it based on proximity to the curve rather than you selecting exactly what you want, it wouldn’t have clean results (especially in high-poly meshes, lots of vertices would have similar proximities, instead of a clean sequence).
So, to be able to unbind and move the curve around and then snap other vertices to it, I think the workflow needed for that would be something like this:
Start the tool as usual, a curve gets generated and fit to selection.
You use the “Extract Curve” operation to get a copy of it.
Cancel the tool.
Modify the curve copy as you like, move it around etc.
Enter the mesh edit mode, select some new vertices.
With the mesh selected and the curve copy selected, start the tool. This would bind the selected vertices to this preexisting curve instead of creating a new curve (this would be a new feature, a new initialization way).
At least that’s what I can think of.
Edit: how are you usually using the snapping? Maybe there’s some other way to approach this.
@RNavega: Super addon, but i have noticed one thing, when it’s got an error you have to restart addon in preferences and it adds itself into menu again. It would be nice to have a way for avoid this. Many thanks!
Hi @TitusLVR, I’ll add a cleanup step when reticking the add-on checkbox.
But I’m curious about the error you mentioned? It’s supposed to be error-free.
I think it is outliner/viewlayer/collection things, so when you have several collections and some of them are hidden but still count as active in outliner but mesh is in “visible” collection and when i start BMS it creates curve inside hidden collection not inside objects collection and it’s give an error.
PS: IMO you have to create curve inside collection where is an active object.
Many thanks! Cool Addon!