Block visibility update delay
The issue:
When placing a block, the hitbox (collision box) appears first then the block texture itself with a slight delay or time difference between the two. It happens regardless of the performance or the number of frame rates per second.
The expected behavior:
Both the block and the hotbox appear (or render) at the same time, and both disappear at the same time as well.
Linked Issues
is duplicated by3
Created Issue:
Block delay still hasn't been fixed
Block delay still happens, and I can clearly see the hit box outline selection of the block before the block appear it self, it can be clearly seen when placing a line of block in normal flying speed.
Not just in Windows 10, even in the Xbox one, and mobile of course.
Block delay still happens, and I can clearly see the hit box outline selection of the block before the block appears it self, it can be clearly seen when placing a line of block in normal flying speed.
Not just in Windows 10, even in the Xbox one, and mobile of course.
Block delay still happens, and I can clearly see the hit box outline selection of the block before the block appears it self, it can be clearly seen when placing a line of blocks in normal flying speed.
Not just in Windows 10, even in the Xbox one, and mobile of course.
Block delay still hasn't been fixedVisible lag when placing blocks
Block delay still happens, and I can clearly seethe hitboxoutline selection of the block beforethe blockappearsitself, it can be clearly seen when placing a line of blocks in normal flying speed.
Notjust in Windows 10, even in the Xbox one, and mobile of course.The issue:
When placing a block, the hitbox (collision box) appears first then the block texture itself with a slight delay or time difference between the two. It happens regardless of the performance or the number of frame rates per second.
The expected behavior:
Both the block and the hotbox appear (or render) at the same time, and both disappear at the same time as well.
Visiblelag when placing blocksVisible block visibility update delay
Visible block visibility update delayBlock visibility update delay
relates to
Affects 1.13.0.17 beta.
Affects 1.13.0.4 beta.
Affects 1.12.0 and 1.13.0.2 beta.
Affects 1.13.0.1.
is duplicated by
is duplicated by
is duplicated by
Thank you for your report!
We're actually already tracking this issue at MCPE-33749, so I will resolve and link this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCPE-59935 and MCPE-33749, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main tickets it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCPE-33749 and MCPE-59935, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main tickets it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
From further testing, I can conclude that in Java Edition, activation is instantaneous (even with /tick freeze, placing the top log will immediately update the heart), and deactivation depends on a random timer kept internally by the block entity which is difficult to observe, but ranges from 0 to 25 ticks.
In Bedrock, the heart seems to reliably take 3 ticks to change states when a log is placed or removed. Like many delayed block interactions in Bedrock (MCPE-33749, MCPE-59935, MCPE-71925), this lack of responsiveness is distracting and makes the game feel laggy.
Is it a an usual amount of time? Like over a second or 2?
No, it's always there. Like all the time.
My Device is a low - end one, but this issue wasn't there before the 1.2.0 update.
I was asking about the Delay time.
Less than a second, but it still obvious especially when placing a lot of blocks.
Still affects 1.6.0.6. An easy way to fix this would be to delay the outline appearing a little bit when placing blocks
Still an issue in 1.11.4. It becomes even more noticeable if your framerate drops below 60 fps.
Affects 1.16 latest release.
Affects 1.16.200.53
Happens on xbox one, iOS and android too.
Does it effect versions (beta) with Renderdragon re-enabled?
Yes this still affects betas with Render Dragon enabled
Someone has commented that MCPE-59935 has been fixed in 1.18.20 beta, if I remember correctly. Since this bug is related to it, can someone confirm whether it has been fixed in that beta?
No, it hasn't been. So this bug is not related to that, unfortunately.