04-07-2013, 05:18 AM
It happens to everyone, with bigger or lesser severity, depending on computer speed.
My guess is that as soon as MCServer generates a chunk, it sends it to the client, but then the fluid simulator takes over and in its first step simulates several thousand blocks, sends those changes to the client and the client freezes because it recalculates lighting for each block change. To confirm this, if you set both water and lava simulators to Noop, the client should cease freezing (but of course you don't get running water, then).
There are principially two solutions to this:
1, Don't send chunks to client until they've had several steps of fluid simulation
2, Generate chunks (at least) one row ahead of clients and siulate them even when they have zero clients.
#1 is quite difficult to code - there's a lot of housekeeping (this chunk has a client, but don't send block updates to it yet, because the chunk itself hasn't been sent yet)
#2 is easier to code, but means that the server will use more RAM (needs 1 more row of chunks around the player) and CPU (chunks that could be unloaded will still be simulated)
My guess is that as soon as MCServer generates a chunk, it sends it to the client, but then the fluid simulator takes over and in its first step simulates several thousand blocks, sends those changes to the client and the client freezes because it recalculates lighting for each block change. To confirm this, if you set both water and lava simulators to Noop, the client should cease freezing (but of course you don't get running water, then).
There are principially two solutions to this:
1, Don't send chunks to client until they've had several steps of fluid simulation
2, Generate chunks (at least) one row ahead of clients and siulate them even when they have zero clients.
#1 is quite difficult to code - there's a lot of housekeeping (this chunk has a client, but don't send block updates to it yet, because the chunk itself hasn't been sent yet)
#2 is easier to code, but means that the server will use more RAM (needs 1 more row of chunks around the player) and CPU (chunks that could be unloaded will still be simulated)