mojira.dev

HAYO

Assigned

No issues.

Reported

No issues.

Comments

Version 1.21.132 has now been released, but this bug still has not been fixed.

It has been one month since the release of 1.21, and three months since this issue first appeared in October.

Leaving such a critical, gameplay-breaking bug unresolved for this long raises a serious concern

is this simply being dismissed because it only affects a portion of players, and therefore not being treated as a priority?

Downgrading Minecraft Bedrock Edition is not straightforward, and from the user side there is effectively no viable workaround.
As a result, all we can do is wait for a bug fix.

I have continued playing other games while waiting, but at this point, after being left unresolved for so long, my enthusiasm for Minecraft itself has started to fade.

I can accept update-related nerfs when they are justified as balance adjustments.

However, instability and control issues introduced by an update are by far the most frustrating outcome possible.

It is deeply disappointing to see Minecraft reduced to what feels like a broken, poorly functioning game.

When enabling full keyboard control, camera movement using the keyboard is completely smooth, with no stuttering at all.
From this, it can be reasonably inferred that the issue is related to mouse input.

However, it does not appear to be caused by the mouse alone.
The behavior suggests that whenever some kind of loading occurs, mouse input polling intermittently drops, resulting in camera stuttering.

This can be observed when creating a new world and loading chunks, and it becomes especially noticeable in environments such as a trading hall with nearly 100 villagers.
This behavior did not occur in the UWP version and started after the GDK transition.

For over a week since version 1.21.130, I have attempted the following without success:
•Reinstalling Minecraft itself, Xbox App, and Gaming Services
•Toggling VSync, mouse polling rate, and low-latency input modes
•Testing various system and in-game input-related settings

None of these attempts resolved the issue.

At this point, I suspect that something related to GameInput or the GDK-based Gaming Services input pipeline may be involved.
Unfortunately, there does not seem to be any viable user-side workaround, which makes waiting for an official fix quite discouraging.

Is the expectation that affected users simply cannot play the game properly until next year???