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
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
Add comment