This cannot be reproduced in the newest versions. Its fixed.
Hi!
Same issue here on Windows 11, on a Realm. Sometimes they become a bit longer, and appear together with a freeze screen. (still very short, but way more noticeable)
A little bit annoying, please fix!
Hi,
This report can be closed.
I selected "Windows Sonic for Headphones" under "Spatial sound," which fixes this issue.
Isnt it fixed in the latest Preview?
It's also very noticeable when riding a horse into water and getting pushed off of it. Sometimes you get “teleported” around before you land in the right position.
Sometimes, when you join a Realm (servers and local worlds too, possibly), you get pushed slightly in one direction, which could put you in a really bad situation—like falling from high places and losing your stuff, or even your entire Hardcore world.
I guess this is related to that bug, or maybe even the exact one, even though I don’t know what exactly caused the push.
Hi!
I play now on the Windows (11) Edition of the game. (I recently reset my PC, installed Windows again. Everything was just fine until the recent updates like 1.21.90 and 1.21.92.)
I play with a DualSense controller, which is connected via cable to the computer. But it happens on the PlayStation 5/4 too. I have not made any modifications to my PlayStation.
I have not experienced any other issues on my PC that could be related to this bug.
No, I do not use any addons. This bug happens on servers that use addons, but it also happens in worlds that do not have any.
I play on the highest possible settings. Exceptions: I do not use Vibrant Visuals, and I have the chunk render distance set to 25.
Other information:
On the Windows Edition, the bug started with freezes occurring rarely, and the freezes weren't long (something under a second). However, just today I experienced this issue again, but with a freeze that was about 2 seconds long. So it's the same pattern as on the PlayStation 4 version of the game—it started rare and short, but became more frequent and longer.
Reinstalling the game (and losing all worlds in the process) was the only way to get rid of this bug for a few days, until you'd need to do the reinstall thing again.
When joining a world—especially servers (I play on Hive)—this bug seemingly occurs at the moment you join. Meaning: the world loads, then the loading screen disappears, and you can see the world, but it gets interrupted by a freeze lasting about 2–3 seconds. This could be the bug, but I’m not really sure.
Actually, now that this bug happens on PS5/PS4/PC, it's more likely that the developers can experience it themselves — which should make the fixing process easier.
Here's a good way to reproduce it:
Get some kind of FPS counter with a graph on your screen. The graph makes it easier to spot the freezes/trace them back.
Join a server (I’ve experienced this many times on Hive, but also on my own Realm).
Just play. Keep an eye on the graph. You’ll notice the bug in-game even without the graph, but especially when you're not 100% focused on gameplay, the graph helps you catch it more reliably.
The freezes happened frequently and for long durations on my PS4. I think it's worth checking for the bug there. But if it's not possible to get a graph on PS4, try reproducing it on PC instead.
My naive theory:
It might have something to do with the game not receiving data quickly enough — maybe from storage. Perhaps there's a limit programmed into how fast the game can access information from storage, but that limit is set too low. That could explain why the issue happens more often on PS4 and less frequently on PS5 — where the limit might be set higher (though it still occurs there).
Additionally, on servers like Hive, you're constantly moving and loading new areas, which might be why I experience the bug more often there compared to my Realm — where I usually stay in the same area and don’t see the bug as often.
So, I’ve now switched to the PC (Windows) version — and what do I see? The same bug.
I can’t play on any platform anymore. It worked just fine yesterday, but today I’ve already experienced this issue three times. What am I supposed to do?
Why is this bug being ignored? I mean, the first report has at least an ADO number — whatever that’s supposed to mean.
The only information I can provide:
I play with a DualSense controller on the Windows edition.
I’m using Windows 11.
This bug affects PS4 players, PS5 players, and Windows players.
So, I’ve now switched to the PC (Windows) version — and what do I see? The same bug.
I can’t play on any platform anymore. It worked just fine yesterday, but today I’ve already experienced this issue three times. What am I supposed to do?
Why is this bug being ignored? I mean, the first report has at least an ADO number — whatever that’s supposed to mean.
The only information I can provide:
I play with a DualSense controller on the Windows edition.
I’m using Windows 11.
This bug affects PS4 players, PS5 players, and Windows players.
This bug right here will probably—just like the other two mentioned above—keep getting worse and worse and worse.
It seems to me like this bug disappears—or at least becomes rarer or less noticeable—when restarting the game frequently.
We have:
MCPE-179572
This bug makes the game unplayable for some PS4 players unless they reinstall the game weekly, including deleting their game data—which means losing all their worlds.
And:
This bug forces players to interrupt what they’re doing and follow a specific set of steps from the bug report to temporarily fix it.
We now have three bugs that appear periodically. Two of them are difficult to capture on video but are clearly noticeable in-game.
Why are such frustrating and hard-to-describe bugs being introduced—and then completely ignored?
This is absolutely related to: MCPE-194370
It's actually the exact same issue: you receive knockback and get pushed into a position, but something prevents you from reaching that position. The same thing that causes MCPE-194370 is causing this issue as well.
The game forces you into the position where you would have ended up, had something not blocked you.
The only difference with this bug is that the block you're forced into pushes you back out — which, by itself, isn't a bug.
This Bug could be related to:
MCPE-194370
I edited most of the bug report after I found out which situations trigger this bug. The two mentioned videos:
In these videos, the bug appears every time—sometimes more noticeably, sometimes less.
[media][media]The 2 Videos:
[media][media]
I updated the Bug report.