Debugging shaders with visual studio graphics diagnostics

#1

Greetings Paradox Team,

An initial fear I had with the mixin shader approach is that it would complicate debugging. So, as a test, I tried out custom effect sample with the pix replacement in VS2013 [which I view as a fairly critical tool]. Unfortunately I did not have a lot of success: VS gets confused stepping over source files (i.e. is over the wrong lines or moves backward when not expected) and I had some initial issues with it even finding the built-in shaders. Is this a bug (maybe as simple as incorrect #line macros being inserted) or am I missing something?

Thanks!
Jason

#2

I can give this a shot how do I use the shader debugger in vs?

#3

Go to Debug / Graphics / Start Diagnostics to get started.

See also:
https://msdn.microsoft.com/en-us/library/hh315751(v=vs.110).aspx

It’s a great nice tool for quick troubleshooting / performance tuning.

BTW, I’m moving this to github issue as I guess the forum is not really the appropriate place for this (and for sure there is an issue here).