System Information
Operating system: Windows 11 Home Version 22H2 OS build 22621.674
Graphics card: NVIDIA GeForce RTX 3060
Blender Version
Broken: 3.3.1 LTS 3.3.0 LTS 3.2.2 LTS
Short description of error
Exact steps for others to reproduce the error
Select ‘willow’ under Load Preset in Sapling Tree_Gen addon.
**System Information**
Operating system: Windows 11 Home Version 22H2 OS build 22621.674
Graphics card: NVIDIA GeForce RTX 3060
**Blender Version**
Broken: 3.3.1 LTS 3.3.0 LTS 3.2.2 LTS
**Short description of error**
**Exact steps for others to reproduce the error**
Select ‘willow’ under Load Preset in Sapling Tree_Gen addon.
Перейти к контенту
System Information
Windows 10 Home (Swedish language)
GTX 1070
Blender Version
Broken: 2.78c
Worked: 2.77a (on windows 7)
Short description of error
UnicodeDecodeError: ‘utf-8’ codec can’t decode byte 0x85 in position 3: invalid start byte
Exact steps for others to reproduce the error
Start blender. Rename default cube to Låda (any name with lowercase åäö will do). User preferences->Addons-> Add Curve: Sapling Tree Gen.
Shift-A->Curve->Sapling Tree Gen.
blender_sapling_error.blend451 KBDownload
Event Timeline
Comment Actions
I was able to replicate this, but inconsistently. Can anyone confirm if this is a blender issue or something addons need to handle themselves. If it’s the addon then how do I fix it?, because I do not know what’s causing this.
Comment Actions
I have a workaround that uses base64 to pass the string through the addon. It lets you choose the objects but still doesn’t show the correct object name in the menu.
Comment Actions
hi testing this (following exact reproduce from op) I was able to get the error using the presets & also in ui.
adding
to the file header (line1) in __init__.py & utils.py
& I cannot reproduce the issue
will commit fix soon
Comment Actions
awesome, I didn’t know file encodings could cause things like this. Its a lot better than my ugly workaround. thanks.
$begingroup$
The problem occured unexpectedly and appears only in one particular .blend file. After shift-a then curve>sapling tree gen no new object is created. Info shows up, pointing three lines in py’s and that one object «Cube.013_Cube.000» is not visible (?) or simply missing.
I tried making a copy of that file, then deleting all objects and seeing if it helps, gives the same info.
I tried downloading different blender version and still in that one particular file add on seems to have problem, in any other .blend it works perfectly.
asked Mar 7, 2019 at 21:11
$endgroup$
$begingroup$
I have found many interesting things
objects supposedly not being invisible in RenderLayer were not visible in any view, moreover, in the outliner. I tried searching for them by trying to append anything, from another .blend blank file. I suprisingly found that a lot of mesh data was in the scene, but it wasn’t connected to any object, thus confusing the add on py’s. After cleaning not used, hidden mesh data, add on started working properly.
answered Mar 7, 2019 at 21:45
$endgroup$
This started not as a real and proper answer, but to demonstrate that at least on 2.76b, with Sapling 0.2.6, sapling addon worked as you would expect:
So, I suggested you to detail exact blender and sapling versions you are trying. It could also be a bug or a changed behavior…
Meanwhile, I found a 2.79rc2 lying on my disk, so tried also launching Blender-softwaregl (opengl sw emulation due to my crappy notebook), here the addon is named «Sapling Tree Gen», version 0.3.3, it behave like you said: the tree is always at grid origin, no matter where the 3d cursor is.
It seems that there was a big change from 0.2.6 to 0.3.2 labeled as a «major rewrite», I guess starting just before 2.78 release, see this diffusion page.
But, good news! Browsing the sources on that page, I found a single line that reverts the behavior of sapling 0.3.3 to how it was in 0.2.6
-
find the file
<blender install folder>/2.79/scripts/addons/add_curve_sapling/utils.py -
go to line 1604, it should be like
#treeOb.location=bpy.context.scene.cursor_location attractUp -
change it to
treeOb.location=bpy.context.scene.cursor_location #attractUp -
save the file
- (if it was open, close and) start Blender
- now sapling should behave as it did in 2.76
Note: I’ve later found a comment by the addon developer stating that he did
«Fix Armature, Tree location generation to 0,0,0 (this was causing fails with armature weights & probably pruning)»
So, use this with caution, and revert if necessary…
This started not as a real and proper answer, but to demonstrate that at least on 2.76b, with Sapling 0.2.6, sapling addon worked as you would expect:
So, I suggested you to detail exact blender and sapling versions you are trying. It could also be a bug or a changed behavior…
Meanwhile, I found a 2.79rc2 lying on my disk, so tried also launching Blender-softwaregl (opengl sw emulation due to my crappy notebook), here the addon is named «Sapling Tree Gen», version 0.3.3, it behave like you said: the tree is always at grid origin, no matter where the 3d cursor is.
It seems that there was a big change from 0.2.6 to 0.3.2 labeled as a «major rewrite», I guess starting just before 2.78 release, see this diffusion page.
But, good news! Browsing the sources on that page, I found a single line that reverts the behavior of sapling 0.3.3 to how it was in 0.2.6
-
find the file
<blender install folder>/2.79/scripts/addons/add_curve_sapling/utils.py -
go to line 1604, it should be like
#treeOb.location=bpy.context.scene.cursor_location attractUp -
change it to
treeOb.location=bpy.context.scene.cursor_location #attractUp -
save the file
- (if it was open, close and) start Blender
- now sapling should behave as it did in 2.76
Note: I’ve later found a comment by the addon developer stating that he did
«Fix Armature, Tree location generation to 0,0,0 (this was causing fails with armature weights & probably pruning)»
So, use this with caution, and revert if necessary…
- В этой теме 0 ответов, 1 участник, последнее обновление 11 месяцев, 2 недели назад сделано
victor59.
Просмотр 1 сообщения — с 1 по 1 (всего 1)
-
Автор
Сообщения
-
Добрый день! Моя версия Блендер 2.93.6 После активации адона Sapling Tree Gen, при попытке его применить создается ствол дерева но окно слева внизу не активно! При попытке что либо изменить в нем, программа закрывается. Помогите пожалуйста разобраться в проблеме. С уважением Виктор.
-
Автор
Сообщения
Просмотр 1 сообщения — с 1 по 1 (всего 1)
- Для ответа в этой теме необходимо авторизоваться.
Авторизация
Рубрики
- Анимация и риггинг
- Загрузки
- Материалы и текстуры
- Моделирование и скульптинг
- Новости и обзоры
- Основы Blender
- Рендеринг и освещение
- Симуляция и частицы
- Скриптинг на Python
- Создание игр в Blender
Bug 1879404
— Blender 2.90.0-3.fc33 crashes when using adding sapling tree or using voronoi texture
Summary:
Blender 2.90.0-3.fc33 crashes when using adding sapling tree or using voronoi…
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|
Go to blenderhelp
r/blenderhelp
r/blenderhelp
For help with Blender problems, also consider visiting [BA](https://blenderartists.org/c/support) or [BSE](https://blender.stackexchange.com/).
Members
Online
•
by
[deleted]
Sapling tree generator not working?
The sapling tree generator is adding a default tree and showing the edit panel but nothing is selectable there.. can anyone help? 
I’ve been working on making and animating a tree in Blender, using the sapling tree generator. I created the tree, added an armature and animation, and added leaves (they’re rectangles with an alpha map to create a leaf shape). I haven’t done anything else very advanced with the leaf materials (just a texture and color ramp). There’s also an emitter modifier for falling leaves.
When I view the animation in the viewport, all looks as expected, leaves are present, and the branches move.
However, when I go to render the animation, it’s missing the leaves and animation added with sapling tree gen.
I’ve checked and as as far as I can tell, all of the entries in scene collection are set to render, so it’s a little confusion as to why they wouldn’t be present in the render.
1 ответ
Ваша модель слишком большая для 3DS. Blender выдает сообщение об ошибке:
В формате 3DS есть ограничение, максимальное количество точек и полигонов — 65536: https://en.wikipedia.org/wiki/.3ds#Shortcomings
Вместо 3DS попробуйте другой, более современный формат, например, fbx или alembic.
ответ дан 1 дек 2017 в 10:30
CrantiszCrantisz
9,7102 золотых знака15 серебряных знаков49 бронзовых знаков
1
-
Спасибо вам, никогда бы не подумал что такое возможно. исходя из вашего ответа о лимите, применил модификатор упрощение, и всё экспортировало. спасибо вам огромное.
1 дек 2017 в 22:02