1

Can someone give me a run-down on the utility or otherwise of using NVIDIA's parallel nsight (in Visual Studio) for debugging OpenGL 3.3/4.2 + shaders? Is this possible? Is it desirable?

If it is possible, what configuration makes it possible? Do I need two cards in one machine, two machines?

Do ATI have a similar feature?

I've found debugging my OpenGL shaders to be hell, and I've tried other OpenGL debuggers, that seem not to work correctly or at all.

Improve this question
3
  • 1
    The Nsight Visual Studio Edition 3.0 RC1 (available early 2013) will support OpenGL shader debugging. The current 2.2 version only supports D3D10/11 HLSL shader debugging. Commented Dec 14, 2012 at 16:22
  • Ah, OK. Thanks Greg. Can you just add that as an answer and I'll mark it. Commented Dec 14, 2012 at 16:29
  • I'll upvote it personally, because it's great news! :) Commented Dec 14, 2012 at 18:10

2 Answers 2

Reset to default
3

Nsight Visual Studio Edition 3.0 (available early 2013) will support OpenGL shader debugging. OpenGL support was announced at SIGGRAPH 2012. The initial version will support OpenGL 4.2 core. Follow on versions will add additional extensions.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

1

If NSight is really coming out for OpenGL soon, it maybe not important, but...

I use gDEBugger. It was, and still is a great tool for OpenGL debugging; requires one card only, works on ATI and NVidia cards, and it's free.

However, since AMD bought it, they've managed to make it totally useless, so GRemedy version is, sadly, last usable one.

Improve this answer

1 Comment

Yea, I tried gDEBugger and it was...well... what can I say? It needs work :).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.