unreal.CollisionEnabled

class unreal.CollisionEnabled

Bases: EnumBase

Enum used to describe what type of collision is enabled on a body.

C++ Source:

• Module: Engine

• File: EngineTypes.h

NO_COLLISION: CollisionEnabled

Will not create any representation in the physics engine. Cannot be used for spatial queries (raycasts, sweeps, overlaps) or simulation (rigid body, constraints). Best performance possible (especially for moving objects)

Type:

0

PHYSICS_ONLY: CollisionEnabled

Only used only for physics simulation (rigid body, constraints). Cannot be used for spatial queries (raycasts, sweeps, overlaps). Useful for jiggly bits on characters that do not need per bone detection. Performance gains by keeping data out of query tree

Type:

2

PROBE_ONLY: CollisionEnabled

Only used for probing the physics simulation (rigid body, constraints). Cannot be used for spatial queries (raycasts, sweeps, overlaps). Useful for when you want to detect potential physics interactions and pass contact data to hit callbacks or contact modification, but don’t want to physically react to these contacts.

Type:

4

QUERY_AND_PHYSICS: CollisionEnabled

Can be used for both spatial queries (raycasts, sweeps, overlaps) and simulation (rigid body, constraints).

Type:

3

QUERY_AND_PROBE: CollisionEnabled

Can be used for both spatial queries (raycasts, sweeps, overlaps) and probing the physics simulation (rigid body, constraints). Will not allow for actual physics interaction, but will generate contact data, trigger hit callbacks, and contacts will appear in contact modification.

Type:

5

QUERY_ONLY: CollisionEnabled

Only used for spatial queries (raycasts, sweeps, and overlaps). Cannot be used for simulation (rigid body, constraints). Useful for character movement and things that do not need physical simulation. Performance gains by keeping data out of simulation tree.

Type:

1