rdb
October 26, 2021, 10:02am
22
Surely, then, it would make sense to put in a feature request for blend2bam to add an export operator that respects selected objects, if you are lacking this feature.
Maybe–but it seems to me that specifying individual elements via command-line is likely to be awkward–even cumbersome with large scenes.
I’d much rather there were a GUI interface, ideally integrated with Blender, and if so then using Blender’s selection mechanism to specify what is to be exported.
rdb
October 26, 2021, 10:22am
24
That is what I am suggesting: requesting that blend2bam add an export operator to Blender’s export menu.
Such a request belongs on the blend2bam GitHub issue tracker.
Ah, I see–my apologies then!
In that case, I may well make such a request there.
[edit]
opened 11:36AM - 26 Oct 21 UTC
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.
1 Like
