37421d12bd
When autokeying a property with a driver, the code added the keyframe into the drivers FCurve. Judging by the code the intention was to be able to quickly set up driven keys by modifying the driven value and have that reflected in the driver curve. However that idea was blocked by the fact that you can't actually change the value of a property that is driven. In addition to that it's quite unexpected and the result is hardly communicated to the user. The solution is to not insert keyframes to drivers using the autokeying system. Also Fixes #95866 This was discussed in the A&R module meeting https://devtalk.blender.org/t/2024-01-11-animation-rigging-module-meeting/32888#patch-review-decision-time-5 and the consensus was the feature to set up driven keys would be great, but since it's not working at all currently it's better to get rid of the bugs. Pull Request: https://projects.blender.org/blender/blender/pulls/116927
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.