2641216344fa14f726b7dcfad3b2f98ac0b04587
When quickly running the "frame step" and "insert key" operators it was possible to run the key insertion when the depsgraph hasn't yet been updated. Because the key insertion code took the frame from the scene, but the channel values from the depsgraph, the inserted keys were appearing to be duplicated from a different frame. Compared to the previous solution #124583 this moves the code to ensure an evaluated depsgraph into a new invoke function for the operator. This avoids the performance issues when calling the operator from python (#125888) Pull Request: https://projects.blender.org/blender/blender/pulls/126123
…
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%
