Maya looks: publish paths as an option for look assigner method

[antirotor]

Feature

reference: #1559

to have looks more flexible, lets publish path along with the ids and let the artist choose when applying look what method of look assignment it should use.

This will bring it closer to usd/alembics and allow to apply look to data coming from different dccs.

[cuID:OP-6782]

[BigRoy]

The paths (or at least the long names) are actually already stored in the look .json files currently. For example:

{
  "attributes": [],
  "relationships": {
    "shading_engine_MTLSG": {
      "uuid": "627bbd3a632436a203ff0ef8:a6684026b4a1",
      "members": [{
        "name": "|model_01_:_GRP|model_01_:geo_GRP|model_01_:mesh_a_GES|model_01_:mesh_a_GESShape",
        "uuid": "627bbd3a632436a203ff0ef8:9b7a7cba5128"
      }, {
        "name": "|model_01_:_GRP|model_01_:geo_GRP|model_01_:mesh_b_GES|model_01_:mesh_b_GESShape",
        "uuid": "627bbd3a632436a203ff0ef8:f410f33e62ac"
      }]
    },
  }
}

It's currently a json.dump of the "relationships" collected here in CollectLook. So it'd be a matter of implementing another way of solely assigning the looks.

[antirotor]

Yes, I think the easiest way would be to drop namespaces on path, treat the root as wildcard (or drop it off completely) and then try to match the path on selected hierarchy.

[BigRoy]

Is this closed in favor of another issue? Since I believe the implementation for path based look assignments isn't implemented?

[tokejepsen]

Not sure why the ynbot closed this.

[BigRoy]

@iLLiCiTiT @mkolar why does ynbot keep closing this incorrectly?

[jakubjezek001]

@iLLiCiTiT @mkolar why does ynbot keep closing this incorrectly

The issue was tagged with false ClickUo ID pointing to different issue which had been already closed. This issue should be now kept since it had been reassigned to new ClickUp task. Thanks @BigRoy for pointing at it!