
Mohamed Elwazir
29 days ago
Thank you for taking the time to provide feedback, and I'm sorry to hear the node wasn't a good fit for you. I've marked the node as an asset to make it asset browser friendly.
Regarding the glitches you describe, they are a side effect of the boolean process where the original edges are removed before merging with the beveled edges. They are quite infrequent, however, as long as you avoid overlap (I couldn't implement "clap overlap" like the bevel modifier) and respond to minor adjustment of the bevel parameters.
The node is, of course, more resource intensive than the native bevel modifier and will be understandably slow when dealing with higher-poly geometry. I have added a caveat about this in the product description. It's nevertheless still very usable I assure you, and I have used it in several projects myself. I hope you'll give it another chance.