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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
Add comment