Navigation
API > API/Runtime > API/Runtime/Chaos > API/Runtime/Chaos/FGeometryCollectionPhysicsProxy
Description
Since geometry collections only buffer data that has changed, when PullFromPhysicsState is given both PrevData and NextData it must examine both PrevData and NextData for data about a particle (since that particle's data coudl be in PrevData and not NextData). PullNonInterpolatableDataFromSinglePhysicsState will do the work to pull the non-interpolatable data (which could include X/R/V/W in certain scenarios) to the game thread.
| Name | PullNonInterpolatableDataFromSinglePhysicsState |
| Type | function |
| Header File | /Engine/Source/Runtime/Experimental/Chaos/Public/PhysicsProxy/GeometryCollectionPhysicsProxy.h |
| Include Path | #include "PhysicsProxy/GeometryCollectionPhysicsProxy.h" |
| Source | /Engine/Source/Runtime/Experimental/Chaos/Private/PhysicsProxy/GeometryCollectionPhysicsProxy.cpp |
bool PullNonInterpolatableDataFromSinglePhysicsState
(
const Chaos::FDirtyGeometryCollectionData & BufferData,
bool bForcePullXRVW,
const TBitArray <> * Seen
)
A boolean indicating whether or not a change to the GT state was detected.
Parameters
| Name | Remarks |
|---|---|
| BufferData | The buffered physics data to pull data from (could be PrevData or NextData). |
| bForcePullXRVW | Whether or not to pull interpolatable data as non-interpolatable data (i.e. X/R/V/W). This happens only when NextData doesn't exist. |
| Seen | The bit array of the previously handled FDirtyGeometryCollectionData (should be null in the case of handling NextData, and should be the TBitArray on NextData when handling PrevData). |