Search Issue Tracker
Won't Fix
Votes
3
Found in [Package]
1.3.X - Entities
7000.0.0a1
Issue ID
ECSB-1094
Regression
No
All Inspectors are affected and one of them rendered blank when changing the Entities Inspector data mode
How to reproduce:
1. Open the user-attached project “findBug_ECSinspectorMode”
2. Open the “SampleScene” scene
3. In the Inspector open the three-dot menu → Add Tab → Inspector to open the second Inspector
4. Change the Layout so two Inspectors are visible at once
5. In the Hierarchy under the subscene “SubScene” select the “Cube” GameObject
6. In one of the Inspectors change the data mode to “Runtime” (Circle near the lock icon in the right-upper corner)
7. Observe the Inspectors
Expected results: Only the Inspector where the data mode was changed is affected
Actual results: Both of the Inspectors are affected and the second one is rendered blank
Reproducible with: 1.0.16 (2022.3.29f1), 1.2.0, 1.2.1 (2022.3.29f1, 6000.0.2f1)
Can’t test with: 2021.3.38f1 (Package versions are not available)
Reproducible on: Windows 11 Pro
Not reproducible on: No other environment tested
Comments (1)
-
martin_noble
May 17, 2024 10:58
I am currently staying on Unity 2022.3.24f1 with Entities 1.2.1, since this issue seems to only be ocurring on Unity versions later that that.
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
There are no fixes planned for this Bug