Tool Presets - can't get brush to work outside of default "User Library"
The tool presets are super handy! I am trying to get a brush from a custom asset library to work with no success unfortunately. When saving the same .blend to the default "User Library", it works. Following the same scheme, but in another library, StoryTools fails to find the brush though.
Cannot load myBrushes.blend/Brush/myBrush, need to be an asset path, ex: "Saved/Brushes/CustomFill.asset.blend/Brush/CustomFill"
Blender 4.4.3 StoryTools 2.20.3
Thanks
works: Blender's default "User Library": Brush in Tool Presets: Saved/Brushes/myBrushes.blend/Brush/myBrush relative as stated in Blender prefs / File Paths / Asset Libaries / Path: /Users/user/Documents/Blender/Assets full file path: /Users/user/Documents/Blender/Assets/Saved/Brushes/myBrushes.blend
does NOT work: custom Library, here "myBrushPack": Brush in Tool Presets: myBrushes.blend/Brush/myBrush relative as stated in Blender prefs / File Paths / Asset Libaries / Path: /Users/user/Documents/Library/Blender/myBrushPack full file path: /Users/user/Documents/Library/Blender/myBrushPack/myBrushes.blend
Ah, actually, this is a known issue !
Whenever a brush name is not found in the native Library, I directly assume it's from the User Library.
Because there's no way to know where it came from based on loaded brushes...
I asked the Blender officials for a solution, but it seems it's going to stay wonky for some time... (like this bottom asset shelf I don't like).
What I can do, is add a separated field to enter the library path (because we need both name and library path to activate a brush). Thing is, I don't like the idea of adding yet another field to this already crowded and hard to understand operator... But seeing you blocked, I might resort to that... will let you know I make the update. Not sure yet
How blocking and frustrating this is for you on a 1 to 10 scale ? Kidding ^^, but really I'd like to know if it's a big issue for you.
No worries, I can just move my (selected) custom brush assets from my custom library to the default user library. Moving, in order to just having them once, to avoid doubles of course. And all other type of assets can stay in the custom library. 😉
In the meantime, that's the best thing to do. But I should support your use case