The HeadChop feature has stopped considering the original scale of specified objects, instead forcing them to an equivalent of Scale 1.0. This is causing visual glitches in the local player's view (PlayerLocal). For example, when the Armature scale is set to 0.01, objects parented under the Head typically have a scale of 100. Previously, HeadChop accounted for this, but it now ignores the parent scale and forces the object to a scale of 1, resulting in an incorrect display size. This issue appeared suddenly within the last 1–2 months. Since the problem persists even after downgrading the SDK to version 3.9.0, it is likely not an SDK-specific bug but rather a result of a change in server-side processing or the build pipeline. Furthermore, avatars uploaded prior to this period continue to function correctly; the issue only affects newly uploaded content. (Note: The behavior remains normal when tested in Unity using Av3Emu.) Example: ・Armature Scale: 0.01 ・Target Object (under Head): Scale 100 (with HeadChop ScaleFactor set to 1) Expected Behavior: The Object Scale should effectively be 1,000,000 (maintaining the visual equivalent of Scale 1 in world space). Actual Behavior: The Object Scale becomes 10,000 (resulting in a visual equivalent of Scale 0.01 in world space).