Quality settings should not affect landscape resolution

UE - LD & Modeling - Terrain - Landscape - Mar 10, 2015

Changing the quality settings (or having them change on you automatically in the editor) drops mips on landscape heightmap textures, which isn't desirable as it makes it look like there are collisio ...

Foliage radius does not affect other foliage assets

UE - World Creation - Worldbuilding Tools - Foliage - May 5, 2016

Setting the radius on a foliage asset does not prevent other foliage assets from being painted within that radius. Regression (no) issues (does) occur in 4.10.4 ...

Actor Enable Collision does not affect ISM

UE - Simulation - Physics - Nov 12, 2020

The problem was reported via UE Bug Submission. I was able to repro with their provided test project. ...

Scene Capture Cube not affected by bloom

UE - Virtual Production - Jun 17, 2021

SplineComponent - setting roll affects tangents

UE - Framework - Components - Jun 12, 2023

Licensee reports issue with setting roll on a spline component control point. ...

Synthetic benchmark is affected by Scalability Settings

UE - Rendering Architecture - RHI - Feb 19, 2025

Sumo Digital Ltd. has reported that the synthetic benchmark has skewed GPUIndex scores when changing graphics scalability settings (i.e. r.LumenScreenProbeGather.DownsampleFactor). They are currentl ...

Crash retargetting AnimBP with "Allow remapping to existing assets" enabled

OLD - Anim - Aug 24, 2016

4.12 version of the crash: [Link Removed] Error message: Assertion failed: (Index >= 0) & (Index < ArrayNum) [Link Removed] [Line: 833] Array index out of bounds: 1 from an array of size 0 Sourc ...

[CrashReport] UE4Editor_Foliage!operator<<() [foliageinstancebase.cpp:93]

UE - World Creation - Worldbuilding Tools - Foliage - Jul 5, 2016

This Jira was created from CrashReports submitted by the public due to the high number of occurrences. Descriptions from users are provided below. Error message: Fatal error: [Link Removed] [Line: ...

Float Curve evaluation may yield completely wrong results due to floating-point precision issue

UE - Anim - Runtime - Oct 31, 2024

Note: This is possibly related to [Link Removed]. For some inputs, function UE::Curves::WeightedEvalForTwoKeys() inside file "CurveEvaluation.cpp" can incorrectly return the value of the first key, ...

Sequencer : Attaching a Possessable to multiple Spawnables across multiple cuts causes incorrect location restoration

UE - Anim - Sequencer - Nov 12, 2021

Regression No, according to affects versions 4.27 and 4.27.1 The restore process proceeds in the following order : 1. Remove spawnable actor in first cut (no effect because the actor is already r ...