Hi NVIDIA team,
I’m encountering a strange OpenGL rendering issue that only happens on NVIDIA professional GPUs (Quadro / RTX A series). The issue does not occur on GeForce cards, and interestingly, it disappears after running Nsight Graphics just once.
Environment:
- GPU: Quadro RTX 5000 / A4000 (or specify your card)
- OpenGL version: 3.3
- Application: Video quality enhancement tool (super resolution, frame interpolation, color enhancement, SDR/HDR conversion)
- Architecture: D3D9 for video decoding + OpenGL for preview rendering
Issue description:
- The preview window shows corruption (black screen / wrong colors / artifacts) only on Pro cards
- Same application works perfectly on GeForce cards with the same driver version
- After installing and running Nsight Graphics once, the issue is completely gone — even when launching the application normally (not through Nsight)
- The same thing happened with RenderDoc: installing it also “fixed” the problem
What I observed in Nsight:
When I ran the application through Nsight Graphics, I saw this message in the output window:
“The attached application is creating a D3D9 device, but Nsight only supports…”
This indicates my application uses both D3D9 and OpenGL, which might be related to the issue.
My questions:
- What exactly does Nsight Graphics (or RenderDoc) change in the driver environment when it attaches? Does it trigger a different driver code path or reset some internal state?
- Is there a programmatic way to apply the same “fix” from within my application code? For example, can I force the driver into the same “compatibility mode” that Nsight enables?
- Is this a known behavioral difference between GeForce and Pro drivers when handling mixed D3D9/OpenGL workloads?
Screenshot attached:
Any insights or workarounds would be greatly appreciated. Thank you for your time!
Best regards,
Sylvan