>>84130758>>84130501I can only speak from my own perspective on this, but I do not believe that getting deep into rendering and what different renderers do/can't do is a bad idea if you're new to this.
Once you get into rendering things like (relatively) complicated Volumetrics, lighting that's more than a single lamp, Subsurface scattering and caustics, portals, particles, CUDA and other shit (CUDA was a bitch once upon a time) etc, then maybe you should consider your rendering options, but bogging yourself down with other renderers is a bad idea when you don't even have an understanding of your standard renderer, Cycles. I've fallen into this trap myself when I began using Photoshop and After Effects years ago with their tremendous amount of fantastic plugins. Long story short, I ended up wasting about 2 months with plugins and other shit, but I still didn't know how to do the standard procedures in either software. After I knew what the hell I was doing, and needed things like Element 3D or whatever plugins would be beneficial for the project, I used them. So to save yourself from that, I would recommend having a decent understanding of your vanilla Blender options before making drastic switches.
>>84130873There's no keyframe between the Warrior 2 position and the Warrior 1 position, so the interpolation takes the shortest route through the head, rather than the to-be-animated route around the body.
