I am working on a demo renderer using Optix6.5 API. I see issues with RT_EXCEPTIONS since I upgraded my driver from 455.something (don’t remember exactly) to 460.89 on a GTX960.
On some of my geometry in run into RT_TRACE_DEPTH_EXCEEDED exceptions for yet unknown reasons. That was fine before on the old driver as in Debug mode I printed all exceptions and set my output buffer to the exception code. In Release however I opted to ignore all exceptions via
context->setExceptionEnabled(RT_EXCEPTION_ALL, false); as the visual output was still as expected.
Now with the new driver the trace call fails in Release mode with an error as soon as an exception is encountered (Debug is still fine: printing messages and setting the code to the output buffer).
The error message I get is:
Unknown error (Details: Function “_rtContextLaunch3D” caught exception: Encountered a CUDA error: cudaDriver().CuEventSynchronize( m_event ) returned (700): Illegal address, file: , line: 0)
terminate called after throwing an instance of ‘optix::Exception’
what(): Unknown error (Details: Function “bufferMap” caught exception: Encountered a CUDA error: cudaDriver().CuMemcpyDtoH( dstHost, srcDevice, byteCount ) returned (700): Illegal address, file: , line: 0)
I would like to keep ignoring exceptions in Release due to performance reasons. Maybe this is an issue only for this hardware? I might be able to check this in office against a RTX2060 card too. The RTX2060 and an MX150 also work fine using some older drivers both on Win10 and Linux (versions between 440.xy and 455.xy).
Any ideas are highly appreciated. In my opinion this is a bug but maybe it is expected (new) behavior?
EDIT: I played with some legacy drivers available from the download website and found that the last version that is fine for me on Win10 x64 is 452.06 WHQL driver - the next 456.38 WHQL give above issue. From 457.71 I start seeing another error in Release mode on different geometry setup. I did not save the output but it was related to alignment issues and the error number was 716 I think.
Probably there is some error on my side but it kind of bugs me that some code runs perfectly fine up to some driver version and suddenly is broken? I will try to check against some other hardware on Monday maybe…