More details in this [Link Removed] ...
Geometry Collections (GC) built with "Use Root Proxies" rendering/transform positions ignore the original root node rotation and can lead to unexpected behaviors. If the root node of the GC was rot ...
Geometry Collection's Chaos Cache Static Pose Scrubbing broken in 5.6 due to Custom Renderer GeometryCollectionRootProxyRenderer. The licensee has provided his analysis: In 5.6, when creating a Geo ...
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 ...
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 ...
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 ...
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 ...
Using GeoMerge on fragments of a GeometryCollection (GC) will create a new single particle while removing the old particles, but although you end up with less particles, the disk file size of the GC ...
A Geometry Collection with Removal-On-Break, after breaking and shrinking until vanished, will reset to the original state (full-size and unbroken) if we toggle between Fullscreen and Windowed while ...