mojira.dev
MCPE-59935

Block breaking has several frames delay

The bug

When a block is mined, it takes about five frames to update properly, which can be somewhat distracting.

[media]

Here is a frame-by-frame analysis beginning with just before the block being broken:

Frame 0: Block is on last stage of the breaking animation. Next frame, it should break.

Frame 1: Pickaxe durability bar appears, indicating that the item was used. Block hitbox outline disappears, indicating the block is gone. The mining animation disappears. The block is still present.

Frame 2: No change.

Frame 3: Block disappears. No item is visible, breaking particles have not appeared.

Frame 4: No change.

Frame 5: Breaking particles appear.

Frame 6: Dropped item appears.

Expected behavior is for the block to disappear, and particles and items to appear all on the immediate frame after breaking the block.

Comparison

[media]

Linked issues

Attachments

Comments 10

Have also experienced this across all previous versions I've played Bedrock (1.12 onwards I think) across Win10, Xbox and Switch.

I know its weird but theres a satisfactory "pop" to mining on Java that isnt the same on Bedrock and I think this is part of it.

Block lag and the jittery movement of broken blocks also play a part

Breaking animation is inconsistent as of 1.16.200.55 on WIndows 10. The delay for the pickaxe to start mining is around 4-6 frames (it changes every time I measure it). Sometimes the particles will appear the very next frame after the block is broken (as they should) but there are also times when either a shadow or a ghost block (never both in my experience) can be seen before the particles are released. Overall there's less delay for the particles to appear, although weaker devices may have a worse delay

Delay is significantly worse in 1.16.210.56. It now takes on average 3-4 frames for particles to appear (Windows 10 singleplayer, it is worse on other platforms), and block breaking in creative is also affected.

Has been fixed in 1.18.0.20

Can you please share a video demonstrating this? I also want to know if this issue is related to repeaters with random timing and stuff.

Why was 1.18.0.21 mentioned?

I've noticed the issue has reappeared for me. It happens on and off

This is an intermittent, but frequent, issue on the Switch as well.

I have a solid connection and Minecraft is on my device and not on a card and my device has plenty of space on it as well.

If it matters any, the issue also persists regardless of joycon use - attached or detached from Switch - and regardless of alternate control use - paired via Bluetooth.

 

 

Thank you for your report!
After consideration, the issue is being closed as Won't Fix.

Please note that this is not the same as Working as Intended, as this bug report correctly describes behavior in the game that might not be the intended or desirable behavior, but it will not be fixed right now. Sometimes, this is because the issue reported is minor and/or impossible to change without large architectural changes to the code base.

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

tryashtar

(Unassigned)

445108

Community Consensus

Windows

responsiveness

1.20.0.20 Preview, 1.18.10.26 Beta, 1.18.0.21 Beta, 1.17.40.23 Beta, 1.17.40.21 Beta, ..., 1.18.31, 1.19.73, 1.21.41 Hotfix, 1.21.43 Hotfix, 1.21.50

Retrieved