Printf not working in OptiX kernel

[shocker.0x15]

Hello,

I’ve noticed that printf seems not to work for my environment.
I can reproduce the issue with optixHello sample in 7.6.0 SDK.
I just added printf("%u, %u\n", launch_index.x, launch_index.y); to the draw_solid_color.cu.

It seems to still work with ordinary CUDA kernels.
Is there any change to enable kernel printf for OptiX kernel?

My environment:
Windows 11 Pro 22H2 (22621.1413)
Core i9-9900K, 32GB
RTX 4080, 16GB
Driver: 531.29

[shocker.0x15]

Oh, sorry, this issue has been already reported:

Debugging is broken after updating to Cuda 12.1

Yeah the support for showing locals and structs in the debugger hasn’t yet always worked reliably, especially inside a function containing an optixTrace() call, though I think it’s improving little by little. I believe it usually does work in functions without a trace call. So this might not be super helpful or convenient, but one thing you can try is temporarily commenting the trace call, that usually seems to increase the number of things visible in the debugger. – David.

I’ve confirmed that printf is resurrected by setting OPTIX_FORCE_DEPRECATED_LAUNCHER to 1 as a user environment variable.