While I have had all the same issues mentioned here, especially the placing block lag and visual glitches, the two points where this is most noticeable is in the nether and while on a boat. The nether tends to have very bad freezes that occur, seemingly randomly, which have lasted anywhere from 30 seconds to an upwards of 120 seconds. While on a boat, chunks will stop loading, and few sporadic chunks will load every 1 to 2 minutes. I am able to boat a few blocks past the last loaded chunk, then I run into an invisible wall until it loads. I do not have an elytra on this world at this point, but I would imagine it would be much the same as the boat, which, for obvious reasons, would be far more dangerous.
I am trying to keep to factual statements in this comment, but it is difficult considering we are nearing in on a full version's worth of updates, and the last time anything about this was addressed was when this was reopened because the 1.18 update that was supposed to fix this did not. Hopefully this information above will help, but at very least, I am trying to add another voice so this eventually gets fixed, hopefully sooner than later.
raccoonwounds13
While I have had all the same issues mentioned here, especially the placing block lag and visual glitches, the two points where this is most noticeable is in the nether and while on a boat. The nether tends to have very bad freezes that occur, seemingly randomly, which have lasted anywhere from 30 seconds to an upwards of 120 seconds. While on a boat, chunks will stop loading, and few sporadic chunks will load every 1 to 2 minutes. I am able to boat a few blocks past the last loaded chunk, then I run into an invisible wall until it loads. I do not have an elytra on this world at this point, but I would imagine it would be much the same as the boat, which, for obvious reasons, would be far more dangerous.
I am trying to keep to factual statements in this comment, but it is difficult considering we are nearing in on a full version's worth of updates, and the last time anything about this was addressed was when this was reopened because the 1.18 update that was supposed to fix this did not. Hopefully this information above will help, but at very least, I am trying to add another voice so this eventually gets fixed, hopefully sooner than later.