Sapling Tree: python traceback when changing batch distribution #94156
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#94156
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: macOS-12.0.1-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.7.29
Blender Version
Broken: version: 3.1.0 Alpha, branch: master, commit date: 2021-12-14 00:16, hash:
blender/blender@c1f5d8d023Worked: (newest version of Blender that worked as expected)
Short description of error
Sapling Tree 0.3.4
Index out of bound when changing batch distribution.
Exact steps for others to reproduce the error
Edit > Preferences then click Add-ons word "Sapling"
0.3.4 -VS -0.4.0
0.3.4 have some bug on Blender 3.1.0
Check link: https://github.com/abpy/improved-sapling-tree-generator
Youtube cause my iMac late start. I show you screenshot
step 1.
then
step 2. youtube
See youtube: https://youtu.be/i9VIyKUrCeM
Added subscriber: @Kent-Davis
Added subscriber: @(Deleted)
maybe the internal blender addon can be replaced by version 0.4.0 ?
https://github.com/abpy/improved-sapling-tree-generator
@rendermonkey
Yes correct.
I hope the devs will update it. I use it a lot too.
Addon Information
Name: Sapling Tree Gen (0, 3, 4)
Author: Andrew Hale (TrumanBlending), Aaron Buchler, CansecoGPC
I have a question for the developers about the Mac OS version using Vulkan. Will Vulkan be the default on Windows and Linux too in the next version or will Vulkan ONLY be used for Mac OS version?
Not only Mac version
There is the same as Mac, Windows, Linux
You said, "Will Vulkan be the default on Windows and Linux too." Yes correct.
I am not good explain my bad english. I am full deaf and low vision.
Sapling Treeto Sapling Tree: python traceback when changing batch distributionChanged status from 'Needs Triage' to: 'Confirmed'
There still old version bug. I am still wait for you to update about tree version.
I am still wait for you to fix new version and update Sapling Tree.
Added subscriber: @OmarEmaraDev
@OmarEmaraDev
There still bug. wait too long to update Spling Tree.
Kent Davis referenced this issue from blender/blender2024-02-14 13:33:24 +01:00
@PratikPB2123
System Information
Operating system: macOS-13.6.4-x86_64-i386-64bit 64 Bits
Graphics card: Metal API AMD Radeon Pro 575 1.2
Blender Version
Broken: version: 4.1.0 Beta, branch: blender-v4.1-release, commit date: 2024-02-13 23:35, hash: c6e229d3e470
Worked: (newest version of Blender that worked as expected)
Short description of error
Sapling still bug few years until now.
Exact steps for others to reproduce the error
Sapling still bug few years previous ticket. blender/blender-addons#94156
Why you never listen what I ask you few times.
Version 4.0 is much better and no bug. But you put 0.3.5 still BUG!
cc @CansecoGPC