mojira.dev

Sean Kelly

Assigned

No issues.

Reported

MC-271105 Stuttering of 1–1.2 seconds every 4–5 seconds on macOS with 1.20.5 (lag spikes) Duplicate

Comments

For those checking back here and want the quick workaround, here's what did it for me:

  1. In the Launcher, go to Settings (lower left), General, scroll down, and ensure that "Use Arm64 Java runtime for Minecraft: Java Edition" is checked.

  2. If you don't have this option, make sure to uncheck "Use beta version of the Launcher" and restart the Launcher; then check the box by "Use Arm64 Java runtime for Minecraft: Java Edition". (You can then go back to the beta after this if you like.)

  3. There's no step 3.

Enjoy.

Thank you @galaxy_flutter for adding your profiling log as well πŸŽ‰

Thanks for adding your profiling log too, @cooldogwalter! πŸŽ‰

Thanks for assist, @turbo! I've attached the two `.zip` files. Hope they help!

Thanks @K7Y, the graphic settings have been adjusted to be minimal. This Mac is a Mac Studio with an M1 Ultra CPU and is plenty powerful enough to run Minecraft.

I've done testing with a much older Macbook Pro and it doesn't show any problem, so the issue seems to be either with this Mac Studio or software also installed on it. However, as I mentioned in the report, downgrading Minecraft to 1.20.4 shows no problems whatsoever, so it's some combination of 1.20.5 and this platform.

As of 2022-04-30, public chat, signs, and books are working again for me on Realms with the Java 1.18.2 client.

Currently, this bug is showing as open and unassigned, but clearly someone's working on something server-side, and their work is appreciated πŸ˜„

+1

Β 

In the Realm I play on, many existing signs have gone blank (although some managed to retain their text). Any new signs placed down lose their text immediately. No public chat messages appear at all (although /whisper works).

Β 

Is there an over-zealous profanity filter on Realms that is censoring every single word?

Here's a short movie that demonstrates the problem:

[media]

This seems to have regressed in 1.18.

I do have this issue on mobile happens on single player and on realmsΒ 

Β 

Β