Search Issue Tracker
Fixed
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment