RuntimeError When Importing Bones with Spaces in Their Names
Summary
When importing a USD skeleton, if any bone name contains a space character (e.g. "Upper Arm"), the importer raises a RuntimeError with an unclear or misleading message. This makes it difficult to diagnose the root cause and breaks the import process unexpectedly.
Problem
Bone names in USD skeletons are expected to be valid tokens. A name containing a space violates this expectation, but instead of a clear validation error, the system throws a generic or cryptic RuntimeError, which:
- Obscures the actual issue (invalid token format)
- Confuses users and developers trying to debug the import
- May cause downstream tools to crash or behave unpredictably
Example of Invalid Input
uniform token[] joints = ["Upper Arm", "LowerArm"]
RuntimeError When Importing Bones with Spaces in Their Names
Summary
When importing a USD skeleton, if any bone name contains a space character (e.g.
"Upper Arm"), the importer raises a RuntimeError with an unclear or misleading message. This makes it difficult to diagnose the root cause and breaks the import process unexpectedly.Problem
Bone names in USD skeletons are expected to be valid tokens. A name containing a space violates this expectation, but instead of a clear validation error, the system throws a generic or cryptic
RuntimeError, which:Example of Invalid Input