-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cycles seg-faults with USD from blender #6267
Comments
The pertinent warnings are these:
We're pretty strict about not loading invalid primitive variables from USD, though here it results in the objects being created without a For now, if those locations are pruned in Gaffer then the Cycles render doesn't crash. |
I'll see if we can find a process to sanitize the geometry before saving it out. It would however be nice if Gaffer could fail more gracefully when it does encounter invalid data like this. |
Indeed! Thanks for the report. I'd imagine our more graceful failing would be either "cause the render to error" or "omit the invalid geometry" so ensuring clean geo is exported out of Blender does sound like a worthwhile pursuit. |
Version: Gaffer 1.5.4.1-linux
Description
Loading a blender USD results in a seg fault. There seems to be some unsupported primvars from the USD that causes cycles in Gaffer to seg/fault. The opengl viewport works fine. Both viewport and render/interactive render crashes.
I`ve tried to remove the primvars using the DeletePrimitiveVariables node to no avail.
Steps to reproduce
Download geo, load it in gaffer, hit render / switch to cycles in the viewport and it instantly crashes.
USD: https://drive.google.com/file/d/1QUHcR17EAG6y8uStOpgJC1vYIbWBDd7X/view?usp=sharing
Debug log
Click to Expand
The text was updated successfully, but these errors were encountered: