Sapling addon: Save preset error #46351
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#46351
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
Windows 8.1 and 10, each on two different computers.
Blender Version
2.75a c27589e
Short description of error
It gives the following error when ever I click the "Export Preset" button.
Exact steps for others to reproduce the error
Changed status to: 'Open'
Added subscriber: @PeterGutfeldt
Added subscriber: @Harvester
Hello, here with the zipped versions of both 2.75a and 2.76RC3 the add-on Sapling Generator works as expected when saving and loading tree presets in an old .blend project (made with v2.69) as well as in a brand new file. My current environment is i7-720Q, Windows 7 Pro 64bit, 8 GB RAM, Nvidia GTS-360M 1GB VRAM. Does the user have the rights to read/write on the \presets folder inside the add-on ...\2.75\scripts\addons\add_curve_sapling?
It seems that that is the problem, the folder is read-only, I can't believe I never thought of that. Sorry for the erroneous bug report.
The problem is that Windows won't let me make the folder not read-only without making the entire program files folder read-only (which I am not ready to do quite yet). I will see if I can dust off my Python and modify the script to save in a different location.
Peter, that's the reason why I don't install Blender but instead I use the zipped version so that I can set the rights I wish on the unzipped folders.
Therefore, I don't think this can be really considered a software "bug".
Added subscriber: @BrendonMurphy
Changed status from 'Open' to: 'Resolved'
closing as resolved