Search Issue Tracker
Active
Under Consideration for 2022.3.X, 6000.0.X, 6000.1.X, 6000.2.X, 6000.3.X
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Visual artifacts appear when the HD Dynamic Resolution Component changes the resolution scale
- Domain Reload loading popup is dark when Editor Theme is set to "Light"
- Scene Views breaks and errors are spammed in the Console when the Game view is shrunk vertically to the minimum, and the Aspect Ratio is 16:9 or 16:10
- Slider Fill Area disappears after undoing “Set Native Size” change
- Crash with multiple stack traces when playing video on a render texture with low-end graphics devices
Add comment