[IN-75547] Upgraded to 1.2.3, collider's enabled state on DebugPolySpatialGameObjectLink won't synchronize with the original collider

Unity Engine
, ,
1

Editor: Unity 2022.3.27f1.
PolySpatial plugins: 1.2.3.
v1.1.6 does not have this problem.

How to reproduce:

  • Create a cube(or any 3D object) with a collider.
  • Run the scene and find the cube’s link object through the DebugPolySpatialGameObjectLink component.
  • Toggle the original cube collider’s enabled.
  • => The link object collider’s enabled value won’t be affected. It should mirror the state of the original collider. (The IsTrigger, Center, Size… can follow changes correctly.)

This will create unexpected collisions and raycast results with the DebugPolySpatialGameObjectLink objects when the colliders should be disabled.

2

The most apparent problem caused by this issue is, you can’t make a spatial button unclickable(or make an object unselectable/unmovable) by turning off its collider.
You’ll have to destroy the collider instead of disabling it.

Fortunately, this issue only occurs in the Editor and not on the device. But depending on the development scenario, this could be quite inconvenient until it’s fixed. The most related script may be PolySpatialCompoundCollider.cs but we cannot modify it.