[Bf-blender-cvs] [65574463fa2] blender-v2.83-release: Fix T76132: Can't export Alembic with changing UVs

[Sybren A. Stüvel]

Commit: 65574463fa2d31dc912cf886649c62a7d0ad2450
Author: Sybren A. Stüvel
Date:   Tue May 12 14:48:18 2020 +0200
Branches: blender-v2.83-release
https://developer.blender.org/rB65574463fa2d31dc912cf886649c62a7d0ad2450

Fix T76132: Can't export Alembic with changing UVs

In the Alembic exporter, UVs were only exported on the first frame. This
is an issue, as when exporting an animated mesh the topology can change,
and then the UV coordinates of the first frame are no longer valid.

T76132 concerns both exporting and importing changing UVs. This fixes
the exporting.

===================================================================

M	source/blender/io/alembic/intern/abc_writer_mesh.cc

===================================================================

diff --git a/source/blender/io/alembic/intern/abc_writer_mesh.cc b/source/blender/io/alembic/intern/abc_writer_mesh.cc
index a47fe55750e..f7b575e7b23 100644
--- a/source/blender/io/alembic/intern/abc_writer_mesh.cc
+++ b/source/blender/io/alembic/intern/abc_writer_mesh.cc
@@ -335,7 +335,7 @@ void AbcGenericMeshWriter::writeMesh(struct Mesh *mesh)
       V3fArraySample(points), Int32ArraySample(poly_verts), Int32ArraySample(loop_counts));
 
   UVSample sample;
-  if (m_first_frame && m_settings.export_uvs) {
+  if (m_settings.export_uvs) {
     const char *name = get_uv_sample(sample, m_custom_data_config, &mesh->ldata);
 
     if (!sample.indices.empty() && !sample.uvs.empty()) {