WIP: Fix #104730: Make first visible CustomData layer active #104739

When creating a CustomData layer with a name not starting with a dot
while all existing layers of the same type have names which do start
with a dot make the new layer the active/render/mask/clone layer.

It can be confusing if the render layers is a hidden/anonymous layer.

When creating a CustomData layer with a name not starting with a dot while all existing layers of the same type have names which do start with a dot make the new layer the active/render/mask/clone layer. It can be confusing if the render layers is a hidden/anonymous layer.

It's not really a satisfactory fix for this issue. I'm open to better ideas.

Active slot switching node - open design. This looks like a partial private solution.

Also, when not connecting a Texture Coordinate or UV Map node, I think the implicit uvmap is still taken from the original object and not the evaluated object. But I need to investigate that more.

Also, when not connecting a `Texture Coordinate` or `UV Map` node, I think the implicit uvmap is still taken from the original object and not the evaluated object. But I need to investigate that more.

Active slot switching node - open design. This looks like a partial private solution.

Yes, probably. But even when that node exists it is imo very undesirable that an anonymous uv map can be the active/render/mask/clone layer. This needs some thinking/designing I guess.

> Active slot switching node - open design. This looks like a partial private solution. Yes, probably. But even when that node exists it is imo very undesirable that an anonymous uv map can be the active/render/mask/clone layer. This needs some thinking/designing I guess.

Also, when not connecting a Texture Coordinate or UV Map node, I think the implicit uvmap is still taken from the original object and not the evaluated object. But I need to investigate that more.

This turns out to not be true. However when an anonymous layer is the only uvmap on a mesh it will still be considered the render/active/etc layer and thus used for rendering. WHich behaves somewhat unexpected. Maybe an anonymous layers should just never be active/render/etc and the active(etc) layer should just be set to -1 if there are only anonymous layers.

> Also, when not connecting a `Texture Coordinate` or `UV Map` node, I think the implicit uvmap is still taken from the original object and not the evaluated object. But I need to investigate that more. This turns out to not be true. However when an anonymous layer is the *only* uvmap on a mesh it will still be considered the render/active/etc layer and thus used for rendering. WHich behaves somewhat unexpected. Maybe an anonymous layers should just never be active/render/etc and the active(etc) layer should just be set to -1 if there are only anonymous layers.

A better solution is maybe to remove anonymous layers from evaluated objects. (and update the 'active/render' layers as needed. (as discussed in the chat)

I think this should maybe still be useful to add after #105192, maybe after some reworking.

The referenced bug is closed, can this PR be closed as well?

Not sure yet. Part of this fix didn't make it into what was merged. We might need some discussion if it's still needed.

The part that was merged suppresses the usage of anonymous layers for rendering, which prevents the most confusing behavior, but the anonymous layer can still be the 'render' layer or the 'active' layer.

I think it would be a good idea to set the first 'nonanonymous' layer to the active/render/clone layer. But maybe that should wait till the whole system of which layer is 'active' is changed to name based like with the color attributes?.

Not sure yet. Part of this fix didn't make it into what was merged. We might need some discussion if it's still needed. The part that was merged suppresses the usage of anonymous layers for rendering, which prevents the most confusing behavior, but the anonymous layer can still be the 'render' layer or the 'active' layer. I think it would be a good idea to set the first 'nonanonymous' layer to the active/render/clone layer. But maybe that should wait till the whole system of which layer is 'active' is changed to name based like with the color attributes?.

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

WIP: Fix #104730: Make first visible CustomData layer active #104739