Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.41f1
Issue ID
UUM-119375
Regression
No
Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
Reproduction steps:
1. Open the attached project “ReproProject“
2. Enter Play Mode with a VR headset connected
3. Select different GameObjects in the Hierarchy window
4. Observe the Inspector window when selecting different GameObjects
Expected result: The Inspector window should immediately update to display the properties of the newly selected GameObject
Actual result: The Inspector window fails to update and continues displaying the previously selected GameObject's properties, despite a different GameObject being selected in the Hierarchy
Reproducible in: 6000.0.41f1
Not reproducible in: 2022.3.x
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Reproducible on devices:
- Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno (TM) 740
Workaround: Clicking on the same GameObject again or selecting a different GameObject may force the Inspector to update correctly
Notes:
- CQA was not able to reproduce this issue
- The issue occurs approximately 5% of the time, making it difficult to consistently reproduce
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
Resolution Note:
Thank you for reporting.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.