It seems like about half of the chunks between the edge of render distance and the player aren't getting rendered, leaving these QR-esque holes in the map.
#[1.19.2] Missing Chunks on map
limber heath
vital estuaryBOT
Thank you! Please provide any errors you are experiencing and upload your configuration.txt. Someone from our <@&1086854037040812224> team will respond to help shortly. As a general reminder, everyone on our support team is a volunteer, please be kind!
limber heath
[FYI, the dynmap version is 3.5].
vital estuaryBOT
Configuration.txt link: https://pastebin.com/CRcL6BQi
vital estuaryBOT
Configuration.txt link: https://pastebin.com/CRcL6BQi
loud furnace
Are the chunks there when you zoom in?
limber heath
No, unfortunately
My friend's on there right now too. He walked straight through one of the "void spaces" and it didn't update at all.
Nether seems to be behaving similarly.
loud furnace
Walking doesn't update it, only block update, chunk-generate and chunk-populate do
So maybe try the forge generator to see if that works
limber heath
Using /forge generate for 4000 chunks didn't update the map at all. I will check in a bit if entering the world after having done so has any influence.
loud furnace
If not, try a fullrender of said map
limber heath
Fullrender appears to be clearing it up. Also, it seems like me having generated 4000 chunks is taking a pretty hefty strain on the server's CPU. Is that normal or do you think that's something else? If it is because of that, is there a way to reverse it?
loud furnace
the generation itself is quite resource heavy, both the chunk and tile generation, after a fullrender is completed the process usage should die down again
limber heath
It was pretty high before I even started the fullrender.
Like, floating around 100% for just me on it
loud furnace
maybe dynmap found the chunkgenerate trigger and started rendering it
limber heath
But once it's actually done generating it should go back to normal?
loud furnace
it should, what is the output of /dynmap stats?
loud furnace
yeah its processing the queue, keep an eye on the size, and if it is 0 + 0 the usage should die down
limber heath
Okie dokie
Does having that many chunks generated put any strain on memory or just storage
loud furnace
memory no, as per player the loaded amount is the same
limber heath
Oh, I see
I will let you know if I'm having performance problems when it's done
The only thing I could think it would be is that I aborted the chunk generation some ways through by stopping the server because the whole thing was really slowing down.
But I doubt it.
loud furnace
that would be really bad coding if that would be the case
limber heath
I know right? lmao
limber heath
Queue is 0+0 and CPU still reads 120%
limber heath
You mean that?
Got it. It was Dynmap. The queue said zero but it was still running that much, I guess.
Feel free to close this ticket.
Thanks for the assistance!
loud furnace
Got it. It *was* Dynmap. The queue said zero but it was still running that much,...
Odd, maybe it was still rendering some zoomouts or sth
vital estuaryBOT
This support thread has been archived due to inactivity. Click the button below to reopen it.
vital estuaryBOT
This support thread has been archived due to inactivity. Click the button below to reopen it.
vital estuaryBOT
This support thread has been archived due to inactivity. Click the button below to reopen it.
vital estuaryBOT
This support thread has been archived due to inactivity. Click the button below to reopen it.
vital estuaryBOT
This support thread has been archived due to inactivity. Click the button below to reopen it.