In a Geometry Collection, enabling Nanite Fallback in a Nanite Enabled collection won't generate a Physics Body when Nanite is disabled. To verify this, follow the steps provided in the Steps to Re ...
Enabling bUpdateComponentTransformToRootBone in a GeometryCollectionComponent causes broken particles to appear in the wrong location. When that flag is true, the moment the GeometryCollection (GC) ...
Fracture Mode > "Remove-On-Break" setting: Cluster Crumbling causes flickering. Once the Remove-On-Break Cluster Crumbling effect is activated, there is a small delay between the disappearance of th ...
A partially broken Geometry Collection (GC) ends up with garbage CollisionGroup data that can lead to strange behaviors. The licensee has noticed that a GC that goes thru a field applying ExternalS ...
Fields with Maximum resolution are not affecting all leaves of a Geometry Collection on 5.4 and onwards. When calling GetRelevantParticleHandles() a Maximum Resolution field does return all particl ...
Chaos Trailing Events not exposed to Blueprints and only accessible via Niagara Chaos DI. The licensee noticed that the Trailing event is not available to BPs. It's expected that the same data avail ...
In Packaged builds, Chaos Cache Manager (CCM) can't animate Geometry Collections (GC) with Nanite Enabled if Cache Mode is set to Static Pose. The licensee tried to animate a CCM using Sequencer onl ...
A Skeletal Mesh simulating physics that hits a Geometry Collection Actor with OneWayInteraction true, OneWayInteractionLevel 1, and is using Damage Propagation (default) will be accelerated so fast ...
Geometry Collection (GC) fragments are affecting the Navmesh in wrong positions and the identified cause is wrong indexing. Once a GC breaks, it's fragments, when big enough, are creating islands in ...
More details in this thread: [Link Removed] ...