I have one comment about a very minor point above. Otherwise, these changes look good to me.
I suspect this print statement was for debugging and should probably be removed.
Also personally I would never recommend doing this (just like I would never recommend adding spaces into file names and such ;) ).
Thank you, @mont29. I completely respect your opinion on…
@deadpin I will also be addressing the issue of the duplicated nodes on re-import in a separate patch.
Hmm, without full material graph translation between USD <--> Blender, it will not be possible to be correct in all situations here. Only the following nodes are supported, which isn't enough to…
I wonder if something more nuanced is needed here. Using the alpha channel for opacity generally makes sense, but I have also encountered materials that use a single-channel texture for…
Not sure about USD paths (and could not find the answer from a very quick search online), but in general paths can have spaces nowadays, so would rather avoid relying on spaces as separators?
…
Thanks for pointing this out, @Matt-McLin and @mont29. I've updated the code to use MEM_SAFE_FREE
.
My apologies for the delayed reply.
Is this describing a problem (like "even though it was set at import time, the modifier is no longer checking...") or is this a description of what the…
I've addressed this bug in pull request blender/blender#107022.
I created a pull request for this feature here: