Toolkit ability to accept subfolders or separate manifest(s) for custom brushes
The toolkit seems to expect all brushes to be in the top level subfolder in assets/resources/brushes
When serializing it finds them, but based on the console reactions, doesn't like it a lot.
I can organize things like that, but it will make things like tracking and importing brush packages much harder
Especially since they get mixed in with the core brushes when done this way
It may also affect model exports and other areas like VR recording.
The ability to handle subfolders without getting confused would make organization a lot easier, as well as potential install/remove operations for brush packages.
This in turn would give greater modularity down the road if there's some sort of brush exchange that gets created.
Particularly noticing this right now, because I'm basically trying to create a master set of brushes from various installs I've made
At any rate, some sort of guidance on how these should be structured would be helpful, because I've got the time right now to do a deep organization and merge of several different sets.
Some guidance on what structure I can anticipate would save a huge amount of time. Ideally, I'd like to do this just once and have everything conformant going forward (and preferably backwards as well)
Some guidance on what structure I can anticipate would save a huge amount of time. Ideally, I'd like to do this just once and have everything conformant going forward (and preferably backwards as well)
1 Reply
ChatGPT tells me this is a regex error or that the folders have to be organized directly in the brushes level
Is this something that can be changed, or should be changed?
