Ok, if that would be due to OpenGL interop, I would have expected that the createBufferFromGLBO() would have already failed. I hadn’t seen your error output before. There is one size related error which I know of which is that interop buffers must not be zero size on OpenGL side before calling createBufferFromGLBO().
In any case, if there is an OpenGL implementation from NVIDIA running on that system and it’s from the Quadro P6000, forcing the programs onto that device should just work.
If the Titan is not running in WDDM mode there cannot be any OpenGL-OptiX interop with that.
Most OptiX samples normally use OpenGL interop by default for the display of the output image.
They are rendering to a pixel buffer object and copy that into an OpenGL texture, all on the device.
That isn’t possible when rendering on a device in Tesla Compute Cluster (TCC) driver mode or in any OptiX multi-GPU context when the output buffer resides in pinned memory on the host.
Some examples offer a switch –nopbo to disable that OpenGL interop, map the output buffer, and copy the data through the host to the OpenGL texture before final display. That should always work.
Please check if the examples you changed to run only on the Titan V device offer that option (–help prints the command line option) and work when setting --nopobo. If yes, that’s your solution.
Before using a Titan V? (Trying to isolate if this is Volta specific.)