Jump to content

View more

Image of the Day

The night is still, but the invasion brings chaos. #screenshotsaturday #hanako #indiegame #gameart #ue4 #samurai https://t.co/cgILXuokoS
IOTD | Top Screenshots

The latest, straight to your Inbox.

Subscribe to GameDev.net Direct to receive the latest updates and exclusive content.


Sign up now

Issue with Visual Studio 2012 Graphics Debuging

4: Adsense

Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.


  • You cannot reply to this topic
2 replies to this topic

#1 skobalczyk   Members   

105
Like
0Likes
Like

Posted 13 April 2013 - 11:55 AM

I've created a simple project to play with DirectX shaders. It's written in C# using SlimDX wrappers and runs as Windows Forms app. Pipeline is setup using DirectX 10 with HLSL shaders compiled from code. I was trying to test shader debugging and capture and all windows look fine. However when I run debug on vertex or pixel shaders it doesn't show the current variable and constant buffer values (I assume it should based on this walkthrough http://msdn.microsoft.com/en-us/library/vstudio/hh972447.aspx).

 Can anyone suggest what might be causing this?



#2 collie   Members   

213
Like
1Likes
Like

Posted 14 April 2013 - 09:59 AM

If your seeing a variable show as a NaN double check that it's really is being *used* within the shader.

If your seeing a variable show as 0.000000000 check that it's going to be accessed within your shader, i.e. it may be in an 'if' that won't be entered?

 

The compiler could be optimizing those variables out.  Assuming this is the issue you've described?



#3 skobalczyk   Members   

105
Like
0Likes
Like

Posted 14 April 2013 - 11:24 AM

'm not sure if this is the case because all variables are constants are zeroed. I would expect that values inputs used in calculations are shown. I compile the shader with Debug and SkipOptimizations flags. Please see the screenshot below:

 

VS_GFX_Debug_issue1.png?psid=1






Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.