Search Issue Tracker
In Progress
Fix In Review for 6000.3.X, 6000.4.0a4
Votes
0
Found in
2022.3.61f1
6000.0.47f1
6000.2.1f1
6000.3.0a5
6000.4.0a1
Issue ID
UUM-113957
Regression
No
Property values are not restored for all objects when re-enabled after reset
Steps to reproduce:
- Open the attached package
- Open Instance Editing Scene
- Select B and C objects in the scene
- Untick the box next to the Gradient property
- Observe that both B and C objects gets assigned default gradient which is expected
- Tick the box next to the Gradient property again
Actual results: Observe that object B gets its gradient reassigned, but object C retains the default value and does not have its gradient reassigned
Expected results: Both objects get their gradient value re-assigned
Reproducible with versions: 2022.3, 6000.0.47f1, 6000.3.0a5
Not reproducible with versions:
Can’t test with versions:
Tested on (OS): macOS
Notes:
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
Add comment