Unreal Engine Issues

[USD EXPORT] USD Exporter does not export subsequence data from the master sequence

As described in the steps to reproduce, when exporting a selected binding somwehere in a sequence hierarchy into usd, the export yields an empty result when using 'selection only' option. The export ...

USD Stage - Import loses UV on a skeletalmesh with animation

https://forums.unrealengine.com/t/usd-import-issue-when-trying-to-import-skeleton-with-animation/2718449 I put another png has the user forgot to add theirs. ...

USD Export - crashes when sub level holds level instance

The engine is crashing when the user tries to export from a persistent level with a sub level that contains a level instance. ...

Level Sequence SpotLight USD Exporter Bug

The attributes for spotlights are not exported. ...

Skeletal mesh reimport via legacy import creates duplicate Mesh sockets

Reimporting a Skeletal Mesh via legacy import duplicates mesh sockets. The issue does not reproduce when using the Interchange pipeline. ...

FBX Export - StaticMesh export to FBX crashes if UVElements has more channels than VertexInstanceUVs

As indicated in the repro steps, we have a StaticMesh asset that, for some reason, has a mismatch in their serialized bulk data where:MeshDescription->GetNumUVElementChannels() == 2FStaticMeshConstA ...

Temporal blur artifacts on Geometry Cache Components in Blueprint actor

When a Geometry Collection is in a Blueprint, attached to other components, it can render incorrect motion vectors at some angles. In the test project, any angle that is not a multiple of 45 will re ...

FBX Import - Morph target normals not correctly applied when imported as LOD 0

This is a regression since 5.5 with skeletal meshes where morph target normal/tangent deformation only works when a mesh is imported as a LOD of an existing skeletal mesh, but not when imported as L ...

FBX Export - Skeletal Meshes created in Unreal with only a root bone do not export correctly

Mesh Variation node usage inside macro - lost of material slot name

When using a mesh variation node within a macro instance script, the material slot name of the input mesh is not transferred. On the generated mesh output, the material slot name is "None" ...