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.
This commit is contained in:
parent
e5bb02aaa4
commit
65574463fa
Notes:
blender-bot
2023-02-14 08:38:11 +01:00
Referenced by commit a1c9d42584
, Fix T77021: Alembic export of animated mesh with multiple UV maps fails
Referenced by issue #77021, Export animated mesh to alembic fail when there are multiple UV maps
Referenced by issue #76132, Can't import or export Alembic with changing UVs
|
@ -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()) {
|
||||
|
|
Loading…
Reference in New Issue