Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.2
2019.2.3f1
2019.3
2020.1
Issue ID
1181869
Regression
No
Mesh.AddBlendShapeFrame API produces broken blendshapes on Mesh assets after any existing blendshape slider has been adjusted
How to reproduce:
1. Open attached Unity project
2. Select CubeBlend in the Hierarchy window
3. In the Inspector window, click "Link SMR"
4. Click "Create/Link"
5. Enter a unique blendshape name
6. Click "Duplicate"
7. Adjust created slider - vertices move
8. Repeat 5 and 6 steps - vertices don't move
Expected result: Sliders should move vertices.
Actual result: Sliders, created after moving created sliders, has no effect on vertex movement.
Reproduced with: 2019.2.8f1, 2019.3.0b6, 2020.1.0a8.
Notes:
- User mentioned that this is a regression from 2017 or 2018 Unity version. Can't test it. The project doesn't work correctly in 2017.4 Unity version.
- Can't test on 2018.4. Project crashes on opening.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment