News for hackers. Stuff that matters.
Re:Game Engine: How I Implemented Skeletal Animation by bsenftner on Sunday April 04, 2021 @07:54AM (#26688730)
Squash and stretch is not implemented with scaling. In fact, for any rational animation system (meaning one that a non-engineer digital artist can actually use) the use of scaling is simply not available in the system. Scaling in a hierarchical animation system is a guaranteed method to fuck up an untold large number of additional systems such as the physics/dynamics associated with the scaled character as well as any geometry attached to the character, as well as any sub-systems which use the now-scaled character for decision triggers. There are simply too many inter-dependent systems that rely on aspects of the environment, such as the scale of objects, to remain consistent for the entire illusion of a consistent world to be maintained.

Speaking from experience: I've written dozens of 3D animation systems for games and film VFX. I've been writing 3D animation systems since the 80's.

Re:Game Engine: How I Implemented Skeletal Animation by gfxgirl on Sunday April 04, 2021 @10:06AM (#26689479)
So have I. I can assure you there is scaling in every game and VFX I've worked on since the late 90s
Re:Game Engine: How I Implemented Skeletal Animation by bsenftner on Sunday April 04, 2021 @05:45PM (#26693108)
You may have scaling in your tools, but under the hood the transformation pipeline treats the result as a translation. Scales cause physics and dynamics issues, which are linked to too many related systems. That's why tools that scale have a "bake" operation afterwards, that baking is transforming scales into translations so runtime and scene logic can use a uniform coordinate space.
Re:Game Engine: How I Implemented Skeletal Animation by gfxgirl on Monday April 05, 2021 @10:46PM (#26707445)
Not my experience. Have shipped several AAA games with scaling, no baking.