.. can do some code unification between USD export and Hydra but I propose to do this in separate PR after this PR will be merged. It requires discussion with USD export team, agree design, etc.…
The point was to use the blender USD export and render that file (exported to memory) This does that
Yeah that is weird right because the "HIP - CPU" render is just using the CPU kernels, not using HIP at all really. Not sure why rendering that way and then redoing with HIP would work. …
Yes, this seems like it can be handled in the add-on. And then enabling viewport rendering or pressing F12 to render would likely be faster too. In Cycles this doesn't take several seconds…
Same as above.
I prefer the original name "Step size" is too generic.
We are looking to enable it for Blender 4.0 in Linux so users don't have to install the HIP RT SDK themselves.
We need explanations of how these methods should be used / overridden
Why are these node defs being included?
I guess my main comment is on the mechanism of generating the .py files for materialx nodes. Why are they generated on the user side and not something done once.