-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
LuisaRenderPy won't compile with NVTT enabled #465
Comments
Could you try 12.4 or 12.1 instead of 12.6? You could also refer to the Dockerfile that we have |
@Kashu7100 Thanks for the reply. I tried with CUDA 12.4 and it didn't change anything. Only when I downgraded the CUDA drivers from 565 to 550 did it work. |
Good to hear that. My understanding is 12.4 - 550, 12.1 - 535 is the right combination. |
I should also mention that I inserted |
In order to render a scene with spherical light sources, I am using this code:
I compiled LuisaRenderPy following the official instructions, including the CUDA backend. I then got an error:
Research into this error (admittedly using GPT 4o a lot) strongly suggested this being due to a mismatch between CUDA driver and toolkit version and my GPU's compute capabilities. I am using CUDA toolkit 12.6, CUDA driver 565.57.01 and my GPU is NVIDIA GeForce GTX 1080 Ti which has compute capability 6.1. They should be compatible, afaic.
So my next hunch was that rendering a .obj file that uses a material - which mine does - needs, NVTT to be installed, so I downloaded NVTT tarball for LINUX x86_64 from NVidia's official website and moved all the binaries to
/usr/local/bin
and the shared object file to/usr/local
and the libs to/usr/local/lib
, and setNVTT_DIR=/usr/local
and tried to re-compile LuisaRenderPy withbut that fails with
My OS is Ubuntu 20.04. I have tried modifying LuisaRenderPy's C++ code even though I'm not particularly familiar with C++, but I'm sure there should be a way to compile LuisaRenderPy with NVTT without changing its code. The commit of LuisaRenderPy I have checked out is
eafb470e97cbc36368f610afa440bb03c4ee3703
.The text was updated successfully, but these errors were encountered: