Unreal Engine Issues

Incorrect UVs on imported FBX when collapsed

UVs appear to be broken when client file is imported using Collapse by Material or Collapse All.  ...

Legacy HLOD Nanite Meshes Always Rendering in 5.5

From licensee: We are using the legacy HLOD system in our game. With 5.5 there was a change to FSceneProxyBase::DrawStaticElementsInternal() where the implementation was removed (https://github.com ...

Plugin template WP map missing actors

Video on Led walls doesn't play in the Local presentation on MacOS.

Some objects are imported with incorrect position in Keep Hierarchy

I could only replicate with the user's sketchup file. Exporting this file as fbx, and importing the fbx in KH doesn't have the issue.[Image Removed] ...

Packed level actors and Level instances are sometimes not included in HLOD build on a World Partition Level

Context World Partition - Hierarchical Level of Detail (HLOD) system uses custom HLOD Layers to organize large amounts of Static Mesh Actors and generate a single proxy mesh and Material. Problem T ...

When a Niagara User Parameter is renamed, mesh bindings on Niagara Mesh Renderers are not updated, and the binding is silently broken

In Niagara, Mesh Renderers expose a "Meshes" array for selecting the meshes to be rendered. On each array entry, a property "Mesh Parameter Binding" is available and allows the user to override that ...

Importing static mesh while a PIE session is running permanently breaks nanite on the asset

Importing a Static Mesh during PIE can cause it to never enable Nanite, even if it reports that Nanite is enabled. To re-enable Nanite on the mesh, the asset needs to be deleted and imported again ...

FJsonObjectConverter::ExportCallback_WriteISO8601Dates allows for writing FDateTime that does not have ticks

Context: `FJsonObjectConverter` is a built-in UE class that makes it easy to convert JSON objects to and from UStructs, including `FDateTime`, which implements a date and time. Problem: An uniniti ...

Shading error after flipping normals on mesh

As far as I can guess is that in the initial state of the object, the vertex normals are as they come from the DCC, but after the modeling operation they get recalculated somehow that doesn't match ...