Localize Texture of Child Object with Texture Tag Selected

Issue #2 on hold
Rick Barrett created an issue

Not sure if this is a bug, but it's a bit of a gotcha.

If you have a texture tag selected and a child object, localize textures creates a new material and replaces the material on the selected texture tag. I expected it to apply a new material on the child object.

This is really an issue with tag selections in C4D and how barely anyone pays attention to them. The texture tag just happened to already be selected and I clicked the child object.

Perhaps if a child object is selected it should use that behavior first and the texture tag replacement as the fallback behavior?

Comments (4)

  1. Donovan Keith

    Hey Rick,

    The order of operations goes from most specific -> least specific with a lot of the commands. Perhaps that should be spelled out in the documentation.

    1. If you have a texture tag selected anywhere, the command only operates on that, not the selected objects.
    2. If you don't have any texture tags selected, it will localize the right-most texture tag on all selected objects.
    3. If you don't have any texture tags on your objects, it will create a local texture on all selected objects.
  2. Donovan Keith

    So you're saying that the order of operations should be:
    1. Selected object's right-most texture tag.
    2. Selected object - create texture tags if you have to.
    3. Selected texture tags.

    What should I do in the situation where there objects and texture tags (not necessarily on the same object) selected?

    I think I like the current method as it's consistent with the behavior of the rest of these tools, but am open to revisiting if I get more feedback of this sort.

  3. Donovan Keith

    Waiting for more user feedback one way or the other. At the moment, we've got an even split of opinion.

  4. Log in to comment