Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0a9
2018.4.0f1
2019.1.0a1
2019.1.5f1
2019.2.0a1
2019.3.0a1
Issue ID
1160752
Regression
No
Mesh normals are getting corrupted while editing blend shapes if Blend Shape Normals are set to Import
To reproduce:
1. Open user attached project "TesBorrame.zip"
2. Open "BlendShapes Bug.unity" scene
3. In the hierarchy select Default > Survivor 1 game object
4. In the Inspector in Skinned Mesh Renderer > Blendshapes edit any blend shape and observe the model
Expected: normals are added to the blend shapes correctly without artifacts
Actual: mesh normals become broken the more the blend shapes are changed
Reproduced on:
2018.3.0a9 2018.4.14f1 2018.4.4f1 2019.1.10f1 2019.2.0b9 2019.3.0a7
Notes:
- Unity crashes while opening the project on 2019.3.0a8 - 2019.3.0a9
- Missing prefabs in 2017.4.30f1
- Models are nor visible on 2018.3.0a3 - 2018.3.0a8
- Enabling Legacy Blend Shape Normals or setting Blend Shape Normals to None fixes the issue
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2019.3.X):
There's an issue with blendshape normals in the FBX SDK which causes those artifacts in some cases. As mentioned earlier, the workaround is to use 'Legacy Blendshape Normals'. Unfortunately there's nothing we can do on our end to fix this.