[Feature]: Leaves and End Branch Radius

[pazderj]

Description

Very excited you guys are working on this new version for us... a couple things I've always wanted from mTree

1. Ability to control the end radius size for branches/branchlets... currently they taper into 0, or at least so small that the....
2. .... leaves don't extend to the ends of branches/branchlets.

This creates trees with "abandoned" or "leaf-less" twigs extending out of the branches and no way to control them. It just does not look natural. I wonder if allowing the ends of branches to have a radius control like the trunk node does would at least give some surface for the geometry node for leaves to put instances on.

If I had a "third" feature request, it would be to be able to give each branch node a separate material, or at least a material index.

Thanks so much again for taking on this project... I see a lot of potential. Keep up the great work!

Component

Tree generation (C++ core)

Use Case

1. Ability to control the end radius size for branches/branchlets... currently they taper into 0, or at least so small that the....
2. .... leaves don't extend to the ends of branches/branchlets.
3. Branch material separate from parent node

Proposed Solution

1. Parameter in Branch node for End Radius
2. Parameter in the leaves geo node for Extend to Tips
3. Material selector for Branch node or at least Material Index parameter

Alternatives Considered

N/A

References

Sapling Tree Gen has the ability to extend leaves to the ends/tips by making the number of leaves an odd number. It also has end radius settings, although it's a bit obscured and not too obvious

[GoodPie]

Hey @pazderj, just me working on it and apologies, I didn't receive a notification for this one.

That is a good point on the branch tapering. I've been facing this issue myself and it's something I've been wanting to address. I'll keep you updated on that one.

Just a question on the material per branch node, more out of curiosity, what would this help achieve? Would it be for a different trunk material vs a different branch material or something a bit more complicated? Happy to consider it though.

[pazderj]

Hi - great to hear from you! Thanks again for working on this new version. I’ve been having fun with it. The ability to control tapering will be very helpful; another option for that request would be to be able to close the ends with a face or close all trunks/branches that are currently non-manifold, like the fill caps property for curves. In regards to each branch node having a property for its own material or at least material index: this will allow the branches and twigs to have different materials or shaders from the trunk or from their parent while retaining the amazing UV mapping that mTree already has. This will also be useful when using a branch node to simulate stems of leaves, which will have a material that more closely matches the leaf color as opposed to the color of parent branches/twigs. A useful example would be a Birch tree. The smaller branches are very dark while the trunk has that classic spotted white bark. Image attached. I look forward to all that’s ahead and thanks again. 🙌

On Fri, Feb 27, 2026 at 2:02 AM Brandyn Britton ***@***.***> wrote: *GoodPie* left a comment (GoodPie/modular_tree#18) <#18 (comment)

 mment-3971199656>

…

Hey @pazderj <https://github.com/pazderj>, just me working on it and apologies, I didn't receive a notification for this one. That is a good point on the branch tapering. I've been facing this issue myself and it's something I've been wanting to address. I'll keep you updated on that one. Just a question on the material per branch node, more out of curiosity, what would this help achieve? — Reply to this email directly, view it on GitHub <#18 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIVEIT5VRR2IPPJAZ66PHOD4N7TY5AVCNFSM6AAAAACV33VPX6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSNZRGE4TSNRVGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>