Forums Technical Discussion Problem compiling shaders

Problem compiling shaders

   8918   16   2
User Avatar
carstenw
Member
30 posts
Joined: Aug. 2010
Offline
 
Hi,

with current Houdini versions (starting with 15.5.553, I believe), I get the following error message when starting a render:

mantra: /shop/principledshader1/SurfaceVexCode:7171:20-30: Error 1066: Call to undefined function ‘getuvobject’.
/shop/principledshader1/SurfaceVexCode:7172:25-40: Error 1066: Call to undefined function ‘getuvhiresobject’.

mantra: Failed to resolve VEX code opdefShop/principledshader?SurfaceVexCode

It doesn't matter whether I use the mantra surface shader or a simple principledshader.

I'm using Windows 10 pro on a HP Zbook 15.

Any ideas anybody?

Regards,
Carsten

Attachments:
error_compiling_shader.hipnc (198.6 KB)

 Report
User Avatar
carstenw
Member
30 posts
Joined: Aug. 2010
Offline
 
… just checked production build 15.5.523: OK.

regards,
Carsten
 Report
User Avatar
carstenw
Member
30 posts
Joined: Aug. 2010
Offline
 
FYI: This will be fixed in an upcoming build.

Regards,
Carsten
 Report
User Avatar
Werner Ziemerink
Member
1269 posts
Joined: March 2014
Offline
 
I submitted this bug as soon as I installed it. Good to hear they are on it.
Werner Ziemerink
Head of 3D
www.luma.co.za
 Report
User Avatar
Mithril
Member
1 posts
Joined: April 2016
Offline
 
This error also happens in 15.5.557. I think this is a high priority issue. Not being able to use materials is kind of a very… very.. big deal. How did this not get noticed?
 Report
User Avatar
neil_math_comp
Member
1743 posts
Joined: March 2012
Offline
 
Mithril
How did this not get noticed?
Apparently, there was some issue with old shader code being cached in our regression tests, so the tests were using the old code and thus kept producing correct output, though that's half-heard 3rd-hand information, so I might have it wrong.
Writing code for fun and profit since... 2005? Wow, I'm getting old.
https://www.youtube.com/channel/UC_HFmdvpe9U2G3OMNViKMEQ [www.youtube.com]
 Report
User Avatar
rodp
Member
5 posts
Joined: April 2013
Offline
 
This is still aproblem with the latest daily build. When will it be fixed?
 Report
User Avatar
goldfarb
Staff
3465 posts
Joined: July 2005
Offline
 
please try today's build (H15.5.560)
seems to be fine now.

thanks
Michael Goldfarb | www.odforce.net
Training Lead
SideFX
www.sidefx.com
 Report
User Avatar
rodp
Member
5 posts
Joined: April 2013
Offline
 
Downloaded 15.5.560 and 15.5.563 but still getting the same issue

Rod
 Report
User Avatar
goldfarb
Staff
3465 posts
Joined: July 2005
Offline
 
damn - sorry - it was fixed - seems to have popped up again.
we're looking into it.
Michael Goldfarb | www.odforce.net
Training Lead
SideFX
www.sidefx.com
 Report
User Avatar
rodp
Member
5 posts
Joined: April 2013
Offline
 
Thanks

Rod
 Report
User Avatar
debris
Member
26 posts
Joined: Nov. 2008
Offline
 
Good to hear you're already on it.

A simple workaround I accidentally found is right-clicking the shader and select “Allow Editing of Contents”.
Ceterum censeo Autodesk esse delendam!
 Report
User Avatar
rodp
Member
5 posts
Joined: April 2013
Offline
 
Thanks this does indeed seem to work.

Hopefully they will get this sorted soon as it is a fundamental problem and I can't use earlier versions because of the windows 10 update bug………
 Report
User Avatar
chrism
Staff
2597 posts
Joined: Sept. 2007
Offline
 
Fixed in today's cut of 15.5.565.
Chris McSpurren
Senior Quality Assurance Specialist
SideFX
 Report
User Avatar
rodp
Member
5 posts
Joined: April 2013
Offline
 
Thank you much appreciated
 Report
User Avatar
debris
Member
26 posts
Joined: Nov. 2008
Offline
 
Confirmed working! Nice!
Ceterum censeo Autodesk esse delendam!
 Report
User Avatar
fgillis
Member
157 posts
Joined: July 2005
Offline
 
Ah… great news. Thought I screwed up dozens of shaders after updating a bunch of otls.

Wondering why there's no mention of this issue/fix in the Journals?
Edited by fgillis - Aug. 14, 2016 00:56:41
Floyd Gillis
 Report
  • Quick Links