user_data_string into image node udim

[tjvollB4GZV]

Further to my previous post, I am now trying to incorporate udim textures into the scenario.

A udim texture path that works with an image shader node no longer gets applied correctly when assigning via the ArnoldUserData node.

 ERROR   |   [texturesys] Could not open file: ....<udim>.tif: No such file or directory

Is this a known limitation? If so, is there a work around?

[Stephen.Blair · Accepted solution]

This might be the case I was thinking of before. Try using the <attr> token instead of connection a user data shader.

[tjvollB4GZV]

Thanks, Stephen!

For anyone interested, it worked as long as <udim> was outside of the <attr> token.

ie.

This is the filename parameter,

<attr:texture_attribute>.<udim>.tif

[Mike_Farnsworth]

Yeah, you can't nest texture tags (they're not recursive).

[laurent.clavier]

The udim token, as others, is detected at update time of the image node : ie. before the shading operate on any object. At that time, values coming from object user datas can't be solved.

This means that no object dependent user data can be used to set a filename using udim token. But you can use unconnected generic token based filename to resolve filename templates.

It will be difficult to treat udim and non-udim files with the same image node though, it's certainly easier to drive a switch node between udim and non-udim file nodes in that case. Or make non-udim files use udim naming even with a single udim.