Is there any way to do a motion guide currently?
For example, if I want to animate a ball bouncing, I'm not sure what the best way to do this is without being able to draw a path the ball moves along.
Motion guide
- Modifié
Yeah.. that would be a major plus.
You could import an image to use as a guide. Check "background" so the guide image cannot be selected.
Yeah, but that's not very smooth because you need to put in a ton of keyframes for a basic curve. Sometimes I can get the effect I want by making a parent bone ease one way and the child bone ease another, but this setup isn't always ideal.
Oh, you want a path that objects follow. That is planned and on the Trello board.
Do you mean motion paths / Bezier curves?
I really need that feature.
Just out of curiosity: what things are you animating that need this feature?
Nate, you are my 5th favorite person in the whole world, I just wanted you to know that.
I would correct that question: What things are You animating without motion paths? 
Motion paths counts as essencial in animation. When You sketch up a motion on paper, you basically start with a line that is the path of the motion and those are rarely straight lines.
They built Spine primarily as a skeleton animation system, meaning rotations would be your primary transform to animate while it takes care of all the position inheritance based on rotations. (I know you base your argument on classical animation. But these aren't straight lines.)
Personally, I'd like a few more features on it for it to have good 2D flexibility that other proprietary systems have had for years, 'cause it can't rely on just rotations since this isn't 3D. A lot of things need to be "cheated", or really, redrawn and replaced temporarily. To really look good, a setup that gracefully supports a nice mix of skeletal and frame-by-frame and FFD animation would be my ideal.
What I did to describe the need (and hopefully clarify possible solutions) was to describe what things I need to animate.
Given that almost everyone wants to do other things with Spine too, I'm interested in what non-skeletal things people are animating that need motion paths.
:-) I want Spine to replace everything I previously used the Flash IDE for. Although it's ok if I need a separate tool to draw the graphics as long as the workflow is smooth (which it is).
I've been using LibGDX to make my game for a few months now, and to describe what "All the things" are, I need to describe where the rough spots are in my workflow.
I chose LibGDX over Unity because I like the runtime better, I prefer how light-weight it is, my game is 2d (Unity2d is newish), and I prefer the workflow of IntelliJ/Java over Unity/C# (or VS).
However, Unity tooling is pretty awesome for configuration. You can use the Unity editor to setup your level, configure everything visually, and even write editor extensions. This is something I feel like I'm missing with LibGDX.
Spine is a skeletal animation tool, and as far as that goes, it's the best I've seen. I would just love to see the same style of lightweight tooling around frame animation, and tooling around visually setting up and configuring my components. Adobe has made several crappy attempts at this: Flash Component inspector, Flex Design view, Adobe Catalyst. Unity is tied to the Unity runtime, but I might play around with it to see if I can write my own exporters.
Motion paths are used in character animation a lot. For example, setting a motion path for an IK (constraint/controller/etc) is very useful. Imagine that the hand of a character has to rotate a wheel or something. The hand has a perfectly circular motion that could be done with only a few keyframes..
5 jours plus tard
Pharan a écritJust out of curiosity: what things are you animating that need this feature?
Anything that needs to move in a curved trajectory needs motion paths. For example a character that jumps from one place to another. Also, all ellipse movements need motion paths.
hydrip a écritPharan a écritJust out of curiosity: what things are you animating that need this feature?
Anything that needs to move in a curved trajectory needs motion paths. For example a character that jumps from one place to another. Also, all ellipse movements need motion paths.
I guess for me I don't use motion paths anymore... or at least I don't need them in the BG of anything. If you use them often enough you just start doing it right the first time. Also theres nothing stopping anyone from just dropping something in the background and checking the Background option to prevent it from exporting.