Issues with position of character head when C+ Profile alters Abdomen Position w/ Child Transform enabled

[Lunaretic]

There seems to be an issue that seems like it may be partially an incorrect Customize+ quirk/bug, and partially a Ktisis bug.

Specifically, C+ Profiles can alter the position of the Abdomen bone with "Apply [spine] transformations to child its child bones" however, C+ for some reason does NOT properly consider the head (and its child bones) to be a child of the Abdomen, while Ktisis.. Sort of does? Or does specifically only to the Head bone, but not the facial bones.

This results in the creation of eldritch horrors when ticking on on [Posing Enabled] in Ktisis. Likewise, if the head is positioned in C+ then to account for Abdomen changes, the character's head bone moves (without facial bones), resulting in a secondary, slightly different but equally terrifying eldritch monstrosity.

Minimum Reproduction:

1. Create a C+ Profile with an Abdomen bone position edit, with propagation to child bone transforms enabled. Note the character's head does not move, but the rest of the body does.
2. Enter GPose, open Ktisis
3. Turn on Ktisis posing. Note the character's head bone moving out of place, but all other bones/features unaffected.

[sleepybnuuy]

thanks for documenting - this has been a known issue for a little bit, but the reproduction steps help make the issue very clear.

1. on head bone vs face bone movement: XIV's head bone (j_kao) is included on both the main body skeleton (which includes torso, etc) and the partial face skeleton (which includes all other face bones attached to the head, besides hair). C+ and Ktisis have likely diverged in how we handle propagating out to the face skeleton or including/excluding the head bone
2. on child propagation/transformation, this is a newer C+ feature that I've not yet found a clean fix to work around on Ktisis or Customize's code. the pose-mode toggle in Ktisis disables several XIV functions to fully freeze the actor's body for posing, but this appears to have some adverse reaction to the logic C+ uses to calculate and apply child propagation to bones in a template.

at a bare minimum, I'd like to include a warning label when a C+ profile using these propagation features is detected before entering pose-mode - an actual fix for the issue would require a bit more dev work (likely on customize's plugin) to sort out the odd conflict.