mojira.dev

_Kastle

Assigned

No issues.

Reported

MCPE-219641 Bamboo does not have the same offset as Java despite the 1.21.80 changelog claiming so Unconfirmed MC-265986 Area Effect Cloud particles do not render if it is spawned more than 32 blocks away from player Community Consensus MCPE-160073 Top Face UV of Blocks Renders Mirrored on Y Axis When Per-Face UV Is Used Cannot Reproduce MCPE-133833 Directory Names Cannot Overlap Default Textures If Resource Pack Remains Compressed Incomplete MCPE-123305 Blocks With Custom Geometry Render Incorrectly in Inventory Confirmed MCPE-116432 Custom Block Geometry Does Not Respect Element Pivots Fixed MC-187292 Resource Pack Does Not Replace mojangstudios.png Duplicate

Comments

Further screenshot to illustrate that offsets changed between 1.21.70 and 1.21,80, but do not match Java, and is not affected by seed.

Java Edition (1.21.5, Seed = 1):

[media]

Bedrock (1.21.80, Seed = 1):

[media]

Bedrock (1.21.80, Seed = 2)

[media]

Bedrock (1.21.70, Seed = 1):

[media]

Bedrock (1.21.70, Seed = 2):

[media]

[media][media]

Can confirm this issue has been fixed.

Resolved in current version.

I would like to add here that https://wiki.bedrock.dev/blocks/block-shapes.html#known-issues describes a workaround in which blocks.json is placed in a separate pack. Perhaps the fact that this works will help to isolate the issue.

I would also like to add that this limitation even breaks the use of Mojang's own geometries in a custom block definition... even tiny things like geometry.player_head since they often have a pivot or one point that trails over the line. So this limitation... if it is truly about performance... makes very little sense if Mojang's own vanilla resources routinely violate it.

@Paul Ellsworth the pack does not fix the issue because of the min engine version. It is because it uses a marketplace pack's uuid which has been whitelisted to have the engine version locked. Normal creators do not have access to this. So setting your pack to the same uuid as the linked pack will fix the issue regardless of min engine version, and setting min engine version will not fix the issue.

I would like to note that this seems to be an issue not of materials, but of the client doing something funny with the skin images themselves. We'd expect switching the top layer of the player model to entity_alphablend to solve this, as that should pick up the translucency data on the skin, if there is any. However, this is not the case.

It is also not an issue of the player material being hardcoded, as using something distinct like charged_creeper shows a clear change. So if Mojang is investigating this I think the issue is somewhere in the skin pipeline or a shader issue specific to the player entity, not a materials issue.

MCPE-139667 no longer blocks as its been resolved. This is still an issue in release as well as beta. Ticket was updated to requested format.

I am able to reproduce myself as well. Please ensure you are enabling holiday creator features and both the behavior and resource pack of the addon.

Still an issue in 1.16.210 release and subsequent 220 betas, as well as using the new 1.16.0 geometry format.

The issue that the bot has linked as duplicate is from a snapshot in 2013 for 1.7