diff options
author | Campbell Barton <ideasman42@gmail.com> | 2020-09-05 18:45:38 +0300 |
---|---|---|
committer | Campbell Barton <ideasman42@gmail.com> | 2020-09-05 19:19:58 +0300 |
commit | 3a8d9198b33d9c90abd3a134ee26e2f68ff52002 (patch) | |
tree | aea4d5dadccc4485857173af0c28a76c73e98b73 /source/blender/io/usd | |
parent | 9978485e8207d1f842f16864bda4260c8fc1335a (diff) |
Cleanup: spelling
Diffstat (limited to 'source/blender/io/usd')
-rw-r--r-- | source/blender/io/usd/intern/usd_writer_mesh.cc | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/source/blender/io/usd/intern/usd_writer_mesh.cc b/source/blender/io/usd/intern/usd_writer_mesh.cc index 75d1ca605d4..7d3ea911a65 100644 --- a/source/blender/io/usd/intern/usd_writer_mesh.cc +++ b/source/blender/io/usd/intern/usd_writer_mesh.cc @@ -106,10 +106,10 @@ struct USDMeshData { pxr::VtIntArray crease_vertex_indices; /* The per-crease or per-edge sharpness for all creases (Usd.Mesh.SHARPNESS_INFINITE for a * perfectly sharp crease). Since 'creaseLengths' encodes the number of vertices in each crease, - * the number of elements in this array will be either len(creaseLengths) or the sum over all X - * of (creaseLengths[X] - 1). Note that while the RI spec allows each crease to have either a + * the number of elements in this array will be either 'len(creaseLengths)' or the sum over all X + * of '(creaseLengths[X] - 1)'. Note that while the RI spec allows each crease to have either a * single sharpness or a value per-edge, USD will encode either a single sharpness per crease on - * a mesh, or sharpnesses for all edges making up the creases on a mesh. */ + * a mesh, or sharpness's for all edges making up the creases on a mesh. */ pxr::VtFloatArray crease_sharpnesses; }; @@ -177,8 +177,8 @@ void USDGenericMeshWriter::write_mesh(HierarchyContext &context, Mesh *mesh) return; } /* The material path will be of the form </_materials/{material name}>, which is outside the - subtree pointed to by ref_path. As a result, the referenced data is not allowed to point out - of its own subtree. It does work when we override the material with exactly the same path, + sub-tree pointed to by ref_path. As a result, the referenced data is not allowed to point out + of its own sub-tree. It does work when we override the material with exactly the same path, though.*/ if (usd_export_context_.export_params.export_materials) { assign_materials(context, usd_mesh, usd_mesh_data.face_groups); |