Search Issue Tracker
Fixed
Votes
1
Found in [Package]
1.2.3
Issue ID
AVPB-668
Regression
Yes
[VisionOS] PolySpatial 1.2.3:Collider's enabled state on DebugPolySpatialGameObjectLink object won't synchronize with the original collider
Reproduction steps:
1. Create a new visionOS MR project
2. Create a new “Cube“ GameObject in the Hierarchy
3. Enter the Play Mode
4. Find and select the PolySpatial GameObject that corresponds to the “Cube” GameObject inside the “DontDestroyOnLoad“ category in the Hierarchy
5. Observe the Box Collider Component status
6. Select the “Cube“ GameObject in the Hierarchy and disable the Box Collider Component in the Inspector
7. Observe the Box Collider Component’s status of the PolySpatial GameObject that is linked to the “Cube“
Expected result: The component is disabled
Actual result: The component stays enabled
Reproducible with: 1.2.3 (2022.3.35f1)
Not reproducible with: 1.1.6 (2022.3.35f1)
Reproducible on: MR inside Editor
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
Add comment