When using the old touch control, player cannot sneak at all even after spamming the sneak button. This only occurs to certain device which got higher refresh rate since this bug doesn't affect my Redmi 9 (60 fps), but it does affect my Poco X3 Pro (120 fps).
There is a way to "fix" this bug and also a way to "replicate" this bug (only if you have a mobile device that has 120 refresh rate or higher).
[media]
To replicate this bug:
1. Have 120 or higher refresh rate.
2. Go to options.txt and make sure (gfx_max_framerate=0).
Alternative:
1. Apply any resource pack that added frame rate slider.
2. Make sure the frame rate is set to at least 120 or above (default is unlimited).
[media]
To fix this bug:
1. Go to options.txt
2. Change the gfx_max_framerate to at most 110 (Ex: gfx_max_framerate=110).
Alternative:
1. Apply any resource pack that added frame rate slider.
2. Change the frame rate to at least 110 or below.
Linked issues
is duplicated by 2
Attachments
Comments 6
The device I'm using is Poco X3 Pro (6GB RAM, 128GB ROM, Snapdragon 860). I did change some settings.
Sensitivity: 30
Button Size: 100
Destroy Block (vibrate): off
This however doesn't effect the sneak button for the new touch control, only the classic control.
I also tried to replicate this bug on Redmi 9, but the control there seems responsive. So this bug probably only affecting certain device like the Poco X3 Pro.
It also happen to me, sometimes I can only sneak in a certain direction, sometimes I cannot sneak at all..this happen whether I'm using resource pack or not..
But whenever I tried to record it with my screen recorder everything's back to normal, I can sneak again. But after a few minutes after I closed my screen recorder I can no longer sneak anymore. I should always open my screen recorder, record it for 1 or 2 seconds, pause it, and keep it open for the entire gameplay, that is my alternative solution for this problem, at least for now..
My device is Realme GT Neo 2, android 11
I could not reproduce on my Redmi Note 7. You haven't updated the bug since July, is this still reproducible?
Sorry, it took me a awhile to know what causes this bug, and after playing around with the setting, I found out that the frame rate limiter is the one that causes the bug.
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response.
What device are you experiencing this on? Did you change anything in Settings > Touch?
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📓 Project Summary – 📧 Suggestions – 📖 Minecraft Wiki