Open BachiLi opened 3 years ago
Hi @BachiLi,
Assuming this is in Debug mode, does it work in Release mode? (At least this would give you a workaround).
The error is surprising since it seems we do set OPTIX_COMPILE_OPTIMIZATION_LEVEL_0
:
Could you check this is indeed set as we expect?
This is apparently a known ABI issue with the latest version of OptiX. Some constants defined in the header file changed their meaning (uh oh). Try setting the CMake option MTS_USE_OPTIX_HEADERS
, which uses the official optix headers, which would have the right constant for that specific version.
Makes a lot of sense. We will try this. Thanks!
I had this issue when I upgraded my Nvidia drivers to one of the latest drivers a few weeks ago. I had to downgrade to 445.75 (old driver I installed in April/May this year) and mitsuba2 worked like a charm. In my case, it made sense as I still have Optix 6.5 installed. Hope this helps.
Thanks all. I am without power here in the Bay Area. @BachiLi and I will try these suggestions once power is restored and report back.
Thanks all for the help! It's working for us. We have to fix two more problems:
1) Nick's GPU only has compute capability of 5.2, so we have to change https://github.com/mitsuba-renderer/mitsuba2/blob/master/resources/ptx/optix_rt.ptx#L10 to sm_52
.
2) As mentioned in https://github.com/mitsuba-renderer/mitsuba2/issues/254, with Optix 7.1 it crashes in Debug mode with nan/inf checks.
I will let y'all decide whether to close this issue or not. Thanks again!
Summary
I'm helping someone (@antipa) building/installing Mitsuba 2. When we run in the
gpu_autodiff_rgb
variant and load a scene file, we getCOMPILE ERROR: Debug level OPTIX_COMPILE_DEBUG_LEVEL_FULL requires optimization level OPTIX_COMPILE_OPTIMIZATION_LEVEL_0.
It fails atrt_check(): OptiX API error = 7001 (Invalid value) in ...\mitsuba2\src\librender\scene_optix.inl:109.
System configuration
gpu_autodiff_rgb
Description
See summary.
Steps to reproduce
Run the following python script
Output