No shader syntax highlighting

No shader syntax highlighting

• Jon Woodcock

  I'm not sure what SKU is, but I'm using VC++ Express if that's what you're asking.
  

• BenWillett

  Kloda wrote:

  Ok, thanks to both of you for the replies. If that's true about PIX it seems like a step backwards in user-friendliness, having to capture a full stream every time you want to debug.

  Not sure what you mean by "full stream" but our goal is to make the experience as productive as possible.  Once it is in, please try it and let us know how it works or doesn't work for you.  :)

   

  Thanks,

  
  
  

• ZapNight

  Yes, I installed the December update after VC++. I also have VS.net 2003 Professional installed, if that could have something to do with it. The highlighting works fine there as usual. Does the Express version support Directx extensions at all
  

• Doubt_in_sql

  Jack Hoxley wrote:

  Does the Express version support Directx extensions at all This would seem to be the key point... the readme doesn't specify anything about the SKUs/versions of Visual Studio 2005. Hopefully Paul or another member of the team will check back on this thread and confirm. Jack

   

  I'm looking into this and will let you guys know.

  
  
  

• jimmyjos

  bump...and another question: are there any plans to add support for the shader debugger in VS 2005 in the near future

  
  

• odrejesus

  Kloda wrote:

  If that's true about PIX it seems like a step backwards in user-friendliness, having to capture a full stream every time you want to debug.

  Well, I suppose each to their own - but I'm no fan of the VStudio integrated debuggers. Yes, they do the job - but using them can be so tedious it hurts

  A few times I've wanted to debug some lighting computations in a pixel shader - running in REF until the breakpoint was hit took a long time. Then it proceeded to break about 50,000 times per frame (yes, I know you can set the rect/point properties). I've not had to do any PS debugging lately, but I'd prefer to call-stream capture and deep pixel analysis. That way I could load up PIX, view the state of my render target and click on a specific pixel that I can SEE is wrong and see what set of input led to that particular output.

  I suppose the best way around it is just to write shaders that work perfectly the first time.

  Jack

  
  
  

• PM2k

  Kloda wrote:

  The readme file of the Dxsdk December update says: "HLSL syntax highlighting works properly in Visual Studio 2005 but the Direct3D 9 Shader Debugger is not currently supported. " Well, the syntax highlighting has never worked for me in VC++ 2005. I thought the Dxsdk December update would fix this ( I found another post here that said it would) but it didn't. Is there anything I can do to activate it

  Which SKU of Visual Studio 2005 are you using  

   

  
  
  

• puromtec

  Thanks for clearing things up Paul

  Kloda wrote:

  are there any plans to add support for the shader debugger in VS 2005 in the near future

  I seem to remember reading an official comment (forget from who, or when) that the shader debugging tools weren't likely to appear for VS 2005. Something to do with improving PIX to take over the responsibility via it's full stream capture tools. I could be wrong though!

  Jack

  
  
  

• wilsonm73

  SKU = Stock Keeping Unit (according to google!)
  
  Thus, "Visual C++ 2005 Express Edition" would be the correct answer.
  
  I'm personally using professional edition, and I have syntax highlighting for shaders. Might be worth posting the exact details of your system and your installation method (e.g. VStudio will only get shader syntax highlighting if the SDK is installed after it is)
  
  Jack
  
  
  

• TITRA FILM

  Ok, thanks to both of you for the replies.

  If that's true about PIX it seems like a step backwards in user-friendliness, having to capture a full stream every time you want to debug.

  
  

• Brett G

  Kloda wrote:

  bump...and another question: are there any plans to add support for the shader debugger in VS 2005 in the near future

   

  I'm looking into this today.  It does in fact appear that the DX Extensions are still disabled for the Express SKUs.  The readme note is incorrect.  To close this thread (and try to provide the state of things):

  As of the DirectX SDK December 2005 release:

  1.  The DirectX Extensions for Visual Studio work completely for VS.NET 2003.

  2.  The shader syntax highlighting works properly for VS 2005 SKUs that allow extensibility (i.e. Standard, Professional, etc...).  There is a "Start with Direct3D Debugging" menu item in VS 2005 but it does nothing.

  3.  The extensions are completely disabled in all Visual Studio Express SKUs.

  4.  Making the extensions work properly for Visual Studio 2005 is low priority right now.  If you have comments on this, mail directx@microsoft.com

  Thanks,

   

  
  
  

• Krishnap

  I installed the December update after VC++. I also have VS.net 2003 Professional installed, if that could have something to do with it.

  
  okay, I don't think 2003 could be a problem... I have Visual Studio 6, Visual Studio 2003 and Visual Studio 2005 installed on my system along with the DirectX 8.1 SDK and the latest DirectX 9 SDK
  
  They all seem to work fine together.
  
  

  Does the Express version support Directx extensions at all

  
  This would seem to be the key point... the readme doesn't specify anything about the SKUs/versions of Visual Studio 2005. Hopefully Paul or another member of the team will check back on this thread and confirm.
  
  Jack
  
  
  
• No shader syntax highlighting