Avoid <UDIM> in cachedresolver identifiers

[dovanbel]

Hi,

This is not an issue about the Cached Resolver, just a word of caution related to Houdini

My custom identifiers look something like :

mycustomuri:template=usd_asset_layer&Asset=triboule&Step=shading&task_name=shd&sg_asset_type=Prop&extension=usd

I have custom code in PythonExpose.py to convert this to a filepath, so far no problem.

I stumbled on an issue when I tried to convert filepaths of textures using udim's to my identifier scheme.

I first encoded my texture identifier like this :
mycustomuri:template=substancepainter_asset_texture_udim_publish&Asset=triboule&Step=texturing&task_name=tex&UDIM=<UDIM>&colorspace=ACEScg&sg_asset_type=Prop&texture_map=BaseColor&texture_set=DefaultMaterial&extension=exr

Notice the substring <UDIM> inside the identifier. This caused an issue inside Houdini. I saw Houdini trying to replace <UDIM> by numbers (1001 to 1100) in a loop. Meaning, Houdini was processing the identifier before the identifier was processed by my PythonExpose.py.

So, avoid <UDIM> in your identifiers :-)

Regards

[LucaScheller]

Hey, I'm currently unable to reproduce this.

If I take the input identifier above, it correctly gets passed as-is to the python exposed methods.

Are you seeing the expansion happening within a parm?