These are the videos that explains the issue. Thank you!
^
^
^
[media]^
^^
[media]^^
^^
[media]^^
^^^
[media]^^^
^^^
[media][media]^^^
^^^
[media]^^^
^^^^
[media]^^^^
^^^^
[media][media]^^^^
^^^^
[media][media]^^^^
^^^^
[media]^^^^
^^^^^
[media]^^^^^
Sorry for some bad english. I hope you understand.
It occurs when you type for the first time after creating or loading a world. It has an irritable delay.
Potion effects like wither effect, harming, fatal poison and others that killed anyone crashes its game. It is through by drinkable, splash and commands as I stated in the description.
Description: In front third person view if I use the joystick and move forward, I go backward. But when I move backward, I go forward. Well, not in case of the d-pad where I move correctly. Sorry for the bad english.
Thank you!
I use with split controls in new touch controls.
Same. I experience the choppy animation.
Oh ok. Thanks! ❤️
Same! I experienced the choppy animation recently after the update. Hopefully they will update it.
Hopefully you can fix as soon as possible even though it has duplication.
Although I was in server, everytime I am in multiplayer or singleplayer, it has a choppy animation. Before it has smooth animation. Also it was not my phone that is choppy.
In the first image, fireball was entity as if you see on @e.
In the second image, the /summon spawns entities, but the fireball is not included.
In the third image, there's no fireball as it already had way back then in Pocket Edition.
The second video was the unlit redstone torch in setblock has its problem. It got unlit for a miliseconds then got lit up for the rest of the time. It should remain unlit for unlit redstone torch.
[media]The first video was that the redstone torch in setblock command is all good.
[media]I have a picture that there is 2 kinds of redstone torch in setblock command.
[media]I meant if I setblock the unlit redstone torch, it should be remain unlit. But what happened was it got light it up itself.
Oh! Thanks! I'm sorry for the typo. But the bug is still there. You can see it on the video I sent.
I received the 1.18.32 hotfix in my Android device. From my experience, I got a little higher FPS than the previous update.