Search Issue Tracker
Fixed in 2.0.1
Votes
0
Found in [Package]
1.0.5
Issue ID
1182794
Regression
Yes
[Alembic Importer] Dragging the minimum value of the Alembic Importers "Time Range" slider corrupts the whole slider
Reproduction steps:
1. Create a New Project
2. Import the Alembic package and the "cube.abc"
3. Inspect the "cube"
4. Grab the left side of the "Time Range" slider and slide it a bit
Expected Result: Minimum slider value gets changed
Actual Result: The slider gets corrupted
Reproduced with: 2020.1.0a4, 2019.3.0b3, 2019.2.6f1, 2019.2.0b1, 2019.2.0a11, 2019.2.0a8, 2019.2.0a7, 2019.2.0a6
Did not reproduce on: 2019.2.0a5, 2019.2.0a1, 2019.1.14f1, 2018.4.9f1
Could not reproduce on, because no packman: 2017.4.32f1
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note (fix version 2.0.1):
This bug has now been fixed in the latest version of the Alembic package (2.0.1-preview.1)