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
- Cursor doesn't change to the resizing when using the Rect Tool and the Sprite is too close to the bottom of the Scene View
- InvalidOperationException exception is thrown when Editor Default Text Rendering Mode is set to "Bitmap" and Editor Font is set to "System Font" and an array is expanded in the Inspector Window
- "Sample Gradient" node can be connected to the "Sub Mesh Mask" input and makes the VFX Graph uncompilable
- "LoadFontFace_With_Size_and_FaceIndex_FromFont_Internal can only be called from the main thread." exception is thrown when opening an editable array in the Inspector while Editor Default Text Rendering Mode is set to "Bitmap"
- EditorGUILayout.PropertyField foldout icon inside Vertical Layout Group has an incorrect indent when used with OnInspectorGUI()
Add comment