Zacharry Williams
- cooldudezach
- cooldudezach
- Europe/Stockholm
- Yes
- No
MC-27455This doesn't happen all the time, but it happens once in awhile. It's enough to cause confusion and annoyance.
When trying to sleep in a bed, the chat window and leave bed button appear while the 'getting into bed' animation is stuck in a loop in the background. It seems as if you are in bed, but will prevent the night from skipping to day. You have to get out of bed first, then enter the bed to be able to actually sleep.
I have only seen this on SMP with another player logged in, however it has happened to a friend on the same server without anybody else logged in. I do not know if the player model is displayed as 'in bed' or just standing, but the client-side display does update as if you are sleeping, just with the loop in the background. If it happens again, I will try to check this out.
Possible cause: Still moving while trying to enter bed while there is some lag on the server. My friend suggested this, as this issue has affected her more than it has me.
EDIT:
I can reproduce this following these steps:
1: Stand next to bed preparing to right click
2: Toggle Wi-Fi switch on/off
3: After the connection to the internet is lost, right click the bed and hold down the right mouse button
4: When the connection is reestablished, the sleeping interface should come up and the animation will start looping
Do I do that whenever, or when the issue shows up again?
Edit: Did it just now.
I should note that the ridiculous amount of zombies was me trying to replicate the issue with lag. It did not work. What I did to replicate was quickly turn my wifi off and then back on so that I did not actually disconnect from the server, while trying to click on the bed the entire time. When my wifi re-established the connection, I was entered into the sleeping loop. Before the connection was re-established, I could not enter the bed nor did the sleeping interface show up.
edit2:
Removed crash report from modded client and replaced with vanilla. It's also shorter since I killed the horde of ~400 zombies I had spawned in.
Per my edit, I was able to reproduce the issue by quickly toggling my wifi switch while right clicking on the bed. As soon as the connection was reestablished, I was able to successfully right click the bed. The sleeping interface came up, and the sleeping animation kept looping in the background. No matter how long you wait, nothing happens. You can leave the bed and reenter it to pass the night. This seems to be due to connection issues between the server and the client, where the client is allowed to sleep but the server doesn't see it or something along those lines.
Forgot I had optifine on there, switching to vanilla now. I did see this issue before I installed optifine. I do not think it is related to the zombie lag, as the zombies I spawned did not cause any fps drop for me.
Edit:
I replaced the crash report with the vanilla one. I was able to reproduce with the same steps on the vanilla client.
Using /gamerule doDaylightCycle set to false, it is only possible to sleep when /time is set between 12540 (exclusive) and 23459 (exclusive). Since /time set night sets the time to 12500, it's not possible to sleep if doDaylightCycle is false, and you have to wait a few seconds to sleep otherwise. It would be better if /time set night used a different value, say 12550.
I see this happen on occasion. The old launcher had an issue with this as well, it's not just the new launcher.
@Markku
I just set up that test, and ran it in the server for 1.6.4 and 13w39b. Same zombies (probably anywhere between 25-40), walled in and not walled in. Ran the server and client both on the same laptop.
1.6.4:
Walls enclosed: 10-25%
Visual Slowdowns: No
Walls opened: 35-60%
Visual Slowdowns: Yes
13w39b:
Walls enclosed: 8-15%
Visual Slowdowns: No
Walls opened: 20-35%
Visual Slowdowns: No
So I guess there is still some CPU hogging, but it is not nearly intensive as it was before. Also, I got zero visual lag of any sort with the snapshot. (You know, aside from my computer running low on memory because I forgot to close Firefox while running both server and client. Closed Firefox, switched render distance to just a few chunks, ran tests again. Exact same results, but no memory slowdowns.)