Extra documentation for outputting UV maps from Geometry Nodes #104392

Closed
opened 2023-03-24 21:10:55 +01:00 by Martijn Versteegh · 7 comments

Add 2 small blurbs to the UV Unwrap node and the attributes output docs

Add 2 small blurbs to the UV Unwrap node and the attributes output docs
Member

A complication with 2D Vector attributes

This is also the case with byte color data, the node has to be used there too. Maybe it could say something more basic like "In order to create UV maps (2D vectors) and byte colors, the store named attribute node must be used instead"

When saving UV coordinates to an atribute, you must save them as 2D Vectors on Corners

This isn't quite true though, if the goal is just to create an attribute. We also try to avoid second person in the manual (and in UI text in Blender) since it reads weirdly like a command. it might be more helpful to be more specific:

In order for Blender to recognize the created attribute as a UV map, it must be created with the [](link to store named attribute node) on the face corner domain with the 2D vector data type. This is necessary because there is no 2D vector socket type.

>A complication with 2D Vector attributes This is also the case with byte color data, the node has to be used there too. Maybe it could say something more basic like "In order to create UV maps (2D vectors) and byte colors, the [store named attribute node](link) must be used instead" >When saving UV coordinates to an atribute, you must save them as 2D Vectors on Corners This isn't quite true though, if the goal is just to create an attribute. We also try to avoid second person in the manual (and in UI text in Blender) since it reads weirdly like a command. it might be more helpful to be more specific: > In order for Blender to recognize the created attribute as a UV map, it must be created with the [](link to store named attribute node) on the face corner [domain](link) with the [2D vector](link) data type. This is necessary because there is no 2D vector socket type.
Author
Member

Better like this?

I couldn't find if there is a way to link to a specific section in another file

Better like this? I couldn't find if there is a way to link to a specific section in another file
Member

Seems good to me, I will apply this Monday unless @HooglyBoogly has something to add.

Seems good to me, I will apply this Monday unless @HooglyBoogly has something to add.
Member

Just a couple things, but yeah, looks good.

  • :doc:`store named attribute node</modeling/geometry_nodes/attribute/store_named_attribute> -> :doc:/modeling/geometry_nodes/attribute/store_named_attribute`` That will fill in the name automatically.
  • You can link to specific sections like :ref:attribute domain ``
  • That should be possible for data types too
Just a couple things, but yeah, looks good. - ``:doc:`store named attribute node</modeling/geometry_nodes/attribute/store_named_attribute>`` -> `:doc:`/modeling/geometry_nodes/attribute/store_named_attribute`` That will fill in the name automatically. - You can link to specific sections like `:ref:`attribute domain <attribute-domains>`` - That should be possible for data types too
Author
Member
  • Removed redundant link text
  • Used :ref: to link to the correct section
- Removed redundant link text - Used :ref: to link to the correct section
Author
Member

@Blendify Do you commit it? Or should I commit it to svn myself ? (3.5 branch and trunk I guess? )

@Blendify Do you commit it? Or should I commit it to svn myself ? (3.5 branch and trunk I guess? )
Member

Committed as revision r10104.

Committed as revision r10104.
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender-manual#104392
No description provided.