Jump to content

  • Log In with Google      Sign In   
  • Create Account


#ActualBrother Bob

Posted 22 July 2013 - 12:14 PM

I ran all the shaders through AMD's GPU shaderAnalyzer and shaders 2,3, and 5 all have reported errors.  Most notable, 2 is using variables that were not declared.

 

Also, there is usually a huge problem with shader tech that is very new.  A lot of it is not tested against multiple GPU's and it can take a while for the GPU manufacturers to play catch-up with one another. Often you will run into compatibility issues if you have a different brand than what the code was tested on.  

 

Here's another site that you can cross-reference against.  

 

http://prideout.net/blog/?p=48

 

ShaderAnalyzer only has a problem with the tess eval shader in this example. 


#2marcClintDion

Posted 22 July 2013 - 03:36 AM

There is far too much arrogance and out right abuse by site moderators, they are teaching other people to behave this way.  The posts I've made will all be shorty removed and replaced with this notice.  Game development is not the only thing being taught here, bad behavior is being taught as well.


#1marcClintDion

Posted 27 June 2013 - 12:20 PM

I ran all the shaders through AMD's GPU shaderAnalyzer and shaders 2,3, and 5 all have reported errors.  Most notable, 2 is using variables that were not declared.

 

Also, there is usually a huge problem with shader tech that is very new.  A lot of it is not tested against multiple GPU's and it can take a while for the GPU manufacturers to play catch-up with one another. Often you will run into compatibility issues if you have a different brand than what the code was tested on.  

 

Here's another site that you can cross-reference against.  

 

http://prideout.net/blog/?p=48

 

ShaderAnalyzer only has a problem with the tess eval shader in this example. 


PARTNERS