| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Use Python's native raw formatting instead, which should take care of any issues
we may face.
|
|
using the Export to File operator
Previously, if double-quotes appeared in the KeyingSet.bl_description field,
these would cause a syntax error in the resulting .py script export of the
KeyingSet. Since single quotes are even more likely to appear
(e.g. as apostrophes), we now use triple quotes here.
Unreported bug, noticed earlier when investigating T61010.
|
|
This was already the bl_idname anyways.
Now this seems to be working, for single and multi-pose.
That said, the operator seems to fail on redo.
|
|
- Logical use of fields since they define type information.
- Avoids using ordered-dict metaclass.
Properties using regular assignments will print a warning and load,
however the order is undefined.
|
|
Internally it's still mostly named lamps, though some modules like Cycles
were already calling them lights.
|
|
|
|
Previously only the active object was used.
Use coroutines to support baking frames for multiple objects at once,
without having to playback the animation multiple times.
|
|
Avoids having to set the scene's active object first.
|
|
To be backported.
|
|
|
|
|
|
In preparation for it being removed, see: T47811
|
|
Tooltip was wrong here, it can only bake a single (active) object, 'only selected' option
is for pose bones only...
|
|
invalid Python code/paths
The problem is that node trees (such as the Material, Lamp, and Compositor node trees)
are stored as "nested node trees" on the affected datablocks. They are particularly
troublesome to deal with, as the are not easily identified, and also cannot be easily
mapped back to the ID's which actually own them. As a result, the usual automated
methods do not work when dealing with these!
|
|
|
|
one.
This is needed when you want to bake only part of an armature's bones, since they
all share a single action, otherwise you'd lose non-baked bones' animation...
|
|
|
|
Since 1c3f2354f83b3e79dee31d837ca4d7c08d2c3f26 the keyframing settings on
Keying Sets have been incorrectly displayed as a clump of toggle buttons,
which are usually only used when only one of the options apply.
Reverting this back to how it was, while leaving bl_options in place still for
the one case where it makes sense to do it that way (i.e. for KeyingSetInfo)
|
|
|
|
|
|
|
|
|
|
Edit existing animsys_refactor module to make able to execute more complex conversions
('to' can now be a callback, instead of a simple prop name), and add a new
Update Animated Transform Constraints operator that uses it to handle complex
conversion for this constraint (drived or animated properties).
Note this operator has to be called manually (from 'space' menu), will make this clear
in release notes.
Also, similar changes made in 2.70 are *not* addressed by this script (would rather wrote
new operators as/if need arise, but Transform constraint looks much more sensible that the others).
This op should not remain in more than two or three releases anyway, imho.
|
|
|
|
* Remove "FCurve/Driver Version fix" from help menu, was used for RNA changes during 2.5x.
* Keep utility code in animsys_refactor.py, might still become useful according to Joshua.
|
|
there are cases where you want to use visual-keying but not remove constraints, also it wasnt obvious that clearing constraints used a different method of keyframing.
So split these into 2 options.
|
|
|
|
in fact this is more feature request.
add an option to bake a parented objects animation, then clear the parent and apply the action.
|
|
bake_action tries to make kind of a 'visual keying'... On one side, this is rather stupid when you keep constraints (in this case, keying actual loc/rot/scale transforms, i.e. matrix_basis, is enough, doing more would lead to unexpected behavior with some constraints). On the other one, making a good visual keying of bones is *really* tricky, so now using the new object's convert_space() func to compute that (when the user chooses to remove the constraints).
Incidentally, this greatly simplifies the code of bake_action!
|
|
|
|
|
|
|
|
|
|
*Add a new idname to keyingsets, keeping name as label-only (using same string for both made lookup fail when using i18n other than english, as it tried to compare an untranslated static string id against a translated RNA name). Also adding a description string (can be helpful with custom keyingsets, imho).
*Fixed a few other bugs related to that area (namely, you can’t deselect current keyingset from the shift-ctrl-alt-I popup menu, and insert/delete key ops were using a rather strange way to get chosen custom keyingset…).
*Fixed UI code so that it always uses (RNA) enum, and simplified menu-creation code.
|
|
anywhere in the UI.
|
|
and add makefile target `check_spelling`
|
|
checking if the collection is True is faster since it only checks if it has at least one item, rather then going over all items.
|
|
would give errors.
|
|
|
|
|
|
- move the data into animsys_refactor.py module so its not loaded on blender start.
|
|
bpy_extras.anim_utils and bake operator into bl_operators/anim.py
|
|
|
|
* Moved Operators from bl_ui into bl_operators.
* Renamed HELP_OT_operator_cheat_sheet to WM_OT_operator_cheat_sheet.
|
