| Age | Commit message (Collapse) | Author |
|---|
|
|
|
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.
|
|
such as playing a sample, an animation, etc.
-Better interpolation of discrete tracks, fixes #4417
|
|
|
|
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
-fixed randon button when editing menubutton #1079
|
|
- Changed node_get_input_sourcre to node_get_input_source
|
|
-=-=-=-=-=-=-=-=-=-=-=-=-=-
*YOUR SOURCE MIGHT NOT WORK*
For mor information on fix:
https://github.com/okamstudio/godot/wiki/devel_scene_tree
Other stuff:
-Shower of bullets demo
-Fixes all around
|
|
|
|
|