Maniphest T96154

Baking ignore selected image/uv and bakes to wrong one. Bug? Old behavior?
Closed, Archived

Assigned To
None
Authored By
Vyacheslav (hitrpr)
Mar 3 2022, 6:43 PM
Tags
  • BF Blender
Subscribers
Ethan Hall (Ethan1080)
Richard Antalik (ISS)
Vyacheslav (hitrpr)

Description

System Information
Operating system: Windows-8.1-6.3.9600-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12

Blender Version
Broken: version: 3.0.1, branch: master, commit date: 2022-01-25 17:19, hash: rBdc2d18018171
As title said. Here is the file.


If UV named «To» is selected, it will be used as baking source, instead UV «From» connected inside shader.

Event Timeline

Vyacheslav (hitrpr) created this task.Mar 3 2022, 6:43 PM
Vyacheslav (hitrpr) renamed this task from Baking ignore selected image/uv and bakes to wrong one to Baking ignore selected image/uv and bakes to wrong one. Bug? Feature? Old behavior?.Mar 3 2022, 6:53 PM
Richard Antalik (ISS) closed this task as Archived.Mar 4 2022, 3:16 AM
Richard Antalik (ISS) added a subscriber: Richard Antalik (ISS).

After checking code I don't see such feature implemented.

Vyacheslav (hitrpr) added a comment.Mar 4 2022, 3:55 AM
In T96154#1316921, @Richard Antalik (ISS) wrote:

After checking code I don't see such feature implemented.

So if it is not feature, it is a bug.
Why did you closed report?

Richard Antalik (ISS) added a comment.Mar 4 2022, 4:04 AM

What I said in other words is, that as far as I can see, this feature was never meant to do, what you want from it.

Ethan Hall (Ethan1080) added a subscriber: Ethan Hall (Ethan1080).EditedMar 4 2022, 7:09 AM

I think the problem here is with the Blender Docs. The docs need to mention that the selected UV map will be used to bake data onto the target texture, and a UV map is not required for baking to vertex colors. The vector input of the target image texture node does not effect the bake.

Vyacheslav (hitrpr) added a comment.EditedMar 4 2022, 4:54 PM
In T96154#1316946, @Ethan Hall (Ethan1080) wrote:

I think the problem here is with the Blender Docs. The docs need to mention that the UV map marked as Active Render

But it use selected, not active for render (camera icon)!
Also it should bake what user see with current the shader. Not something, that connected by obscure rule!

So please reopen! As papercut, bug, todo, no matter. This is huge issue with baking now!

Vyacheslav (hitrpr) renamed this task from Baking ignore selected image/uv and bakes to wrong one. Bug? Feature? Old behavior? to Baking ignore selected image/uv and bakes to wrong one. Bug? Old behavior?.Mar 4 2022, 5:17 PM
Ethan Hall (Ethan1080) added a comment.Mar 4 2022, 10:14 PM
In T96154#1317140, @Vyacheslav (hitrpr) wrote:

But it use selected, not active for render (camera icon)!

Oops, you are right about that.

Also it should bake what user see with current the shader. Not something, that connected by obscure rule!

There is a good reason why baking doesn't evaluate the input of the target Image Texture Node. The input on the Image Texture Node can be anything, not just UV maps. However, baking to a texture only makes sense with UV maps. Using the UV map marked as Active Render would make more sense to me though. The documentation definitely needs to be more clear in any case.

Vyacheslav (hitrpr) added a comment.EditedMar 9 2022, 11:26 PM
In T96154#1317254, @Ethan Hall (Ethan1080) wrote:
In T96154#1317140, @Vyacheslav (hitrpr) wrote:

Using the UV map marked as Active Render would make more sense to me though.

The issue, that render icon is «UV that rendered», donor, source, not recipient!
Also few UVs can be recipients.
I supose that is why developers made selected UV as target.
IDK where UV with render icon actually used and why icon can be inly switched.

Yes, it is usual case is baking from few UV`s and textures to one texture and UV.
But what if I need to bake few materials, from few UV`s to 2 different UV`s? One target UV for albedo (more detailed)
and one for normals (more optimized, mirrored).
Is it even possible with current system «only one target»?

Now all looks like abandoned part, and it needs good system design.
It is not about bug, right. But still about design, UI, UX