I do not think it is the PC specs, we are experiencing the same issues and they seem to be syncing across everyone on the server. This ranges from quite top-end, new machines to work desktops/laptops without any 3rd party graphics cards.
EDIT: Not sure of full server specs, but we are running on a 6Gig RAM virtual hosted server hosted by GameServers, with only up to around 5 people online concurrently at maximum.
I haven't done extensive testing, but I think a the below points are correct:
The fix of clearing the cache works, but is not a permanent fix, the problems reappear after a period.
The area around spawn does not seem to have the issue at any stage, I am guessing because the chunks do not load/unload constantly?
My (underground) base area (41,95,-280 in the above world backup), away from spawn , is where I am noticing the problem.
If I log out for longer than approximately 5 minutes while in the base, when I log in it seems the entire base gets affected by the lighting glitch about half the time (seems random but I have not been monitoring closely).
If I log out while at spawn, even for long periods, and then fly to my base on logging in, it seems to not be affected (if it was working on logout).
Once a chunk is affected it seems to be affected until I reset the lighting by placing/breaking a torch. This "semi" resets the lighting in a 6-10 block radius (some of the blocks still seem slightly underlit until I place a torch).
If I place a torch in an affected area next to crops, the crops break when the torch is placed.
The blocks are definitely reading as light=0, it does not seem to be just a render issue.
The server light field is not showing any value, except for the block and sky lights shown in parentheses, not sure if this is normal behavior.
I believe (although again I have not specifically tested) that if someone else has been on the server between me logging off and back on, that there is a higher chance of the bug materializing in my base when I log in.
Tim Craven
I do not think it is the PC specs, we are experiencing the same issues and they seem to be syncing across everyone on the server. This ranges from quite top-end, new machines to work desktops/laptops without any 3rd party graphics cards.
EDIT: Not sure of full server specs, but we are running on a 6Gig RAM virtual hosted server hosted by GameServers, with only up to around 5 people online concurrently at maximum.
World backup: https://www.dropbox.com/s/zw39ogah5dit6zh/world.zip?dl=0
I haven't done extensive testing, but I think a the below points are correct:
The fix of clearing the cache works, but is not a permanent fix, the problems reappear after a period.
The area around spawn does not seem to have the issue at any stage, I am guessing because the chunks do not load/unload constantly?
My (underground) base area (41,95,-280 in the above world backup), away from spawn , is where I am noticing the problem.
If I log out for longer than approximately 5 minutes while in the base, when I log in it seems the entire base gets affected by the lighting glitch about half the time (seems random but I have not been monitoring closely).
If I log out while at spawn, even for long periods, and then fly to my base on logging in, it seems to not be affected (if it was working on logout).
Once a chunk is affected it seems to be affected until I reset the lighting by placing/breaking a torch. This "semi" resets the lighting in a 6-10 block radius (some of the blocks still seem slightly underlit until I place a torch).
If I place a torch in an affected area next to crops, the crops break when the torch is placed.
The blocks are definitely reading as light=0, it does not seem to be just a render issue.
The server light field is not showing any value, except for the block and sky lights shown in parentheses, not sure if this is normal behavior.
I believe (although again I have not specifically tested) that if someone else has been on the server between me logging off and back on, that there is a higher chance of the bug materializing in my base when I log in.
Hope this info helps. 🙂