Geoff Bailey

In general, as long as color management is set up correctly, you only need to properly interpret your textures when you bring them in.

In your material, in whatever texture node you are using there should be an option to set the source colorspace. The "automatic" default usually does a decent job, but you'll want to set it accordingly. Assuming you're bringing in sRGB images, set it to sRGB - texture or whatever your source color space is.

There's also an "ocio colorspace transform" node if you want to explicitly do the conversion in a dedicated node. Generally you'll br converting sRGB textures to ACEScg, but that really depends on how you've set up your color pipeline.

From what I can tell from the Chicken rig, Walter is using a basic 2-bone IK to drive the hip-knee-ankle portion of the leg and then driving the ankle_ctrl with a parenting / lookat setup based on the ball_ctrl. So the ball_ctrl drives the ankle_ctrl, which is the target of a basic 2-bone IK.

Like a lot of things in the APEX beta, it will work, but it's a bit of a workaround. There are other rigging set-ups that require 3-bone spring IK setups that are more elegant and produce more natural results. Which is why I was asking, but thanks for the responses. Looking forward to future releases.

Been diving into APEX, however, most of my rigging tends to be quadruped rigging and I've hit a bit of a wall.

Haven't had as much time as I would like to expllre, but some cursory experiments seem to show that currently neither the auto-rig components nor the APEX IK solvers can handle 3-bone IK. Anyone found any way to do quadruped rigging with the current APEX nodes?

Or have suggestions about how to build a spring solver from scratch? I'd be willing to put the time in to crafting it from scratch if I understood the underlying math better. Any help would be appreciated.