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
- Project Auditor suggests to update package to a lower version than installed when the recommended package version is not the latest version
- Low performance when multiple meshes using BlendShape are rendered on screen
- TMP Dropdown visually corrupts or disappears when its own GameObject is assigned to "Caption Image" or "Placeholder" elements
- Usymtool tries to upload GameAssembly.pdb when it doesn't exist after building with Mono backend
- “NullReferenceException” error thrown in the Console when running HDRP Wizard “Fix All” in URP project after installing HDRP Package
Add comment