Closed steckhan closed 1 year ago
Hi @steckhan . Two quick things to check:
1) When you installed the Laubwerk plant kits, did you choose the "Custom" installation method and ensure the "Python Extension" component is checked?
If that doesn't address the issue,
2) Which version of Laubwerk are you using?
Yes I did use everything as custom and the python folder is there. Using the Laubwerk Plants kit freebie.
Attached the settings
Best Nico
Am 24.10.2021 um 20:04 schrieb Darren Hart @.***>:
Hi @steckhan . Two quick things to check:
When you installed the Laubwerk plant kits, did you choose the "Custom" installation method and ensure the "Python Extension" component is checked? If that doesn't address the issue,
Which version of Laubwerk are you using? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
@steckhan the Laubwerk package also has a version (in addition to a kit name). Are you using 1.0.39?
If you just want to try and get things working, I recommend getting version 1.0.37 of the Laubwerk Plants kit freebie and using Blender > 2.81 and < 3.0. I'll need to work with Laubwerk and Blender to sort out some new issues between the projects.
Between 1.0.37 and 1.0.39 I just confirmed that Thicket now fails to load the Laubwerk module with the following traceback:
Traceback (most recent call last):
File "/Library/Application Support/Laubwerk/Python/laubwerk/init.py", line 39, in
Testing from #53 on Windows suggests this is limited to the Laubwerk libraries for MacOS.
Is still not working.
Using Thicket 4.0 / Laubwerk direct from you page (most recent I assume) And Blender 2.83 On macOS Big Sur 11.6
Am 24.10.2021 um 23:10 schrieb Darren Hart @.***>:
Testing from #53 https://github.com/Thicket-Blender/thicket/issues/53 on Windows suggests this is limited to the Laubwerk libraries for MacOS.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Thicket-Blender/thicket/issues/53#issuecomment-950395567, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEUC5B36TPAM3F2YI3VC6V3UIRY27ANCNFSM5GSOYTBQ.
@steckhan which Laubwerk version did you install the Python extensions from? The file name of the package you downloaded from Laubwerk should include it.
Which directory is shown in the Python library path (the red box), and what is the contents of that directory?
@steckhan the Laubwerk link from the Thicket README does not specify a version, so what you downloaded will be whatever was current from Laubwerk at the time. If that was 1.0.39, this appears to be a build error in the Laubwerk python extension for MacOS specific to the 1.0.39 release (the shared library is missing symbols). I have tested both 1.0.37 and 1.0.38 successfully. Unfortunately, those do not appear to be available for download from the Laubwerk site. I will follow up with them and ask if they can be made available, but they are typically quick to turnaround fixes and I expect we'll see this resolved shortly.
@steckhan I've heard back from Laubwerk who have made the 1.0.38 version for Mac available temporarily. If you would like to try it, please contact me via email at dvhart at gmail dot com. Thanks.
Dear Darren,
thanks for your efforts. I have a scientific-art question. Do you ever had the chance to synthesize a tree or other plants from genetic sources ? Or if you ever tried to build a synesthesia of plants from Laubwerk and sounds according to some heuristic conditions ?
Best Nico
Am 26.10.2021 um 17:56 schrieb Darren Hart @.***>:
@steckhan the Laubwerk link from the Thicket README does not specify a version, so what you downloaded will be whatever was current from Laubwerk at the time. If that was 1.0.39, this appears to be a build error in the Laubwerk python extension for MacOS specific to the 1.0.39 release (the shared library is missing symbols). I have tested both 1.0.37 and 1.0.38 successfully. Unfortunately, those do not appear to be available for download from the Laubwerk site. I will follow up with them and ask if they can be made available, but they are typically quick to turnaround fixes and I expect we'll see this resolved shortly.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.
Hi @steckhan , I have not attempted anything along those lines. There are some more dynamic plant builders out there, but I don't think quite what you're describing.
This issue has been resolved with updated releases from Laubwerk.
Describe the bug Somehow the path to the Python extension in Blenders Plugin Settings is not accepted.
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Desktop (please complete the following information):