Search Issue Tracker
Fixed
Fixed in 2022.3.33f1, 6000.0.7f1
Votes
0
Found in
2022.3.32f1
6000.0.5f1
7000.0.0a1
Issue ID
UUM-73153
Regression
Yes
A secondary Inspector does not show Entity properties when two instances of Inspectors are open
How to reproduce:
1. Open the “EntitiesSamples.zip“ project
2. Open the “demo“ Scene
3. Open a second instance of the Inspector (if it is not open already)
4. Enter the Play Mode
5. Select any one Entity GameObject under the “New Sub Scene“ in the Entities Hierarchy
6. Put both Inspectors into “Runtime“ Mode
7. Observe the Inspectors
Expected results: Both Inspectors show the same Entity data
Actual results: Only one Inspector shows the data
Reproducible in: 2022.3.25f1, 2022.3.32f1, 6000.0.5f1
Not reproducible in: 2022.3.24f1
Could not test in: 2021.3.39f1 (No Entities package)
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
Workaround: “Lock” both instances of the Inspector
Notes:
- It looks like all changes done on the secondary Inspector transfer wholely to the primary Inspector
- If both Inspectors show the data correctly, “lock“ and “unlock” both instances of the Inspector, this will mess it up again
- Regular GameObject data is shown correctly on both Inpector instances
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Add comment