Search Issue Tracker
Fixed
Fixed in 2023.1.0a9
Votes
0
Found in
2022.2.0b8
2023.1.0a8
Issue ID
UUM-15847
Regression
Yes
Component's field does not change back its type when resetting the component
Steps to reproduce:
1. Open the user’s project
2. Open the “Bugs“ Scene
3. Select the “Bug 3” GameObject in the Hierarchy
4. Right-click the script header (Bug 3 (Script)) → Set to plain Example
5. Notice that Example’s field changed to text-field
6. Right-click the script header (Bug 3 (Script)) → Reset
Expected result: The Example’s field changed back to the slider
Actual result: The Example’s field remains text-field
Reproducible with: 2022.2.0a9, 2022.2.0b8, 2023.1.0a8
Not reproducible with: 2021.3.11f1, 2022.1.18f1, 2022.2.0a8, 2023.1.0a9, 2023.1.0a10
Could not test with: 2020.3.40f1 (Console error)
Reproduced on: macOS Monterey 12.5.1 (Intel)
Note: It changes back to the slider after selecting another GameObject and switching back
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