Search Issue Tracker
Fixed
Fixed in 6000.0.18f1, 6000.1.0a1, 7000.0.0a1
Votes
4
Found in
2021.3.39f1
2022.3.33f1
6000.0.7f1
6000.1.0a7
7000.0.0a1
Issue ID
UUM-74316
Regression
No
VisualElements that use TrackPropertyValue keep tracking properties when they are removed
Reproduction steps:
1. Open the attached “BugRepro” project
2. Select the “Assets/BugDemonstrator.asset” asset
3. Click the "Add Tracking Element" button in the Inspector window
4. Click the “Remove” button in the Inspector window
5. Click the "Add Tracking Element" button in the Inspector window
6. Click the "Modify tracked property" button
7. Observe the Console window
Expected result: Element properties are not tracked once they have been removed
Actual result: “Element 0 is still tracking even though it's been removed.” message is thrown
Reproducible with: 2021.3.39f1, 2022.3.33f1, 6000.0.7f1
Reproducible on: Windows 11
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
- 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
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment