Why a virtual body may stop at the waist
In many virtual-reality setups, the system directly tracks only a few points: the headset and the hand controllers. Those give a good read on where a person is looking and reaching, but not where their hips, knees, or feet are. Without extra body trackers, the avatar’s lower half has to be estimated from the movements the system can see.
That estimate is a problem of inverse kinematics: working backward from known points to calculate a plausible pose for the joints between them. The system can guess how legs might bend, but it cannot reliably know whether a player is sitting, crouching, stepping in place, or simply shifting their weight. A plausible guess can quickly look wrong when it meets the virtual floor.
The cost of getting feet wrong
Feet are especially revealing because they are expected to stay planted during a step. If an avatar’s foot moves while it should be supporting the body, the foot appears to slide across the floor. If the software holds it still, the legs may bend or swing in ways that do not match the player. Either mismatch can make the avatar feel less like a body and more like a faulty puppet.
Adding trackers to the waist and feet can give the system more information, but it also means extra equipment and setup. Omitting the legs is a simpler design choice: it avoids displaying a confident-looking pose that the software cannot support. The tradeoff is visible—the avatar seems to float—but its tracked head and hands can still express where the player is looking and what they are doing.
