MCPM_SX

Update: Technical Root Cause Analysis

Following further community investigation, we have identified why this issue occurs globally even if the Adult Fox geometry remains partially unchanged:

1. Renderer Migration: In Preview 26.10, the Adult Fox has been migrated to a new renderer. This new pipeline appears to handle attachment points differently, potentially disregarding traditional animation-driven offsets.

2. Structural Inconsistency (Baby Fox): The baby_fox.geo.json has switched held_item from a Locator to a Bone, and changed its parentage to root.

3. Conflict: This mix of a "New Renderer" and "Bone-based attachment" creates a regression where item scaling and positioning (FMBE techniques) no longer function as they did in v1.26.0.

Requested Action: Please ensure the new renderer maintains parity with old Locator-based offsets and revert the Baby Fox's held_item to a Locator to restore technical stability for creators.

Headline: Root cause found in geometry JSON hierarchy

I have investigated the geometry files and found the technical reason for this regression. In the previous versions and the current adult fox (fox.geo.json), held_item is a Locator attached to the head.

However, in the new baby_fox.geo.json, held_item has been changed to a Bone.

Why this matters:

• Scaling: As a bone, it now inherits the head's scale and parent transforms, which explains why the item is rendered at an incorrect, tiny scale.

• Hierarchy: The head's parent is now root instead of the traditional body hierarchy, further breaking transform calculations.

This change breaks visual parity and long-standing community technical techniques. Please consider reverting held_item to a Locator.