i had not looked at the server for a few days. all was fine 3 days ago. when i looked today im getting this error non stop. i have restarted the the unity server and have tried rebooting the physical machine as well. after restart the error doesnt start until a player logs in.
Unable to create chunk part!
- james1bow
- Thread is marked as Resolved.
A new update is now available, introducing seasons and more!
-
-
Sorry for the late response! This error basically shows up if it takes "too long" to generate the chunks that were requested by a client. Chunk creation has to happen synchronized, and if another thread holds the lock on the chunk list for too long (because it takes too long to generate the chunks), this message occurs.
This mostly happens if a client spawns in a new area which hasn't been loaded before since server restart (once a chunk has been generated, it's stored in the cache until next restart, so chunk requests can be processed a lot faster). The higher the view distance of the client, the worse it gets. And it also depends a bit on the speed of the CPU and the hard drive of the server (the server benefits from an SSD in this case).
Having said that, this error is basically harmless (more or less) It will cause the client to request the chunk(s) again with a small delay, so in the worst case, it slows down world generation for this client a bit. It's still a bit annoying if it shows up frequently in the log, so we'll see if we can improve this part (e.g. increase the timeout threshold or speed up chunk generation in general)
-
Sorry for the late response! This error basically shows up if it takes "too long" to generate the chunks that were requested by a client. Chunk creation has to happen synchronized, and if another thread holds the lock on the chunk list for too long (because it takes too long to generate the chunks), this message occurs.
This mostly happens if a client spawns in a new area which hasn't been loaded before since server restart (once a chunk has been generated, it's stored in the cache until next restart, so chunk requests can be processed a lot faster). The higher the view distance of the client, the worse it gets. And it also depends a bit on the speed of the CPU and the hard drive of the server (the server benefits from an SSD in this case).
Having said that, this error is basically harmless (more or less) It will cause the client to request the chunk(s) again with a small delay, so in the worst case, it slows down world generation for this client a bit. It's still a bit annoying if it shows up frequently in the log, so we'll see if we can improve this part (e.g. increase the timeout threshold or speed up chunk generation in general)
thanks, ill stop watching the server console now! lol. the machine dual x5677 with 64 gb ram an a samsung 850 pro.
Participate now!
Don’t have an account yet? Create a new account now and be part of our community!