Colin Smith
Comments
Confirmed, still happens in 15w42a
There is something very bizarre with this bug. Two people with nearly identical systems can have vastly different frame rates, which doesnt make any sense as the minecraft jar is the same across the two systems.
The normal troubleshooting steps are:
make sure video card drivers are up to date.
install the latest version of java after uninstalling the old one, and upgrade to 64bit if you can.
delete your minecraft shortcut and create a new one.
make sure your power profile is high performance (especially on laptops, this is vital)
disable all background programs with msconfig and reboot.
backup the entire ".minecraft" folder to another location, and then delete it, and redownload it from scratch as it will redownload all the libraries.
make sure vsync is off in minecraft settings.
try fullscreen/windowed to see if that changes it.
What AV are you using?
Have you tried deleting the entire folder and starting from scratch (after backing up your saves)?
What OS/hardware are you guys running? 1.8 on my old laptop (core I5 dual core, with basic 6700 series ATI card, 16 gig of ram, and windows 2008R2 server edition) im getting over 160 fps with 10 view distance. There has to be something else going on here. Java 7 64bit.
This is starting to sound like two different bugs. There is the one where a block doesnt update for a period related to frame rate, then there is the one where only a block update fixes it.
I am able to reproduce the bug nearly 100 percent reliably.
While moving back or forth, keep opening/closing a door. It looks like it happens when the viewpoint changes and another block is selected WHILE its updating, or the "visible" area changes when doing a block update. It doesnt ever seem to happen when you are still.
It will get to the point where the door will look closed but actually BE open, or vice versa.
This issues fixes itself if you destroy a block next to the door, so it looks like a block update fixes the glitch. Even a block being destroyed with the door just out of view fixes it. If you do anything with the door behind you or way way out of view, it doesn't get fixed.
If you place a block or destroy the block more then around 3 meters away, it stays glitched.
So.. perhaps there is a flag saying "update the engine" not being passed occasionally to the render thread?
It seems to be a lot easier to reproduce when you are moving. This is pretty important. I can reproduce this bug with anything when you are moving. When you are still, its seems to be impossible to reproduce the bug. So it has to be something that changes when you coordinates are changing. Just looking around doesnt trigger it. Its only when you are actually moving. The F3 view when looking at the selection box says the door is the opposite of what it actually looks like.
Another update. Just had the door bug out again. I have multiple screenshots of it, actually standing in the door, and the selection box showing it as open. It stayed like that no matter what i did (as long as i didnt click it) i could walk through the door, and so could mobs, and i heard the sound, but the door "looked" closed. Exiting the game and then reloading the save fixed it though.
If it helps, there are also selection issues with other things too, for example flowers show up with the selection box in a different spot. There seems to be some occasional disconnect between the render engine and the actual state of the game. The game said the door was open and the engine treated it like that, but the actual rendering still thought the door was closed.
I had massive issues with 34c, even to the point where it felt like the game was missing mouse events, and the view didnt follow the movement of the mouse.
It has to be something else as well though Grum. I have a machine that can pull over 500 fps, and its always over 100 outside on 16 view distance, yet when i get this issue, its usually permanent, not just a few frames. Just now i was playing and i opened a door. I heard the sound, and i can walk through the door, but the door didnt change state. I had to open and close it multiple times for it to work. When the glitch happens it often sticks around for a lot longer then a frame or two. It also shows that in the screenshots, there is no way you could get a screenshot of it the issue if it only existed for 2-3 frames.
This particular issue has now only been in the last four snapshots ( i think, correct me if im wrong). Something changed 4 snapshots ago that made this happen. I have a hex core intel I7 machine, 4.7 gig, 7900 series video card, 32gig ram at 2.4gig itself.. and i get this issue probably at least every 2-3 minutes of play.
Perhaps it was that "Viewable" code that was ported from the portable edition?
Using the absolute latest dev. Its not as easy to reproduce as originally, but its still occasionally there. Will try to catch a screen shot.
It appears to be some corner case, much harder to reproduce but it seems to be related to the lag fix. That lag fix totally fixed the missing blocks.. somehow linked?
Ok, will recreate this world and see what happens.
Place some wooden slabs in empty space, and just start to add to them. Sooner or later it starts, you place a block, its the exact same bug back again.
If you cant repro, i can record/screen shot it.
Its back in 14w34d.
Ahhhh the missing block fix is broken again!
Fixed for me in 14w34d!!!
This specific bug doesnt seem to be addressed as a "fix" but it seems to be gone.
Confirmed here too. Also when looking with the mouse it sometimes feels like the game is "missing" mouse events, and you dont turn as much as you think you have.. it kinda forgets about the occasional mouse event.
Having this issue as well, It is specifically visible if you place a lot of blocks at once, not letting go of the mouse button.
Not a slow PC either, Radeon 7990, hex core 4.7 gig I7. 16 gig ram.
My first thought was that it was at a chunk boundary but further testing eliminated that.
Guys, change your power settings to "maximum performance" and see if the lag goes away.