Open ArsThaumaturgis opened 3 years ago
Sorry for taking so long to respond to this! I would be open to some more filtering options for blend2bam. However, I believe a Blender addon is out of scope for blend2bam, and I do not feel like maintaining a Blender addon at this time. That said, I encourage others to make a Blender addon that calls out to blend2bam. In other words, create a GUI wrapper (via Blender) around blend2bam.
Ah, that's fair, if a pity!
The option to filter the exported objects by Blender's selection (or in some other way, if that's not available without Blender running) would still be a useful addition, I feel.
Hey guys, I think I can try to make a wrapper for Blender that integrates this as an add-on. Actually, I wanted to try this on MacOS (it couldn't solve the blender path issue even though I already gave the path of my blender installation, it still can't detect my blender installation).
Anyway, I'm not giving any promises, I already work 6 days a week full-time (+ overworking hours :') ) as a computer engineer besides 3 days a week side-job, so I'll try to use some LLMs to create at least the bpy (blender) script for it first, after that I'll try to make it as an add-on with the help of some LLM Q-A sessions :D.
Note: this will be my first-ever attempt to create a blender addon, so wish me luck 😄
This request is for two connected features:
First, that blend2bam be given a Blender-integrated UI, invoked from Blender's "export" menu.
And second, that when exporting via this UI, the option be present to export only those objects that are selected in Blender.
The first, I feel, would go a long way to making the exporter user-friendly--and especially to new users.
If I'm not much mistaken, recognition tends to be easier than recollection, and thus I would expect that visual UI controls would tend to be easer to use than command-line arguments.
UI controls may also be more convenient, by virtue of clicks requiring less subjective effort than typing.
The second, I feel, would greatly enhance the utility and power of the exporter.
Right now, any workflow that includes elements that are not intended for export (e.g. template objects), or even just multiple individual objects in a single Blender-file, isn't feasible with blend2bam--all will be exported regardless, if I'm not much mistaken. Allowing the user to specify which objects are to be exported would enable these workflows, I daresay--and, well, Blender provides a means to that via its selection functionality.