When working on the level editor viewport or testing on PIE, the visual appearance of additive/translucent lit materials changes significantly (and abruptly) when varying the camera FOV or the viewp ...
The game can crash when one thread clears RunTimeToPSOUsage while another thread is expecting it to contain a PSO it is registering stats for. Thread A: calls CacheGraphicsPSO() Thread B: calls C ...
ChaosCacheManager is not properly recording the state of each particle when toggling Fields and Anchor Fields in the scene. During my investigations I've noticed that ChaosCacheManager does not reco ...
Might relate to issue [Link Removed] - "The Remove-On-Break feature, set on Fracture Mode on Geometry Collections, stops shrinking and shows strange behaviors" The added information on this particu ...
Currently, Niagara Components are only expected to have their TickComponent() method called when their system is marked as "Solo", which makes them be simulated individually. In the most common scen ...
A Packaged build that has had an Editor Only Component added to one of its Blueprints logs a false positive warning in USimpleConstructionScript::FixupRootNodeParentReferences(): USimpleConstructio ...
The order of passes related to Decal rendering (without the DBuffer) and CustomDepth is changed by the CVar "r.Lumen.AsyncCompute", even when Lumen is not enabled. This causes Decal Materials that ...
Consider an actor defined in C++ with "bIsSpatiallyLoaded" set to true (the default), and a derived blueprint that overrides "bIsSpatiallyLoaded" to false. Now consider an actor instance of that blu ...
The Remove-On-Break (ROB) feature, set on Fracture Mode on Geometry Collections (GC), was supposed to make the particle shrink until it vanishes. When the GC goes to sleep the shrinking stops and sh ...