Closed Draise14 closed 2 weeks ago
As usual, it is not one new option, but the whole thing is completely outdated. And holy molly, how much options can one put into a single exporter ....
Yeah refactoring these. Will commit after the merge.
Err, i have assigned to this task already, and am nearly through :)
Merge conflict. I too have already done it.
Okay, i will trash my work then.
Draise, for the future, please respect assignments. When you want to fix the task, then assign. When somebody is already assigned, let him do the task. That's the whole idea behind the tracker.
I have now worked three hours for the birds. That's not how it should be. And that's why we have the system of assigning to a task. Assignee is the one who fixes it then. When you want take over, then please first ask.
I did.
I see. Then you would have to close this one, since this is a double then.
I will close it as double now if you don't mind
Related task:
603
Details
SHA-1: 0f0a8df8a922cdb0796c0b3fdbdc5c669efb3059 * glTF exporter: Option to export VC even if not used in node tree glTF specification says that VC must be used as a base color multiplier, so you should add it to your node tree to see it. But seems common usage of VC is to use it for custom data. Custom properties/attribute is the best place for these data, but in order not to break production workflow/pipeline, we add an option to export active VC