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
- UI Toolkit Debugger Pick Element does not react to the Burst Inspector window when hovering over the Burst Inspector window
- Some buttons in the Burst Inspector window crop the button text from the left side making it unreadable when the window is smaller, and the window has to be almost fullscreen for the full button text to show
- Text in the Burst Inspector Left side panel overlaps/goes out of bounds when scrolling
- Multiple "Incompatible keyword states" or “Keyword state size mismatch (60 vs 59 keywords)“ Errors when opening the project
- Non-editable Repeat - X and Repeat - Y settings appear when UI Builder Canvas Background is set to image
Add comment