MCPE-186491Entity geometry rotation is ignored when merging identical skeletal structures
Summary
Data-driven entities support the conditional rendering of geometries through render controllers, either through using ternary expressions or indexing into an array. If two geometries share the exact same skeletal structure—with each bone of the same name parented the same way and sharing the same pivot—the rotation property is ignored. It appears to depend on which geometry was loaded first.
Steps to reproduce:
The attached add-on contains one entity with two possible states: a default state and a "rotated" state. One has a cube positioned high, the other low and rotated; they otherwise share the same skeleton and pivots.
- Download the attached add-on and apply it to your world.
- Summon in the entity "mcpe:model". /summon mcpe:model <location: xyz> 0 0
- Summon in another of that entity, with the "rotated" variant set: /summon mcpe:model <location: xyz> 0 0 mcpe:rotated
Observed result:
The default entity (brick placed low) is facing the south side of the model. The "rotated" variant (stone brick placed high) is also facing the south side.
Expected result:
For the "rotated" variant to face the west side, as defined in its model.
Created Issue:
Entity geometry rotation is ignored when merging identical skeletal structures
Summary
Data-driven entities support the conditional rendering of geometries through render controllers, either through using ternary expressions or indexing into an array. If two geometries share the exact same skeletal structure—with each bone of the same name parented the same way and sharing the same pivot—the rotation property is ignored. It appears to depend on which geometry was loaded first.
Steps to reproduce:
The attached add-on contains one entity with two possible states: a default state and a "rotated" state. One has a cube positioned high, the other low and rotated; they otherwise share the same skeleton and pivots.
- Download the attached add-on and apply it to your world.
- Summon in the entity "mcpe:model". /summon mcpe:model <location: xyz> 0 0
- Summon in another of that entity, with the "rotated" variant set: /summon mcpe:model <location: xyz> 0 0 mcpe:rotated
Observed result:
The default entity (brick placed low) is facing the south side of the model. The "rotated" variant (stone brick placed high) is also facing the south side.
Expected result:
For the "rotated" variant to face the west side, as defined in its model.
Attachments2
![[Mod] Jarl-Penguin](../../../data/avatars/users/92849.png){kind=small}
![[MCQA] Emir Misiratov](../../../data/avatars/users/18935.svg){kind=small}
Can confirm, affects preview 1.21.40.20.
I could confirm in Android.