Mark Tucker

Be careful with backslashes in node parameters. All string parameters are run through a parser to expand environment variables, and it treats backslashes as an escape character. So if you want to look for a backslash in an asset path, you have to double up the back slashes in the parm. Also, this node works on the un-resolved asset paths. I think USD asset resolution returns paths with backslashes, but maybe the actual asset path before being resolved is using forward slashes?

You might want to try using the python method to make sure that the asset paths being tested are what you expect (using print statements) and make sure that the node is at least capable of doing some replacement (which would narrow down the issue to how the LOP is doing the prefix test). Can you attach a simple hip file showing the issue?

Settings point to products. So picking a different Settings prim picks a different (set of) Product(s) implicitly. Providing an explicit product specification would be redundant. I think it's probably just as easy to do in your USD file by making a new render settings prim (referencing an existing settings prim) and overriding the Products relationship yourself.

I suspect you need to change the way you're authoring that "overlay" layer so that /Character_GEO is "untyped" (or a pure "Over" prim) rather than a "Defined" Xform prim. As you've currently authored this layer, referencing it onto /root/Armature/Character_GEO will turn your Skel prim into an Xform prim. You probably also don't want /Character_GEO to be marked as a "Component". The Kind of this prim should be left blank.