Affects 1.21.2
On Windows, this issue also appeared with the implementation of the new graphics engine, both in the beta (1.16.100.54) and in the official release (1.16.200). Some players used an alternative method to download the x86 build of the game instead of the x64 build, as the x86 build did not have the input delay. Now it has, because RenderDragon was finally implemented in it in the last update (1.18.30).
The input delay is clearly related to RenderDragon.
I have the same problem in the version 1.17.32
The new Beta 1.16.220.51 does NOT completely solve the problem. The input delay improves to a level where the game becomes almost playable, but is still a major nuisance. Changing the "vsync" option to "0" seems to slightly improve the input delay, but at the cost of a huge amount of frames per second. Anyway, the game remains unplayable.
Here are the specifications for my computer. I have the same problem. The game's FPS is fine as usual, but the mouse input lag makes it unplayable. My Windows is up to date and so is my graphics driver (intel HD graphics family).
[media]
I am having this problem in the official version 1.16.200. The response time of the mouse is terribly high, even with Windows and the graphics drivers properly updated. This is not a problem in the game's FPS, the frame rate remains as good as usual. But the mouse has a very, very large input lag. Even out of a world. In the menus, the delay between the cursor movement and the buttons being selected is ridiculous. Update 1.16.200 made the game impossible to play.
I'm not sure if that's is the case, but I think pillagers' crossbow don't break because they aren't supposed to. It may be intentional that pillagers can shoot forever.
I have confirmed the same issue in my game several times. I hope this will be fixed soon.
I made a villager farm on Windows 10 Edition 1.12.0 and they are harvesting carrots normally. They only stop harvesting when I remove the beds of the farm, so they no longer want to reproduce. Maybe you should put beds on your farm.
My Minecraft on Windows 10 Edition is crashing frequently when I close a world, and has several framerate drops in game since 1.10.0 (which I reported here and no admin didn't even read it).
I made a clock system to activate a dispenser and it worked as i expected.
I had this problem several times. They spawn in very deep caves and even using a glitch to see through blocks its difficult to find them.
I play on Windows 10.
I was always moving far enough on my testing.
If there are only one, two or even three spawning spots available for the pillagers to spawn, sometime they will stop spawning forever, regardless of the conditions (mob cap not full, player far enough, no light). They will only respawn in the other (the unavailable) spawning spots if they becomes available.
I don't think my raid farm is going to be broken, it is still working pretty good.
I dont know if it will answer your problem, but I did some testing (when I was developing a raid farm) and found that a pillager outpost has four spawn spots, one inside the outpost and the other three outside, with no blocks underneath them, so pillagers cannot spawn on them. If there are less than the four spawn spots available for pillagers to spawn, they stop spawning after a while. I think you should build a platform on the same Y of the highest floor of the outpost to cover the four spawn spots. A spawn spot is a corner among four blocks, the first one is near the chest, find it and the others are six blocks far. The four spawn spots make a square.
The game keeps lagging and I think it wont be solved...
It keeps lagging, but less often. The framerate is still unstable.
It looks like the framerate drops stopped after version 1.10.1, but I need to play more to make sure. The game keeps lagging abnormally when there is another window loading something.
I know it's not a problem with my device because I have an app that tells me how much processor and RAM my computer is using, and the numbers never come close to 100%.
I always search before reporting an issue, but didn't find this. :x sorry. I voted on the original one.
Can the developers or moderators PLEASE clarify why the status of this issue was changed to "resolved" even though there is no fix version?
Update 1.20.30.20 Preview, the most recent update listed as a "fix version", was released in August 3, 2023, and it DID NOT fix the issue, as reported by several users. The status of this issue was changed to "resolved" in September 4, 2024, 13 months after 1.20.30.20 Preview. No changelog of any update after 1.20.30.20 Preview mentions this issue.