-
Notifications
You must be signed in to change notification settings - Fork 207
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
Segfault/Crash when rendering VDBs in Cycles Linux #5824
Comments
I suspect the VDB code hasn't changed much, #5373 was the code to get it to work, but needs rebasing and the unit test to function. |
I spent a tiny bit of time looking at this on Friday. With a rebased #5373 the crash is gone, but interactive shader updates don't seem to take effect without a renderer restart. There's a lot of stuff bundled up into that one commit in that PR, so I'll need to find some time to pick it apart and rebuild it... |
Just confirming whats been said on discord. The GafferCycles build from Alex previously worked OK in regards to rendering VDBs and doing shader (parameters) updates in an interactive session. |
i have same issue on windows 11, cycles crash when try to render vdb. i try to load vdb from embergen and cycles crash in cpu or gpu . both have issue. |
I have the same issue on Windows 10. But it seems to crash only if the vdb is being shaded. |
Version: Gaffer 1.4.1.0-linux-gcc11
Third-party tools: Gaffer Deadline
Third-party modules: None
Description
Simple setup, trying to render a small vdb (or any other I have on disk) results in a crash.
Interactive mode seg faults and crashes while doing a local dispatch render outputs:
Tried various shaders, and connecting the density parameters. All results in the same crash.
Steps to reproduce
Download the script to see.
https://drive.google.com/drive/folders/1e1hdsMcCDkkX-yGXY9jKU-UP3THPU7fC?usp=drive_link
Debug log
Click to Expand
The text was updated successfully, but these errors were encountered: