I am using Nsight Compute 2024.2 for profiling OptiX 7.1. Recently, after updating Nsight Compute due to a driver issue, the display for raygen__** in Nsight Compute changed to NVIDIA Internal(optixLaunch), and I can no longer view the source code. I have set module_compile_options.debugLevel = OPTIX_COMPILE_DEBUG_LEVEL_LINEINFO; and included --lineinfo in the OptiX build. Please tell me what I should check to resolve this issue.
Thanks.
Hi, @tommyecguitar
Can you please update to the latest R555 driver to see if your user kernel is visible ?
Please refer restrictions for Optix
https://docs.nvidia.com/nsight-compute/ReleaseNotes/topics/library-support-optix.html?highlight=optix#optix
Also suggest you to use non-interactive, as there are some known issues with interactive profile
Thank you, @veraj .
My driver version is already 555.99 on RTX 2070 super.
In non-interactice profile, raygen is not displayed. I can see only “NVIDIA internal(optixLaunch)”.
Hi, @tommyecguitar
We can see the raygen_** related info in our test. We are using optixPathtracer.exe from Optix 7.6 package.
@veraj
Thank you.
Can you tell me what the profile settings are like? In my environment, I only have Import Source set to Yes.
Also, could the CUDA version of the application be relevant? My application has been developed with CUDA 11.
We use the default setting of non interactive profile.
I’m not sure if CUDA will be relevant in this case, but as CUDA 11 is relative old, I would suggest you to update to latest CUDA and Optix.
After setting CBL1 to OPTIX_FORCE_DEPRECATED_LAUNCHER, the Source was displayed.
Is it safe?
You can use CBL1.
@veraj
Thank you.
I will use CBL1 for a while.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
