- User Since
- Mon, Aug 12, 1:02 PM (1 w, 2 h)
Fri, Aug 16
Yeah I totally get that, no need to apologize.
Now that I know it's a necessary sacrifice I'm happy to accept it :)
Aaaah okay. I wasn't aware that you couldn't have AutoGrab on and cancel without it AutoMerging.
I think that logically you could create a state in which cancelling AutoGrab would not AutoMerge...and even if it did, you could rip the vertex.
@Paul Kotelevets (1D_Inc) Where would Auto-Merge cause an issue on the creation of those examples? Saying that it would cause an issue on "complex models" without explaining why doesn't help.
I came across this bug while working on a complex model and found it inconvenient.
Thank you. This is exactly what I've been trying to get across. Inconsistent behavior from Auto-Merge on "Quad from Vertex" operation.
I think Paul was trying to explain that it's by design but couldn't come up with a use case in which Auto-Merge being blocked by the addon would actually result in a desired outcome.
Thu, Aug 15
At this point I give up. This is a hopeless exercise.
I don't mean to insult Paul but your grammar is a mess, man. I can't decipher the point you're trying to make.
Paul, F2 at the very least treats merges differently at the quad from vertex level. The expected response from a user is that vertex-based fills will merge just like edge-based fills.
Being accustomed to that is not learning the software. It is becoming accustomed to an inconsistent behavior, which you still haven't managed to explain the professional benefits of. I've explained why it is not of benefit, and you agreed that it did not increase or decrease working time. Therefore, the benefit is that changing it would make it more intuitive, and would not hurt existing users in a meaningful way.
So now that we've established it does nothing to speed-up or slow-down work, we may now focus on why it's a problem:
AutoMerge inconsistent behavior.
In every other case, AutoMerge will merge two vertices on top of each other. This is what the tool is expected to do.
When a tool does something that is not expected, it is a bug.
I'm not saying that's what F2 is. I use Blender for professional work as well, you don't need to go shooting your highly polished work at me and assume I'm simply using it to "Fill grids".
Here's a use case of filling in faces with a corner selection, which would be possible with a couple of F taps if this wasn't an issue.
Considering how F2 treats edges and allow you to spam F to fill multiple segments, the same is expected here.
I can confirm this behavior was built into F2 from 2.79b, my bad.
The issue is AutoMerge not recognizing the vertices are within the merging threshold. If I wanted them to always merge, I don't have that option. I need to drag it and snap to the vertex it lays on top of.
This apparently still existed in 2.79b too, but seems like a bug behavior to me, since AutoMerge isn't acting in the way one would expect.