First thoughts are a typo in a custom texture's shader, or a $value that isn't
used in csgo, probably the latter. I have/had some textures that would spam
the console with something like that because ... the $alphainbumpmapwhatever
shader was something different in Go.
On Monday, November 11, 2013 2:14 AM, Michael Mayea <mikema...@gmail.com> wrote:
I'm working on a custom map and suddenly this started being spammed in my
console "***** Trying to set a pixel shader that failed loading! *****"
I am not sure what it is in my map that is causing this. Anybody have any
ideas?
_______________________________________________
Csgo_sdk mailing list
Csgo_sdk@list.valvesoftware.com
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_sdk
_______________________________________________
Csgo_sdk mailing list
Csgo_sdk@list.valvesoftware.com
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_sdk
