I have tried to turn anti-aliasing down to zero, it did change something, but comparing to the expected, it's nothing.
The problem is about the maximum performance but not really the hardware's performance limit. In the attachment, you can see that the GPU was never utilized to 100% but cap at 60% for some reason. (While running at 20~45FPS without a frame limit set)
Edit: Anti-aliasing is set to 1. There isn't am option to turn it off.
Yes that worked perfectly! I also put down a grindstone and some other workstations and some of those brown robed villagers turned into different trades.
I forgot to mention this but, I tried relogging, setting my smooth lighting to off, graphics to fast, and render distance down to 8, and it seemed to have no effect
What do you mean when you say Minecraft may or may not support them? All mobs except for bats can be leashed (with the help of editors, of course), but most of them follow the "rules" of leashes, including zombies and skeletons. I just don't see why the slime-based mobs should be exceptions, or if they're supposed to be.
Some problems were fixed in the 1.6 prerelease. The armor now seems to display the proper number of hearts at all times. However, the player will still have "20 HP" upon wearing the armor for the first time. Damage in this state seems to fix this though.
I have tried to turn anti-aliasing down to zero, it did change something, but comparing to the expected, it's nothing.
The problem is about the maximum performance but not really the hardware's performance limit. In the attachment, you can see that the GPU was never utilized to 100% but cap at 60% for some reason. (While running at 20~45FPS without a frame limit set)
Edit: Anti-aliasing is set to 1. There isn't am option to turn it off.
My duplicate issue was presented without bucket disappearing in 1.20.51
A freeze at 45% could be due to network conditions, when the client itself is trying to connect Xbox Live service
have the same issue
ok thanks
Experiencing same issue on beta 1.15.0.56 LGE LG-V521, Adreno (TM) 405, Android 7.0
Crash occurs second time joining server, during "Generating world - Locating Server"
To replicate:
Connect to a server such as Lifeboat
Save and quit
Attempt to connect to server again
Can you please fix this, I can't play this game with this happening
Can y'all notice this? Like I literally can't play minecraft with this happening
Yes that worked perfectly! I also put down a grindstone and some other workstations and some of those brown robed villagers turned into different trades.
Oh, I was unaware that that would affect it, thank you!
Merry Christmas / Happy Holidays!
I forgot to mention this but, I tried relogging, setting my smooth lighting to off, graphics to fast, and render distance down to 8, and it seemed to have no effect
The response is near-identical: string parsing fails because of an unbalanced quotation.
What do you mean when you say Minecraft may or may not support them? All mobs except for bats can be leashed (with the help of editors, of course), but most of them follow the "rules" of leashes, including zombies and skeletons. I just don't see why the slime-based mobs should be exceptions, or if they're supposed to be.
Redownloading the snapshot fixes it.
By the way, you really shouldn't spam your own comments section.
No regular zombies or pigmen are spawning for me. They're all babies.
Some problems were fixed in the 1.6 prerelease. The armor now seems to display the proper number of hearts at all times. However, the player will still have "20 HP" upon wearing the armor for the first time. Damage in this state seems to fix this though.
That's why the issue is so annoying. You can't reliably lose or gain health without removing and replacing the piece of armor in question.