mojira.dev
MCPE-235822

Foxes hold items at an incorrect scale and offset

When a fox holds an item, the item is rendered significantly smaller than intended. Furthermore, the item’s offset is misaligned, causing it to be buried inside the fox's body model under default conditions. The item only becomes visible at a reasonable size if the fox is scaled up during certain animations. Currently, the item is invisible unless the fox model is made transparent.

Attachments

Comments 6

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.

E3B0465F4D0A9397703991436410A13E.jpg
FCEBAAEC2345FB64852EE62BD4D00E99.jpg

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.

Why are the authorities always keen on restricting the basic conditions for creating diverse gameplay for players of the Bedrock version? I don't believe the official doesn't know the importance of FMBE for Bedrock players, let alone how much impact his changes to physical models will have on FMBE and even the mod ecology of Bedrock (the mod ecology of Bedrock is already bad enough)

Vote option is located at the bottom left of the page

Yes, I noticed that foxes hold items over them

Gaagaa

(Unassigned)

1554101

Confirmed

Windows

Windows 11 Home / 25H2

26.10.21 Preview

Retrieved