Sapling Add-On full of errors. #42138
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#42138
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system and graphics card
Windows 8; NVidia GeForce GTX 760
Blender Version
Broken: 2.72
Worked: 2.71
Short description of error
The Sapling Add-On seems partially broken. Changing the preset to the tree type ca_black_oak causes an error:
These statements, though copied from the Blender log panel, appear in reverse order here.
ZeroDivisionError: float division by zero
location: :-1
********************************Although it does not seem to apply any changes, it does cause other errors that do not otherwise occur within the Sapling settings: cannot turn on bevel, cannot make changes to curvature, etc. If, however, I go back to the presets and change it to one of the other settings, like black_tupelo, the errors stop and I can make changes, as you normally would.Exact steps for others to reproduce the error
Open Blender.
Turn on the Sapling Add-On.
Add a Tree curve.
Change the preset to ca_black_oak *error occurs here
Try to make other changes to the tree *error occurs here
Change the preset back to black_tupelo
Try to make other changes to the tree
Changed status to: 'Open'
Added subscriber: @MattLindley
#42010 was marked as duplicate of this issue
blender/blender#42250 was marked as duplicate of this issue
Added subscriber: @BrendonMurphy
hi, after some testing, the issue is when the Limit Import button is checked & only with ca_black oak file.
However, the "ZeroDivisionError: float division by zero" error seems endemic throughout the addons settings.
Prune throws same error as do many other changes.
This addon has no maintainer, https://developer.blender.org/p/trumanblending/ has not been active for some time.
I would add a warning "Buggy" for the immediate future & actively seek out a maintainer to fix current issues.
Added subscribers: @kintoun1, @truman
Added subscriber: @LeeA.Wentzel
Added subscriber: @lichtwerk
Added subscriber: @AditiaA.Pratama
Added subscriber: @NikoLeopold
this should fix the zero by division errors and also make the shape affect first level branches: D844
its just 3 lines of code so you can change it yourself in the addon if you need a quick fix.
looking for review. how does this work for addons?
Assigned to lichtwerk (Philipp Oeser).
he has also written a patch, I would expect fixes to be finalized this week.
ok. i didnt know since it was not claimed yet (and author was said to have no time for maintenance)
great to hear that its being done :)
Thanx for this Nikolaus,
I hope I'll find the time later today or tomorrow to have a final look.
I was more looking into https://developer.blender.org/T42207 which is more about pruning&armatures but hopefully we can solve this all in one go :)
thanks Philipp, i just did a really quick hotfix, there might be more places vulnerable to division by zero errors and other issues. i didnt have more time to test on the weekend unfortunately, just wanted to get it to work quickly :)
thanks for your effort!
Hi again!
Just wanted to say that I think the patch looks good (but I wont be the person to make a final decission here).
I will leave a note (and a WIP patch) about the other problem ('armatures&pruning' aka #42207) in that bugreport.
I am also on another job for at least a week, so I wont be available -- and thus put this up for grabs for anyone to jump in, sorry about that.
If this hasnt been solved, I will pick it up again when the other job is done [still think this addon deserves to be in addons and should be kept alive :)]
i would happily pick it up – you mean the other one, #42207 right?
also i would just extend the current patch of this little problem here to test for more possible vulnerabilities to division by zero and change such to prevent that.
also i wanted to ask who i could ask for code review in the end, since the author is not available..
EDIT: unfortunately i might not be able to look into this until next weekend due to university duties...
This issue was referenced by
51b6f00666
Changed status from 'Open' to: 'Resolved'
Closed by commit
51b6f00666
.