Eldar
Assigned
Reported
MCPE-230674
Poor frame pacing and micro-stuttering at high FPS/Hz after recent game update, despite high framerate.
Duplicate
MC-266963
summoned fireworks colors don't work
Cannot Reproduce
MC-204460
Mesh between blocks
Duplicate
MC-86164
When renamed with a name tag, armor stand will not show the nameplate above its head until CustomNameVisible:1b is set
Confirmed
MC-86077
armor stands can't get a custom name
Invalid
Comments
I can confirm the problem for Ubuntu 16.04 LTS too (in all 1.13 Snapshots).
I have the same issue in 15w51b, but I don't have to jump from a high place. It just stops working completely, just negating fall-damage most of the time.
well thx for trying to find a solution, but I'm not here to find one. I know the commands good enough, that I already used that. I just wanted to make the bug public, so it can be fixed by Mojang.
/entitydata @e[type=ArmorStand,r=5] {CustomName:"Name Here"}
Thx, I know this command, but that doesn't change, that you can't rename an armor stand with a name tag as you could before (and should be able to).
Also this bot-thing is silly. Why do we have access to this version number in the affected versions list, when we aren't supposed to mark it with it?
Please re-open! First off the name isn't displayed above the armor stand and second of your command doesn't result in saying test, but instead lists all entities before literally saying {CustomName:test} as you can see in the second picture I added as proof.
ok, you're right. That was a silly mistake. Anyway, the name tag doesn't work.
Deleted the mistakes I made. Thx for the help 🙂
Well I wouldn't call this a bug, because they just disabled it completely (not just the gui!), but you are free to try. As I said before I would love to get access to it's functions too, but I don't think it will be in 1.9.
I would be happy if they add support for it, yes. But as far as I know it will work for them, because they just disabled it in the released version...
The structure block isn't supposed to work. It's just in the game to help them to implement new structures (such as the end city).
Confirming the issue on a high-refresh-rate system with detailed specs.
System Configuration:
CPU: 12th Gen Intel(R) Core(TM) i5-12400F (2.50 GHz)
GPU: NVIDIA GeForce RTX(TM) 4060 (Driver 561.57)
Monitor: 180Hz, 1920x1080
OS: Windows 11 Pro for Workstations, Version 24H2
Specific Symptoms:
The jittery camera movement is especially severe and pronounced at high refresh rates (180Hz, 165Hz). At 60Hz, the problem is less noticeable, but the game feels unplayable due to low smoothness. The issue is 100% reproducible and feels like a severe frame pacing problem, not an FPS drop (the FPS counter remains locked at the monitor's refresh rate).
Extensive Troubleshooting Done:
I have exhaustively tested the following in the NVIDIA Control Panel, all with no success:
G-Sync (On/Off)
V-Sync (On/Off)
Low Latency Mode (On/Ultra)
Various Frame Rate Limiters (in-game, driver-level, NVIDIA Profile Inspector)
All Anti-Aliasing settings (In-game TAAO/Bilinear, Driver FXAA, MSAA)
Power Management Mode (Prefer Maximum Performance)
Resetting Shader Cache
The problem appeared immediately after the 1.21.120 update. This confirms the issue is with the game's rendering pipeline and not user settings or hardware.
My original report was [MCPE-230674] and was marked as a duplicate of this one.