Thank you for the report, we haven’t seen this issue before, so we will investigate. Which CUDA toolkit version are you using?
Also tell me about using NTC_WITH_DX12… is that desirable? I admit we didn’t plan on or expect people to build the embedded version of libntc for any other backend than OptiX. If you want to build libntc in general or for DirectX, I would highly recommend getting it directly from the source, and not using the version in the OptiX SDK. The official libntc repo is located here: GitHub - NVIDIA-RTX/RTXNTC-Library: Runtime library for the NVIDIA RTXNTC SDK
and NTC_WITH_DX12 is just a try since I got no texture but white.
only happens when I combine it with NTC_WITH_PREBUILT_SHADER
Also, I know it’s off topic, But why nvcc only generate .obj files even I already set up –optix-ir option in Visual Studio project properties at my own project
OK, NOW I KNOW WHY I GOT .OBJ, IDE PASSED -o ${projectpath}\x64\Debug\kernel.cu.obj TO NVCC
The issue you’d like to hear updates about is the missing texture when optixNeuralTexture is built from default settings? We haven’t been able to reproduce that problem yet.
You mentioned driver 590.26, is that correct? Where did this driver come from? The 590 driver is not yet publicly released, so if you have a preview driver, this might just be a bug in the preview driver you have. Have you tried using a 580 driver? It’s also possible a newer CUDA toolkit version could affect this. We have automated testing showing this sample working out of the box with CUDA 12.8 and a 580 branch driver.
Okay thanks. So my best guess is that this driver is causing the issue you’re seeing because it’s not well tested. So if you can’t fall back to an earlier driver, the next best thing is to wait for the official release of the 590 driver, and check whether that fixes the issue you’re seeing with the OptiX sample.
If there’s any question or chance whether you’ve toggled DX flags in the OptiX sample, you could try installing the OptiX sample from scratch again and build/run without changing anything, but if you’re certain that you didn’t change anything and it’s running incorrectly by default, then it’s most likely the driver.
Whatever the problem is, our automated tests are showing the sample running correctly out of the box on our 590 release candidate drivers, as well as the very latest code beyond the 590 driver. So if the 590 preview driver had an issue, it’s already been fixed along the way and we just need to wait for the fix to be released.