UV operations skipped in alpha when using texture coordinate node. #104730

New Issue

Paul · 2023-02-14T09:08:54+01:00

Paul commented

2023-02-14 09:08:54 +01:00

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: AMD Radeon (TM) R9 390 Series ATI Technologies Inc. 4.5.14800 Core Profile Context 22.10.1 31.0.12019.16007

Blender Version
Broken: version: 3.5.0 Alpha, branch: main, commit date: 2023-02-14 02:26, hash: 46c34ba1f666
Worked: (newest version of Blender that worked as expected)

Short description of error
UV math operations made in geometry nodes are skipped when using texture coordinate node.

Exact steps for others to reproduce the error
Take UV from any geometry nodes primitive, and store it, try to do vector math on connection between Store Named Attribute and UV output from primitive.

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: AMD Radeon (TM) R9 390 Series ATI Technologies Inc. 4.5.14800 Core Profile Context 22.10.1 31.0.12019.16007 **Blender Version** Broken: version: 3.5.0 Alpha, branch: main, commit date: 2023-02-14 02:26, hash: `46c34ba1f666` Worked: (newest version of Blender that worked as expected) **Short description of error** UV math operations made in geometry nodes are skipped when using texture coordinate node. **Exact steps for others to reproduce the error** Take UV from any geometry nodes primitive, and store it, try to do vector math on connection between Store Named Attribute and UV output from primitive. ![image](/attachments/31da0d21-a249-4686-bbf0-dba34c163ff6)

image.png

562 KiB

Paul added the

labels 2023-02-14 09:08:55 +01:00

Iliya Katushenock commented

2023-02-14 10:02:28 +01:00

Are you sure you can access the UV attribute this way? This seems to be how you get the active attribute, but not yours.

Martijn Versteegh commented

2023-02-14 11:43:57 +01:00

I looked into it some. What happens is this:

As soon as you conenct something to the UVMap output socket of the cube node, the cube node creates an anonymous UV attribute. Because there is no UVMap yet, this will be set as the 'active' and the 'render' UVMap.

In the example above the UV map is saved to 'UVMap', but because there already is a (invisible, anonymous) UV map it doesn't get set as the 'render' or 'active' map, amd the hidden uvmap still gets used.

I looked into it some. What happens is this: As soon as you conenct something to the UVMap output socket of the cube node, the cube node creates an anonymous UV attribute. Because there is no UVMap yet, this will be set as the 'active' and the 'render' UVMap. In the example above the UV map is saved to 'UVMap', but because there already is a (invisible, anonymous) UV map it doesn't get set as the 'render' or 'active' map, amd the hidden uvmap still gets used.

Martijn Versteegh self-assigned this 2023-02-14 11:44:34 +01:00

Iliya Katushenock commented

2023-02-14 12:20:23 +01:00

Anonymous attributes can be active?

Paul commented

2023-02-14 12:52:39 +01:00

Are you sure you can access the UV attribute this way? This seems to be how you get the active attribute, but not yours.

Well since 3,5 I sort of can I thought that this is new feature with some issues.

> Are you sure you can access the UV attribute this way? This seems to be how you get the active attribute, but not yours. Well since 3,5 I sort of can I thought that this is new feature with some issues.

Martijn Versteegh commented

2023-02-14 13:19:49 +01:00