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

… just checked production build 15.5.523: OK.

regards,
Carsten

FYI: This will be fixed in an upcoming build.

Regards,
Carsten

I submitted this bug as soon as I installed it. Good to hear they are on it.

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?

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.

This is still aproblem with the latest daily build. When will it be fixed?

please try today's build (H15.5.560)
seems to be fine now.

thanks

Downloaded 15.5.560 and 15.5.563 but still getting the same issue

Rod

damn - sorry - it was fixed - seems to have popped up again.
we're looking into it.

Thanks

Rod

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”.

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………

Fixed in today's cut of 15.5.565.

Thank you much appreciated

Confirmed working! Nice!

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?