Player/world jitters at high X/Z coordinates

This is still present in the Nether Update

How can we get this bug report I made to their attention ?

I'm sure they are well aware of it in a more broader sense but I don't know if they plan to fix it.

Truth is I wouldn't know they are aware of the distance effects but won't fix them for example they claimed to have "patched" falling through the world but they didn't patch it they just made it much harder on my duplicate issue report I didn't know that someone else reported this in all honesty this is the biggest thing that bothers me about bedrock

I got java edition cause on how much this bothers me by the way look into "bedrock distance effects" on Minecraft wiki cause has mentioned before it has many many distance effects and not 1 has been patched

I am very sure they are aware but they won't patch this bug at all maybe it's laziness? Either way it's very bad cause this obviously effects servers too so any massive server has to deal with this from far out

Personally I can notice the jitter around 10K blocks and that makes me mad as one thing I love doing in Minecraft is exploring and 10K blocks or more in bedrock makes the movement feel very crappy also java edition is 30,000,000 blocks out not 60,000,000 it's still much much more then bedrock though

Has java's distance effects don't even happen till past 30,000,000 while bedrock's begin as early as 10K it's sad cause I know they are aware of these issues but won't truly patch them or at least make a statement

If I was to say your best chances of getting their attention likely would be getting a lot of votes on this issue so if you can get a lot of votes it may help and I only say may cause the falling through the world bug report got lots of votes but they only made it harder to fall through

But even so it's worth a shot so good luck on this cause I want bedrock's distance effects patched too despite now being a java player but I play bedrock on console with friends so I would still want this fixed

Yes, I run a self hosted bedrock server for me and a few of my friends to goof around in.

I had to tell them to not go beyond 12K blocks because of this jitterness issue.
I don't want the server to have some weird crash on it and all becomes lost.

The java version uses 64-bit for calculating player positions and other various aspects. While in bedrock it is obvious they are using 32-bit.

I was on Java for years but switched to bedrock due to increase performance and cross-platform. But this distance limitation is a real REAL annoying bug that is actually holding back bedrock edition from truly shining.

If only we can get thousands of people to vote this up.
If only!!!

Well I got a suggestion for you of course this wont guarantee anything but you can tell your friends and other bedrock players you know to vote for this issue the more votes the more likely it is to get noticed its unfortunate but that is how it is so your best bet will be to tell your friends to vote for this issue

Partially covered by MCPE-39299 and MCPE-102351.

Not just partially covered but fully covered as all of this is caused by the same thing

Still present in 1.18.30

So in the Minecraft wiki website it says that only 23 bits of precision are used for the locations of entities but I don't understand why only 23 bits but not all 32 bits because if it actually used the 32 bits then you could go further without it jittering. ( something like 8 million blocks ) 

Affects 1.20.30

Affects 1.20.51

Affects 1.20.62.... Why? This bug makes a huge part of the world unplayable. Why does this bug still exist?

Affects 1.20.71

I wonder if in the 1.25 update, one will be forced to enter these bugged areas to load new chunks, as additional new structures can/must be found there.

affects 1.20.72

Affects 1.21.20.21 

Hotcoco-cat, According to the [wiki|https://minecraft.wiki/w/Bedrock_Edition_distance_effects#:~:text=the%20other%209%20are%20used%20for%20the%20sign%20and%20the%20order%20of%20magnitude[],] While Bedrock Uses 32-bit floating points, only 23 its are used of precision because the other 9 are used for the sign and the order of magnitude. On the other hand, Java uses 64-bit floating points but in the same way not all of those bits are used for precision. 52 bits of precision (double fraction format) are used for Java instead of bedrocks 23 bits (single fraction format).

@unknown,

Is it for the Mojang-Team possible to change it so that Bedrock has more of these bits?

affects 1.21.3

SaveTheBedrock, Its likely possible but may be a huge task. The reason Bedrock is partially 32-bit is because during its inception, most mobile phones had 32-bit arm CPU's. If 32-bit support was dropped, there is no telling the number of players would lose access to the game. In addition, this is not really high priority for them unfortunately. Mojang probably has telemetry that tells them that most bedrock players don't travel the far distances required to experience these jitters. So they don't feel the need to address it immediately. 32-bit support has begun to fade away as time has passed, I'm sure Mojang will fix this issue when they are ready.

Don't look for reasons to please mobile "32-bit systems and 32-bit CPUs", because those old CPUs can't carry games for a long time. And now the optimization is not good, even the flagship processor on the mobile side often stutters and drops frames.

So, Mojang is adding a (very nice and cool looking) new biome, which is relatively rare. This means we'll need to travel long distances to find it. Mojang, hello? There’s a bug that ruins the game experience if you go too far from the spawn point—in an ADVENTURE game. And now you're forcing us to travel those distances, but won't fix the bugs that prevent us from doing it? Does anyone at Mojang even play Minecraft Bedrock Edition? Are they aware of this nonsense?

I did some math and found out that only 0.067% of the Minecraft Bedrock world is normally playable. 

Dropping 32 bit support wouldn't be a problem. Majority of phones are 64 bit nowdays.

Thank you for your report!
After consideration, the issue is being closed as Won't Fix.

Please note that this is not the same as Working as Intended, as this bug report correctly describes behavior in the game that might not be the intended or desirable behaviour, but it will not be fixed right now. Sometimes, this is because the issue reported is minor and/or impossible to change without large architectural changes to the code base.

If you'd like to post a suggestion or give further feedback, please visit the Minecraft Feedback Site or choose a link below.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

Request to reopen this bug report: After every update that adds new structures or biomes, players have to travel farther from spawn to experience the new features. Players with older survival worlds are already forced to explore areas affected by this bug to find new content, which significantly diminishes the gameplay experience. Keep in mind that with each update, players must travel even deeper into these areas, further impacting gameplay. Also, consider how quickly these areas can be reached through the Nether. A five-minute trip, set up a portal, and you're in an unplayable overworld. This bug also affects both large, official servers and small private servers with many structures and regions. Public Survival servers, where long-distance travel is essential, are particularly affected. Please reopen this bug report.

The problem this bug poses has again been exemplified in the 1.21.50 drop. I've had friends mention to me how difficult it is to deal with this on their large realms as they have had to travel thousands of blocks just to find a Pale Garden. I really hope Mojang considers reopening this issue because like stated by SaveTheBedrock , players with older worlds are forced to explore farther and farther just to engage with new the content in each update. A lot of these players do not have access to chunk trimmers or other tools which could help to remedy this because of platform limitations.