Unexpected behaviour when applying linear velocity on GC with AddPhysicsField

Development Asset Creation
, ,
1

This question was created in reference to: [Destroying GC with multiple AddPhysicsField doesn’t seems to work as [Content removed]

Hi !

I have observed some strange behaviour when using PhysicsField on specific Geometry Collection rather than using a TransientField. When doing this the first application of the linear velocity on the intact geometry collection seems to work fine but when applying it a second time on the remaining GC the linear velocity seem much stronger. See attached video for an example.

We use PhysicsField in our custom master field to be able to filter the geometry collection on which we want the master field to be applied. In the project uploaded I simplified our Custom Master Field so only the linear velocity use PhysicsField but on our end all other Transient Field applied are actually replaced with PhysicsField with no issue.

This issue is caused when using the velocity but some very weird behaviours can also be observed when using force (that might be the subject of another post).

[Attachment Removed]

2

Steps to Reproduce

  • Launch the uploaded project and start the PIE
  • Use left click to place the master field on one of the GC.
  • Observe that the linear velocity seems fine
  • Place the master field a second time on what’s left on the GC
  • Observe that the GC seem to take much more velocity than before.
    [Attachment Removed]
3

Hi Raphael, and thank you for the repro.

I’ll dig into this and get back to you - I wonder if the velocity isn’t getting cleared between iterations?

Best

Geoff Stacey

Developer Relations

EPIC Games

[Attachment Removed]