Morgan Stair
Assigned
Reported
Comments
Hi Grum,
I just found that (for me) changing the "Max Framerate" has a dramatic INVERSE effect on this bug.
My previous observation about the game being unplayable was based on "Max Framerate" = "20".
"Max Framerate" = "unlimitted" : this bug does not show up at all (albeit with very limitted testing).
"Max Framerate" = "10" : this bug is worse than ever.
I'm not going to suggest WHY changing the "max framerate" has such a dramatic effect, but it does... at least for me (single player survival mode).
Grum wrote:
> On a given system that can obtain ~60 fps, a hole would be visible for upto 'just under two frames', which would be around 16.7 * 2 = 35ms
> Now, if you have a system that averages at 10fps, this hole is visible for upto 200ms
FYI, when "Max Framerate" is unlimitted, my system gets around 100-300 FPS with VSYNC turned off. I like the framerate turned down to minimize CPU load, thus heat, and thus fan noise 😉
Yeah... sorry. Instead of saying "unplayable" I should have said this bug makes single player survival games too frustrating to play. You just can't play those games without immediate visual feedback when you've uncovered a "hole" or you're gonna fall in it.
FYI - This bug makes MC 1.8-pre1 unplayable. I had to give up testing 1.8-pre1 åfter just 10 minutes when I fell into an "invisible" hole exposed while mining.
Hi Kumasasa,
Thanks... I needed to record the info somewhere, and this was the best place for it in terms of storing state. I do appologize for using this as such, because I didn't mean to distract you from evaluating other issues. FWIW, I had read your earlier comment here (when you closed this issue as invalid) and I had done some searching based on your previous comment, but you didn't give a specific link where MC:PE bugs could be reported and all I was able to find quickly was this "official" link on the mojang.com site that brought me back here - if you know who to contact to get this page fixed, it would help:
https://help.mojang.com/customer/portal/articles/409117-where-can-i-view-or-submit-bugs-
However, for future readers looking for a place to report MC:PE bugs, I've since searched some more on the sites you suggested and (for future readers looking for a place to report MC:PE bugs), for now, the following appears to be the best place to report Minecraft Pocket Edition (aka MC:PE, MinecraftPE) bugs:
Minecraft Forums -> http://www.minecraftforum.net/forums
Minecraft Support -> http://www.minecraftforum.net/forums#forum-root-support-1013
Pocket Edition Support -> http://www.minecraftforum.net/forums/support/pocket-edition-support
This Issue -> http://www.minecraftforum.net/forums/support/pocket-edition-support/2169430-hostile-mobs-not-visible-in-local-wifi-clients-if
The key link is this one... who knows if PE developers read it, but this is the best I found:
Pocket Edition Support -> http://www.minecraftforum.net/forums/support/pocket-edition-support
– Morgan
Confirmed in MC:PE 0.95 (released version)
iPhone-4 with iOS 7.1.2
Severity: CRITICAL (in my opinon)
The "peaceful" mode comment is wrong - this happens ALL the time.
This is as bad as a bug gets since my kids can NO LONGER PLAY TOGETHER after upgrading.
There is no way to downgrade iOS "App Store" products to previous versions.
@Stephen wrote:
> The block updates correctly ... going out of the view cone and re-entering it.
I am definitely having a different experience from yours. As mentioned in my comment on 7/30, I dug a big square trench and none of the dirt I'd dug disappeared until after I'd stopped digging and looked around (and then waited a couple of seconds).
@Jacob - Whee... if you accepts that this bug "will always exist" then you'd would need to be qualify which variations on this bug have a "significant" effect on gameplay... but you may be right. If I'm reading between the lines of your post correctly, then you're saying that this new separation between the world "model" and the world "view" really needs to exist, even though it didn't exist (to this extent) until now.
Regarding "machine performance and video settings", I just tried this while monitoring the CPU. It never exceeded 25% load. Minecraft used to burn CPU like crazy - now not at all.
I'm using a a recent high end macbook, but it's still a laptop, so I wouldn't expect great "performance"... but this doesn't seem tied to CPU load or memory at all... it's as though minecraft isn't even trying to use the CPU to update the screen. I thought it might be a JVM problem, so I gave it 4G and loads of per thread stack, but it didn't make a difference.
EDIT: "... isn't even trying to use the CPU to update destroyed blocks..." The "screen" is updating fine.
14w31a:
1. I created a new world with cheats enabled
2. I gave myself a diamond shovel
3. I dug a big square trench
None of the dirt I'd dug disappeared until after I'd stopped digging and looked around.
4. I waited about a minute to see if this was just a startup issue, then tried it again: I dug three more blocks then turned around to look. None of the blocks had dissappeared. A few seconds later, they all disappeared.
5. I thought I might be able to work around this by digging one block at a time, but found that the screen wouldn't update even after digging just one block until I'd waited about 2 seconds.
In short, the problem seems to have gotten worse in 14w31a... even with a new world (survival mode). Is no one else seeing this?
14w30c - The bug isn't immediately noticeable in a fresh world. It shows up after playing for a while and gets progressively worse. I found that running into a new area and then digging continually would make the bug more obvious earlier on.
After several hours of playing and building a wheat farm, it became so bad, I couldn't trust the visuals at all because they wouldn't update while I was doing something. It became progressively worse over time, until eventually the game was unplayable.
I had to quit and restart a few times after everything froze. Restarting did seem to make things better for a little while, but I can't say for sure.
I've given up on using 14w30c because the worlds eventually stops being usable.
14w30c - problem can be extreme (5-10 seconds before changes appear) if I'm performing a lot of changes, like mining a bunch of blocks or running around gathering stuff. The most painful scenario is when you uncover lava or water and there is no sign of it until the UI "catches up".
I'd agree that it's not acceptable for hardcore, but as for myself (1.8 release, single player, 12 block render distance), it now seems "acceptable" after the latest updates. In other words, I am now only seeing block update delays in situations that don't affect gameplay, eg., I saw it while chopping down a tree three blocks away.
There are probably variations on this story that still present a serious problem, but unless they refine or split up this bug report into a couple more specific bug reports, be specific about which variation on this bug you're seeing.