Export 3D Object: docs say a texture's graphics take the fill's opacity

docs/mcp.md said the graphics keep their own opacity; they take the
opacity of the face's fill or stroke, and the object's opacity applies
to the face and its graphics together. The split of a solid's mesh is
laid out as rustfmt writes it.
This commit is contained in:
dotCooCoo
2026-11-15 00:43:47 -08:00
parent c1de98b4fc
commit 54acbab14e
2 changed files with 5 additions and 2 deletions
+2 -1
View File
@@ -8453,7 +8453,8 @@ about: in points (USD's layer gives `metersPerUnit`), in meters in glTF. Files t
Graphics mapped onto a plane or onto Extrude & Bevel's front or back cap (`threeD.mapGraphic`) are exported as a PNG
texture of that face: the face's color with its graphics drawn over it, flat and unlit, on a mesh of the face's own
triangles with texture coordinates and a material that shows the texture. A face that is not opaque keeps its opacity
in the texture's alpha, and the graphics keep their own. glTF embeds the PNG as a data URI
in the texture's alpha: as on the canvas, the graphics take the opacity of the face's fill or stroke, and the object's
opacity applies to the face and its graphics together. glTF embeds the PNG as a data URI
(`TEXCOORD_0`, `baseColorTexture`), USDZ stores it after the layer, USDA reads it through `primvars:st`, a
`UsdPrimvarReader_float2` and a `UsdUVTexture` connected to the surface's `diffuseColor`, and OBJ gives `vt` coordinates
and an MTL `map_Kd`; OBJ and USDA write the PNG beside them as `<name>-texture-1.png`, `-texture-2.png` and so on