Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2020.2
2021.1
2021.1.0b3
Issue ID
1310843
Regression
No
[2D] Sprite Library blending float values have to match exactly for the sprite change to occur
Reproduction steps:
1. Open the project in "2021.1.zip"
2. Open SampleScene and enter play mode
3. Inspect the blend value
Expected result: Sprite changes should occur once the float value is at the middle of the 2 blend values (at 0.25, 0.75)
Actual result: The Sprite change almost never occurs because the value compared are floats (float == float)
4. Press Snap in the top right corner of the game
Workaround: Blend values will be rounded to the nearest 10^(-1) and the Sprites now will be changing (however they will change at 0, 0.5, 1 which is not the expected behaviour, the changes should be at 0.25, 0.75)
Reproducible with: 2021.1.0b10, 2021.2.0a7
Could not test with 2018.4.32f1, 2019.4.21f1, 2020.2.7f1 because of package errors (could not resolve them)
Note: video is attached 2021-03-03 11-46-33.mp4 (1.3 MB)
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 ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note:
The changes needed to fix this cannot be backported and the work to fix this has been added to the backlog as it requires more work. Resolving this as postponed.