Unreal Engine Issues

bIncludeComponentLocationIntoBounds breaks bounds calculations

Bounds generation when bIncludeComponentLocationIntoBounds is active is broken. Both the calculation of the local bounds and the world bounds are incorrect (see screenshot). When that flag is acti ...

Lumen Card Sharing is active on material with custom primitive data

The wrong emissive value may be used on Nanite objects with custom primitive data when Lumen card sharing is enabled. This issue can be mitigated with: r.LumenScene.SurfaceCache.AllowCardSharing 0 ...

Weight blended layers can leave ghost traces when cleared

Directory placeholders can get added to the external actor packages.

We should not create placeholders when using WP or OFPA. ...

Vector VM - Crash / memory stomp when using > 255 external function calls

The Vector VM has only every supported a byte's worth of external function calls, when we blew the limit it would index into the incorrect VM call. The new VM will also overwrite memory when exceed ...

Visibility doesn't get effected by hierarcy levels

We use the hierarchy bias to override actions within subsequences. We can do that for transforms and control rigs, but the visibility track doesn't seem to obey the same rules. Attached is a video o ...

Visual helpers for Spacing and Area are visible when occluded

Reported in SF [Link Removed] Visual helpers for Area and Spacing tools are always visible when helpers are enabled, including when occluded by other geometry. This behavior is inconsistent with o ...

Modifying PostProcess Film Slope can cause TSR to produce ghosting artefacts

When TSR is active, the scene is dark, and a foreground object is lit, modifying the Film/Slope value on a PostProcessVolume can lead to TSR ghosting. TSR occurs prior to Tonemapping, so the issue ...

USourceControlHelpers::IsEnabled crashes shipping builds

The licensee has reported that the naming of the IsEnabled node is not descriptive enough and can be easily confused with other IsEnabled functions or variables. The Licensee has requested that the ...

Incorrect resolution used because SetProcessDpiAware() is not called when bAllowHighDPIInGameMode=False

The incorrect resolution is used on computers with 4k monitors that use DPI scaling (default 150%) because the default for UE projects is bAllowHighDPIInGameMode=False which results in SetProcessDp ...