rat

As I have already told you about this issue…

This is an expected response. I understand clearly that Mojang doesn’t like duplicate reports. But that only makes sense to be bannable in certain contexts. I think making a duplicate issue after you failed to update the current ones version (Aka, your job). Fail to give any update. Fail to tell us you are going to prioritize this. Mojang failing to have fixed this after 3 months of people stating this and giving information about a game breaking bug is much worse than creating a duplicate report. Making a duplicate report is much better 😀 . Also it would be nice to not be banned, so people who bought the game can report bugs- which is intelligent. Maybe give me a break instead of Mojang, who didn’t fix something for three months. Making the game unplayable. Sorry, a duplicate report is too far.

Here is the friendlier one.

I understand the policy regarding duplicate reports, and I’m not trying to ignore it.

However, from a user perspective, the frustration comes from the fact that this issue has been reported repeatedly for months, with substantial technical detail, votes, and confirmations — yet there has been no visible update, prioritization, or acknowledgment of progress.

When an issue that makes the game effectively unplayable for mouse users remains unresolved for this long, and existing reports are not updated with status or communication, it creates the impression that the problem is being deprioritized or overlooked.

Duplicate reports are not created out of disregard for the rules, but out of a lack of feedback and visibility on critical issues. Clear updates or confirmation that the issue is actively being worked on would likely prevent most duplicates.

I’m not asking for special treatment — only for transparency and acknowledgment that this regression is known, reproducible, and being addressed.

Oops, I guess I just made a duplicate response. 😘

Thank you!

aware but doing nothing after 3 months. bunch of …….

I can’t even click in the newest version.

Still broken. Updated to the latest version. Settings perfect. Still unplayable after three months.

Exactly, just because some people don’t experience this with the same game settings and computer settings doesn't mean its not a GDK issue.

The issue is context-dependent, which doesn’t point towards an issue related to mouse software.

*..in the newest version, which is why I am playing a downgraded version*

I am still using version 1.21.114 and things are becoming very unstable, because you people have not fixed the unplayable critical bug. The game is still stuttering.

Version 1.21.130 did not resolve this issue. In single-player testing, camera movement remained choppy and laggy, almost as if it were running at a lower refresh rate. On a server, the behavior was similar; additionally, I immediately noticed that the hand animation does not play when clicking—this issue only occurred in the server, not in a normal single-player world. Overall, even in normal worlds with high FPS and a high refresh rate, camera movement still feels choppy, resembling a lower refresh rate experience.

And nobody can really find this unless it’s a dupe report.

@Alfrednalxr2 Yep. I also am at 240 Hz and my fps is high and stable. But the camera movement when moving the mouse is laggy and not smooth still. Even trying different polling rates. I can’t play unless they fix this. It’s unplayable. It ruins the game. It’s impossible to actually play like before. 19 votes on a bug report and still nothing… this thing gets at least a vote a day. Still no fix.

Thank you.

Genuinely please. I haven’t been able to play and have fun for 4 weeks. I’ve been giving so much information on this. Are you guys ignoring my comments? I actually haven’t been able to play for 4 weeks. Please do something.

Can you actually do something about it, or give any other information other than saying don’t dupe issues and then redirecting me to the older bug report you still haven’t fixed

The mouse jitter isn’t a traditional FPS or polling rate issue. The game maintains stable framerate, but the camera movement is consistently unsmooth. Its severity is context-dependent: in some areas or during chunk/entity loads (like server spawns), it becomes much worse, while in other areas it may feel smoother. The behavior is unpredictable and dynamic — the engine consistently misprocesses relative mouse input, but the severity varies depending on context. This explains why FPS counters are stable, yet camera movement feels stuttery or jumpy. It’s a persistent issue tied to the GDK rendering/input pipeline rather than hardware, V-Sync, or mouse polling. Mojang. Please. Fix. This. Issue. It. Is. Unplayable.

Never mind it’s actually very noticeable when the polling rate is above 125hz. The 125 hertz on worlds is better than servers. It feels like a dynamic polling rate cap

Yeah this only affects the mouse. From my pov: It seems to be an annoying mouse input gdk problem that seems to be a dynamic hertz issue maybe based on load. But, it shouldn’t get laggier based on load because if your hertz is 240 on your monitor and you remain at a high lets say 600 fps at least consistently the polling rate or hertz shouldn’t go lower. But somehow the quality of this game is bad so you notice a polling rate/refresh rate that is terrible. This seems to mostly affects high end systems. So it’s definitely Mojang's issue not ours. Dynamic Hertz is off and vsync is off for me and it seems like its off for everyone in this thread. For me, servers is noticeable, and worlds are not really noticeable. But it’s naturally going to be different for everyone because not everyone has the same hardware. Very annoying code issue.

It seems like it depends on load. So if you are at 125 hz you wont notice it with low load but when the load is high it even gets laggy on 125 hz even though it shouldn't be laggy for me even at 500hz its still technically a glitch. Because its excessive load and strain no matter how good your pc is. seems like a glitch.

or it al least makes the glitch less noticeable