Get compile errors of GLSL material?

   4604   5   0
User Avatar
Member
13 posts
Joined: Dec. 2012
Offline
Hi

I am not a shader writer, but a render wrangler. I got scene with a GLSL material and it does not seem to compile.
If I copy-paste the source of an other shader from Houdini 16.5.473\houdini\glsl\material\GL32\ into the .frag, .geom and .vert files, the shader compiles and I see the material in my viewport.
But with the original shader source, I just see a white sphere.

I have seen that the compiler commandline vcc has options for log output (-q -e logfile), which I tried to remove.
Then I tried to set an error logfile -e \\path\errorlog.txt, but I do not get any output.

Is there a way to get the errors of the shader compiler?
User Avatar
Staff
5158 posts
Joined: July 2005
Offline
If the shader isn't compiling, you'll see the geometry with red diagonal lines on it. It sounds like the shader isn't being applied.
User Avatar
Member
13 posts
Joined: Dec. 2012
Offline
But if I change the source of the shader files as described in the first post and re-open the scene without any change, I see the shader. I even tried adding a line “aslfdkfddsaddasd” to the shader source and I haven't seen any red lines.
Edited by schoenberger - Sept. 21, 2018 10:08:52
User Avatar
Member
1 posts
Joined: Oct. 2021
Offline
I solved it!!!. I just installed Nvidia studio drivers, 472.39
https://www.nvidia.com/en-us/drivers/results/183366/ [www.nvidia.com]

and problem solved, hope it works for you guys too.

I'm on Windows 10 ♥

Please Subscribe to my channel if this gives you the solution hehe ♥
https://www.youtube.com/c/TGameplay4k?sub_confirmation=1 [www.youtube.com]
User Avatar
Member
7 posts
Joined: March 2016
Offline
For those who have video cards that do not support the studio version of the drivers, I had to roll back to https://www.nvidia.com/en-us/drivers/results/180557/ [www.nvidia.com] this version in order to bypass the HLSL errors. Hope this helps in the meantime.
User Avatar
Member
3 posts
Joined: Sept. 2015
Offline
The latest "regular" Nvidia driver fixed it for me. (build 497.09)
I still had some weird behaviours here and there ... but it's working with my 3080Ti.
  • Quick Links