Hi again
I get another error with my job on amazon cloud
Submission and pre-flight work well now, my job is now in the amazon cloud. But…
I'm using H14.0.444. I use only standard clay shader and i get this error every frame
Call to undefined function ‘expand_udim’.
well, i do not using udim and i know is a new function. what can i do to avoid this ?
How to fix this and get my job complete on Amazon EC2 renderfarm ?
Amazon EC2, Call to undefined function 'expand_udim'.
5471 18 2
-
- 7on7on
- Member
- 22 posts
- Joined: 12月 2010
- Offline
-
- awong
- Member
- 818 posts
- Joined: 9月 2013
- Offline
The texture vop is updated in 14.0.341 to use the new udim function, which is used by used by the clay material: clay/surfaceColor/texture1. We haven't updated the Amazon Cloud to the newer Houdini build, so maybe that's why your scene fails to render there. The easiest workaround is probably to save the hip file using 14.0.340 or older. That should avoid the problem.
If you don't have access to that older build, you could also override the default Vop/texture node to use the old one. I've attached an HDA that contains the older Vop/texture that doesn't use the expand_udim() function. To use the asset in your scene, use the Assets -> Install Asset Library and select the asset. After loading the asset library, the scene should switch to that definition. You can verify that by middle-clicking the clay/surfaceColor/texture1 node. You should see the “Defined by” line pointing to the newly installed HDA file. If you do this, the Amazon submission process should also bundle this HDA file with it.
Hope this helps!
If you don't have access to that older build, you could also override the default Vop/texture node to use the old one. I've attached an HDA that contains the older Vop/texture that doesn't use the expand_udim() function. To use the asset in your scene, use the Assets -> Install Asset Library and select the asset. After loading the asset library, the scene should switch to that definition. You can verify that by middle-clicking the clay/surfaceColor/texture1 node. You should see the “Defined by” line pointing to the newly installed HDA file. If you do this, the Amazon submission process should also bundle this HDA file with it.
Hope this helps!
Edited by - 2015年9月24日 13:16:39
Andrew / アンドリュー
-
- 7on7on
- Member
- 22 posts
- Joined: 12月 2010
- Offline
-
- 7on7on
- Member
- 22 posts
- Joined: 12月 2010
- Offline
-
- awong
- Member
- 818 posts
- Joined: 9月 2013
- Offline
-
- 7on7on
- Member
- 22 posts
- Joined: 12月 2010
- Offline
-
- awong
- Member
- 818 posts
- Joined: 9月 2013
- Offline
Hm, I wonder if you need to force Houdini to use your definition of the node. You can do this by Assets -> Manage Asset Libraries. Right click on your version of Vop/texture, and select “Use This Definition”. You should see the label turned green.
Did you see the HDA file being included in the submission process?
Did you see the HDA file being included in the submission process?
Andrew / アンドリュー
-
- 7on7on
- Member
- 22 posts
- Joined: 12月 2010
- Offline
-
- awong
- Member
- 818 posts
- Joined: 9月 2013
- Offline
Looks like the texture asset that I attached wasn't old enough. Ok, I mentioned this to our Amazon guy. He'll try to update the build on Amazon in the next day or so.
If you still feel adventurous, I've also re-uploaded an older texture to the post above.
Also, I wonder if this is happening because you have the surfaceColor node embedded into your scene. It's typically not embedded into the scene. Do you remember why it became embedded? If it doesn't need to embedded, you should delete it from the “Manage Asset Library” dialog too.
If you still feel adventurous, I've also re-uploaded an older texture to the post above.
Also, I wonder if this is happening because you have the surfaceColor node embedded into your scene. It's typically not embedded into the scene. Do you remember why it became embedded? If it doesn't need to embedded, you should delete it from the “Manage Asset Library” dialog too.
Andrew / アンドリュー
-
- 7on7on
- Member
- 22 posts
- Joined: 12月 2010
- Offline
-
- awong
- Member
- 818 posts
- Joined: 9月 2013
- Offline
Yeah, I don't think that's normal. It usually comes from the OPlibVop.hda, which is from the Houdini installation directory. Maybe some operation that you did caused Houdini to embed this asset into the scene file. You should be able to revert to the default Houdni one by simply deleting the asset under the “Embedded” tree in that asset library dialog.
Andrew / アンドリュー
-
- 7on7on
- Member
- 22 posts
- Joined: 12月 2010
- Offline
-
- awong
- Member
- 818 posts
- Joined: 9月 2013
- Offline
-
- 7on7on
- Member
- 22 posts
- Joined: 12月 2010
- Offline
-
- 7on7on
- Member
- 22 posts
- Joined: 12月 2010
- Offline
-
- 7on7on
- Member
- 22 posts
- Joined: 12月 2010
- Offline
-
- 7on7on
- Member
- 22 posts
- Joined: 12月 2010
- Offline
-
- 7on7on
- Member
- 22 posts
- Joined: 12月 2010
- Offline
-
- awong
- Member
- 818 posts
- Joined: 9月 2013
- Offline
-
- Quick Links