You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 13, 2021. It is now read-only.
I was watching one of Deadbones' [recent streams], and I started to think his puppet's animations looked off, since they're so close to the ones in Babble Buds, but not quite right. Obviously I've been staring at these animations in my own program nonstop during development, so they look good to me, but to someone used to Puppet Pals, the animations in Babble Buds are going to be the ones that look off. It's kind of an uncanny valley type situation: the animations should be changed to either look exactly like the ones in Puppet Pals (no easy feat), or intentionally change further so the two programs look stylistically different.
Or maybe its fine as it is now. This ticket is fairly low priority, and whether or not I'll work on it will be largely based on user feedback.
The text was updated successfully, but these errors were encountered:
thepaperpilot
changed the title
[BUG] Move and Deadbones-style Talking Animations Not Quite Right
Move and Deadbones-style Talking Animations Not Quite Right
Jul 18, 2017
I was watching one of Deadbones' [recent streams], and I started to think his puppet's animations looked off, since they're so close to the ones in Babble Buds, but not quite right. Obviously I've been staring at these animations in my own program nonstop during development, so they look good to me, but to someone used to Puppet Pals, the animations in Babble Buds are going to be the ones that look off. It's kind of an uncanny valley type situation: the animations should be changed to either look exactly like the ones in Puppet Pals (no easy feat), or intentionally change further so the two programs look stylistically different.
Or maybe its fine as it is now. This ticket is fairly low priority, and whether or not I'll work on it will be largely based on user feedback.
The text was updated successfully, but these errors were encountered: