Age | Commit message (Collapse) | Author |
|
Fixed Mix nodes in Animation Tree Player
|
|
Done with `autopep8 --select=E2,W2`, fixes:
- E201 - Remove extraneous whitespace.
- E202 - Remove extraneous whitespace.
- E203 - Remove extraneous whitespace.
- E211 - Remove extraneous whitespace.
- E221 - Fix extraneous whitespace around keywords.
- E222 - Fix extraneous whitespace around keywords.
- E223 - Fix extraneous whitespace around keywords.
- E224 - Remove extraneous whitespace around operator.
- E225 - Fix missing whitespace around operator.
- E226 - Fix missing whitespace around operator.
- E227 - Fix missing whitespace around operator.
- E228 - Fix missing whitespace around operator.
- E231 - Add missing whitespace.
- E231 - Fix various deprecated code (via lib2to3).
- E241 - Fix extraneous whitespace around keywords.
- E242 - Remove extraneous whitespace around operator.
- E251 - Remove whitespace around parameter '=' sign.
- E261 - Fix spacing after comment hash.
- E262 - Fix spacing after comment hash.
- E265 - Format block comments.
- E271 - Fix extraneous whitespace around keywords.
- E272 - Fix extraneous whitespace around keywords.
- E273 - Fix extraneous whitespace around keywords.
- E274 - Fix extraneous whitespace around keywords.
- W291 - Remove trailing whitespace.
- W293 - Remove trailing whitespace.
|
|
|
|
|
|
Also switch existing shebangs to "better" /usr/bin/env python.
|
|
|
|
|
|
AnimationTreePlayer filters improved
|
|
This reverts commits 8884b8f51963553dd1ecc0bc4accf64deb4f645f
bd5c8f2aa086c2cacc704dfef249c124760ab569
and 5cb31f6d5b667a551092b699de6f4786e0bb5b6d.
<reduz> Akien, I understand the need for the second loop mode, but I think
the current UI is pretty confusing. I think this should be changed for an
enum, both there and in the animation.. otherwise we should revert it
[...]
<reduz> alternatively this could be added per track, which I think should
make it a little less confusing
Reopens #959..
|
|
Now the AnimationTreePlayer filters for Blend2 and OneShot nodes
behave as expected, that is the main animation is not affected by
the secondary animation if the track is filterd out for arbitarily
complex trees.
|
|
Some compilers do not like this.
|
|
Added toggle for loop interpolation based on adolson's code
|
|
such as playing a sample, an animation, etc.
-Better interpolation of discrete tracks, fixes #4417
|
|
Part of #5272
|
|
Also removes a couple wrong Godot headers from third-party source files.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
AnimationTreePlayer: fix discrete value tracks.
|
|
Discrete value tracks don't update every frame (only when a new key is
reached). So we can't use the actual property value as an accumulator:
it will end up being zero most of the time.
|
|
AnimationTreePlayer: allow animating resource properties.
|
|
AnimationTreePlayer: constructor now sets processing mode.
|
|
e.g. Particles2D config and param values.
|
|
|
|
AnimationTreePlayer: Various processing improvements
|
|
|
|
copy-paste duplication.
|
|
start.
|
|
|
|
|
|
tsn->seek_pos.
|
|
The _process_node function (which recurses through the blend tree
generating blend values and the active animation list) had an argument
named `switched` which would loop an animation back to the beginning if
it had reached the end (regardless of whether or not it was supposed to
be a looping animation).
This argument was only used in four places: two of them were overridden
by a seek-to-zero, and I believe the other two are bugs.
In OneShot, it was used to reset the oneshot animation to the beginning
when fired. But this would fail if the oneshot node was fired before it
had completed its previous run. While this *could* be a valid way for
oneshot to work (firing does nothing if it's already running), the code
currently resets the fade-in, so I believe that it is intended to reset.
I replaced this usage with seek-to-0.
In Transition, it was used on the previous (fading out) animation when
seeking the Transition node, which I believe is incorrect: why would you
want to loop a non-looping animation instead of simply fading out from
the end? Also it will never happen unless you seek the Transition node
twice during one cross-fade.
The other two uses are in Transition and _process_animation, where it is
used along with a seek-to-zero which overrides it.
|
|
TimeScale node: scale return value (time remaining).
|
|
|
|
|
|
If the node had a 3D Transform, the transform would always get written,
even if the tracks on that node were supposed to be value tracks.
|
|
|
|
AnimationTreePlayer (Blend3): process all inputs.
|
|
Variant:
- zero() sets a Variant to the appropriate type of zero value
- blend() blends part of one Variant on top of another.
|
|
Always call _process_node on all three inputs so that looped animations
don't get out of sync.
|
|
-Fixed sample import plugin, makes samples sound strange in smp when limited hz
|
|
|
|
|
|
|
|
When AnimationTreePlayer switches to new animation it never
seeks it to 0 which leads to problems with non-looping animations being
played just once.
This patch is direct approach fixing this problem.
It handles most common cases of occurance.
Closes #2199
|
|
unresolved
-Added a tool to clean up unresolved tracks and unused keys
|