mojira.dev
MCPE-236392

UWP to GDK mouse input - Polling rate bug

Link

Unlisted youtube video demonstration

You may be able to verify this yourself even on previews

Step 1 : In your mouse software set your polling rate to 1000hz, this has been the standard polling rate even for low end mic for years now

Step 2 : While in game you will swipe your mouse a couple inches very fast while leaving it engaged on the mousepad the entire time, you should notice there is no issue.

Now swipe a couple inches very fast then lift the mouse off the pad, the cursor may teleport.

Even if you do a tiny swipe and lift the mouse

This is a normal movement for someone trying to turn around and re-center the mouse quickly

You will notice after doing this a few times that the cursor is teleporting a little even after you lifted the mouse.

Step 3 : Change your polling to a very low 1990’s speed polling of 125hz and you’ll notice the game handles this with no stuttering

Step 4 : Test either 250hz,500hz,1000hz and you will experience stuttering, If you want to know what you are looking for visually than watch the demonstration video I linked at the top

Notes: Before the update that switched from UWP to GDK there was never an input issue with normal polling rates.

high polling rates like 2,000 to 8,000 are likely to cause CPU issues even with some modern games but 1000 has been the standard that bedrock has always been able to do smoothly

It almost seems like the mouse input was downgraded in some way where it isn’t raw input and lifting the mouse confuses it’s last known location so it just stutters, or can no longer handle modern day polling rates. When I use 125hz I have no stuttering. I have tested this on multiple high end mice and only have this issue on Minecraft. My PC can use 2000hz polling on other games without issue. I have heard this issue brought up by players who enjoy PvP as the lack of quality in mouse input in the last 4 months has been noticeable and even a deal breaker for some. I even stopped playing for 2-3 months because It made the experience of playing the game difficult for me as the input feel of a game is very important to me. Playing on a refresh rate of 280hz but a mouse polling of 125hz makes me disappointed as I upgraded my monitor and wanted a good experience on the game.

Comments 8

This is actually true. It’s almost unplayable now. Before the GDK update, it used to run very smoothly, but now it’s stuttery and horrible for PvP.

I noticed this immediately, I stopped playing for 2-3 months because of this. And now only 125hz polling is playable to me. I really want to be able to play on 1000hz polling again which is average. I play on Oled 1440p 280hz so the stuttering is even more of negative impact and highly noticeable and 125hz polling with a 280fps does not match up well.

I thought it was just me! I switched to using my controller because when I use my mouse the screen teleports when I swipe it.

This made me switch to java…

Literally the mouse input broke and even if I wanted to switch to controller there aren’t deadzone controls in minecraft like other modern games have. I don’t know why minecrafts controls don’t get as much attention, it’s what you use to explore the game in the first place.

I have had this issue for the past 4 months since the GDK update. I have an OP1 8k and the mouse software doesn’t allow a polling rate below 1k so the newer versions are unplayable for me.
If i use a controller to look around there is no visible stutters.

The controller test on max sensitivity was what I tried also. It’s smooth, you swipe a mouse even on 240fps plus and it looks like your frames are dropping even though with a fps counter you can see it’s stable.

Please do not select Future Update as an Affected Version. You don't have access to it yet. Please edit your report to change the Affected Version to the version shown on the Minecraft title screen

I truly cannot believe they haven’t fixed this. Are they aware of how many people stopped playing there game because of this? The only fix for me is capping your fps 60 frames lower ( I use 180hz so i cap my game at 120) then I apply DLSS lossless scaling to 180 frames using the Lossless Scaling app. The con is 1ms delay lag

Branden Scott

(Unassigned)

1568113

Community Consensus

Windows

26.10.25 Preview, 26.3

Retrieved