Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0f3
Issue ID
990242
Regression
No
Field decorated with a Range attribute defaults to 0 instead of the specified minimum value in the Inspector
Steps to reproduce:
1. Open attached “Range.zip” Unity project
2. Right-click in Project Window
3. Create->Test->RangeAttributeTest
4. Select created ScriptableObject asset in Project window
Expected results:
Created ScriptableObject asset Number value in Inspector falls into specified range of [Range(10, 15)] attribute
Actual results:
Created ScriptableObject asset Number value in Inspector defaults to 0 and does not fall into the specified range
Reproduced in: 2018.2.0a1, 2018.1.0b4, 2017.3.0p3, 2017.2.1p2,, 2017.1.3f1, 2017.1.0a1
Note: Same happens when attaching scripts to objects
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
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
- Root motion is not reapplied when transitioning from an animation without root motion to an animation with root motion
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.