Uploaded image for project: 'Minecraft (Bedrock codebase)'
  1. Minecraft (Bedrock codebase)
  2. MCPE-85756

Keyboard-only input lag since Nether update

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • None
    • 1.18.0.21 Beta, 1.17.30.24 Beta, 1.17.30.21 Beta, 1.17.30.20 Beta, 1.17.11 Hotfix, 1.17.10, 1.16.0, 1.16.1, 1.16.10, 1.16.20, 1.16.201 Hotfix, 1.16.221 Hotfix, 1.17.30, 1.17.34, 1.17.40, 1.17.41 Hotfix, 1.18.2 Hotfix, 1.18.30, 1.18.31, 1.19.0, 1.19.51, 1.20.32 Hotfix, 1.20.41 Hotfix, 1.20.81 Hotfix, 1.21.0, 1.21.1 Hotfix, 1.21.22 Hotfix, 1.21.23 Hotfix, 1.21.44 Hotfix
    • None
    • Community Consensus
    • Windows
    • 379418

      I haven't seen anyone on YouTube or elsewhere that's mentioned this issue which led me to believe it may have been an issue with my keyboard, but after more tests on other games, I isolated it ONLY to Minecraft Bedrock after I updated to 1.16.

      For the first few moments I'm loaded into the world, the game doesn't accept any input from my keyboard at all. Once it begins accepting input, it often doesn't register that I'm not still pressing a key, leading me to walking straight in one direction... sometimes off cliffs. As well as that, it'll miss many keystrokes and sometimes even repeat what it did in the beginning. This has never been an issue before and it makes the game totally unplayable, especially in a world filled with oceans of lava. I've heard that there is no such issue on Java edition, but I simply don't have a system capable of running it decently at all.

      As for troubleshooting, aside from testing in other games, I've reinstalled the drivers for both my wireless mouse and keyboard and clean installed Minecraft, then loading into a fresh world. I thought it may have been an issue with the game becoming more demanding, so I gave it high priority in the system. None of this eliminated the issue.

      Update (6/25, edited 6/28): Based on further research and independent testing, I've concluded it is likely a chunk rendering issue. The issue doesn't exist after creating a "Flat" OR "Old" type world as long as you remain in the overworld. The idea is that the "Old" world type only generates a set amount of blocks and doesn't continue while the "Flat" world type has no complexity in its generation. On some high performance computers, lowering render distance may remedy the situation in an "Infinite" (default) type world and, on others, this issue may not exist at all.

      Videos from MCPE-85450:
      https://youtu.be/pTaXhdwK0nI
      https://youtu.be/cwAYn06u46s

            jirauser512550 user-7e445 (Inactive)
            Votes:
            89 Vote for this issue
            Watchers:
            45 Start watching this issue

              Created:
              Updated:
              CHK: