Search Issue Tracker
Fixed
Fixed in 1.4.X
Votes
0
Found in [Package]
1.2.3
Issue ID
AVPB-470
Regression
No
The polyspatial debug link does not copy over the disabled state of the Camera component
Reproduction steps:
1. Open the attached “Repro“ project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Select the “TestCamera“ GameObject (TestCameraRoot > TestCamera) in the Hierarchy window
4. Observe that the Camera Component is disabled
5. Enter the Play Mode
6. Find and select the equivalent GameObject created by the “Debug PolySpatial Game Object Link” under the “DontDestroyOnLoad” category
7. Observe the Camera Component’s status
Expected result: Camera Component is disabled
Actual result: Camera Component is enabled
Reproducible with: 1.2.3 (2022.3.28f1)
Couldn’t test with: 1.0.3, 1.1.6 (2022.3.28f1) - Camera Component is not copied over
Reproducible on: MR with M1 MacOS 14.4.1
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
- [OpenXR][HDRP] XR Fails to initialize and black screen is present when waking up the HMD with DLSS enabled
- Baked reflection color of clouds does not match the Scene sky color when generating lighting in Unity
- The sampling result will have black artifacts when using URP Sample Buffer with UV value set to 1
- "Assertion failed on expression" errors thrown in Console when opening Profiler (Standalone Process) window
- Skinned Mesh Renderer with multiple Animator Components does not render when "Optimize Game Objects" is enabled
Add comment