Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2018.1.X
Votes
0
Found in
2018.1.0b8
Issue ID
1006561
Regression
No
Default preset is not applied when dragging component from Project window to Inspector
To reproduce:
1. Open the "Unity2018.1.0b8 - Default Preset Bug.zip" project
2. Select "Presets/MyComponentPreset0" in Project window and set Test Value to 100
3. Open the Sample Scene, drag MyComponent script to PresetTarget game object in the Hierarchy
4. Observe that TestValue is 100
5. Drag the MyComponentScript into the Inspector
6. Observe that TestValue is 0
Expected: dragging component to Inspector applies the default preset of the component
Reproduced in 2018.1.0a6, 2018.1.0b1, 2018.1.0b8, 2018.1.0b9, 2018.2.0a2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor fails to render and NRE errors thrown when Domain is reloaded after code changes and Image component is visible in Inspector
- Native allocations appear as Unrooted when tracing GraphicsStateCollection
- Profiler data stream has invalid signature" errors are thrown when loading a .highlights file in the Profiler
- Hierarchy is not updated when a selected GameObject's visibility is toggled with a shortcut when Scene view is not visible
- [AI Assistant] UI elements overlap
Add comment