Search Issue Tracker
By Design
Votes
0
Found in
2022.3.62f1
6000.0.48f1
6000.1.3f1
6000.2.0b1
6000.3.0a1
Issue ID
UUM-104860
Regression
No
Default Preset application and Reset() method execution order is different when adding a Component via the Inspector versus calling Reset via the Component context menu
Reproduction steps:
1. Open the attached “IN-101122.zip” project
2. Open the “SampleScene”
3. In the Hierarchy, select the “Test” GameObject
4. Drag the “Test” Script from the Project Window to the Inspector
5. Observe the “Preset and Reset Number” property in the “Test” Component
Expected result: “Preset and Reset Number” property value is 5
Actual result: “Preset and Reset Number” property value is 10
Reproducible with: 2022.1.0a1, 2022.3.62f1, 6000.0.48f1, 6000.1.3f1, 6000.2.0b1
Reproducible on: Windows 10 (user reported), Windows 11
Not reproducible on: No other environment tested
Note:
- Clicking three dots on the Component > Reset, shows the expected result
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
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
Thank you for bringing this to our attention. I understand this behavior can be confusing and less than ideal from a user experience perspective.
After consideration, we've determined that we cannot modify this execution order without significant risk to the Unity ecosystem. This behavior is deeply embedded in Unity's component initialization system and has been the established pattern since Default Presets were introduced. The current execution order (Reset() first, then presets) when using the context menu is by design to ensure preset values always take precedence.
While this isn't the ideal user experience, maintaining stability and backward compatibility for the broader Unity community must take precedence. We appreciate your understanding and will keep this feedback in mind for future architectural decisions.