6023a6a4237d681a05ffaba628969ad60d67ae9c
Exposed by383a145a19. Think the issue actually started incfa53e0fbe, since then the new destination normals were only filled from the first array copy onwards (probably hidden by some recalculation of normals somewhere?). In any case, starting the destination normals array with what we have from the input mesh normals and then resizing the array (instead of reinitializing it from scratch) fixes this. Pull Request: https://projects.blender.org/blender/blender/pulls/115612
…
Blender
Blender is the free and open source 3D creation suite. It supports the entirety of the 3D pipeline-modeling, rigging, animation, simulation, rendering, compositing, motion tracking and video editing.
Project Pages
Development
License
Blender as a whole is licensed under the GNU General Public License, Version 3. Individual files may have a different, but compatible license.
See blender.org/about/license for details.
Description
Languages
C++
78%
Python
14.9%
C
2.9%
GLSL
1.9%
CMake
1.2%
Other
0.9%
