The VMC output from SlimeVR Server has an issue with the foot bone locations being offset forward by some amount

This issue does not manifest in many VMC receivers, as they disregard this received local bone location and instead drive the VMC pose via the rotations alone (with the exception of Root and Hips which need the entire transform for proper root motion and hips placement)

For VMC receivers which consume the entire transform and apply it to the pose of the receiving skeleton (including the location data) will experience this issue, see below examples:

VMC4UE implementation also experiences crushed fingers and toes as it does not mask out received identity transforms, this would be resolved by sending reference pose transforms for the bones, or possibly not sending those bones at all, but I digress:

All other bones appear to be just fine, it is only the foot bones that experience this issue

Adjusting the Body Proportions in SlimeVR appear to make no difference to the VMC pose output, however I don't have a set of trackers yet, whether this behavior changes when actually tracking I am unsure