You can only load one usd file into the assets at a time. All previously added assets will vanish and cause issues when you open the file again.
Is this referring to replacing references on assets/instances by the Layout LOP?
You can only load one usd file into the assets at a time. All previously added assets will vanish and cause issues when you open the file again.
mtlx2karma.py
(json-representation/registration) and and mtlx2hda.py
(create VOP node for users), to be usable by Karma.
tamte
how does one implement a new node that works for all MtlX renderers?
I assume implementing codegen targets will not make it work for Karma since we've been told Karma is not using any of those languages
But if Nodegraph doesn't have many basic functions what are the options if we don't want to implement basic libraries (like random, matrix math, quaternions, ...) using only available very elemental math functions from scratch?
primvars:id
on the Procedural Prim curves. I think the problem is the int to float connection, which for some reason isn't just auto-converted in every case? Also generating simple random numbers for Karma/MaterialX in-shader is more awkward than it should be, we're working on it.tangentu
attribute on the geometry.st
or uv
- some USDZ files have decided to use st0
by default...). As long as that name is in the USD Primvar Reader, it should work; you may also want to double-check that the type matches your primvar (i.e. is it a vector2 or vector3).