Time Nick Message 01:33 MTDiscord maybe 2 bugs, or just one bug here with this mapgen multithreaded thing. Looks like the same mapchunk is called for mapgen twice - maybe we're literally double generating sometimes 01:39 MTDiscord oh and if you breakpoint while the first of the group and second of the group are generating, our thread pool get's another 2 lined up to tackle it. So literally 4 of the same mapgen chunk generation occuring right now.... So need to figure out why... even if intentional.... seems unintentional 01:43 MTDiscord (oh and for the record, making biome generation go +- y direction did have a large effect on fixing the issue, but doesn't resolve the core problem - instead it nearly masks it completely, but not quite. 01:59 MTDiscord Darn it, my brain is going to mush trying to understand our thread pool and emerge logic for he first time. I'll just keep focusing on masking the "issue". Getting biome generation to go +-1 Y did get most of the issue. The remaining one(s) are less repeatable with that fix in though so it'll take longer to hunt/mask it 02:41 MTDiscord hurm, this is all due to overgenerated terrain. what if I just set that back to contentIgnore..... 02:52 MTDiscord oooh, that might be the solution!! just set that overgenerated +1 -1 Y layers to CONTENT_IGNORE again. works for mapgenV7, let's try some others 03:10 MTDiscord Excellent. 03:22 MTDiscord Woohoo, okay branch and PR are up: https://github.com/luanti-org/luanti/pull/16224 09:54 sfan5 maybe 2 bugs, or just one bug here with this mapgen multithreaded thing. Looks like the same mapchunk is called for mapgen twice - maybe we're literally double generating sometimes 09:54 sfan5 same issue as here https://irc.luanti.org/luanti/2025-05-28? 10:52 MTDiscord Yes, aware that may be the case. Did some research, from what I understand, when we overgenerate chunks, they overlap by an entire mapblock +-1 node in the Y direction, correct? That is all my issue was from testing. That said, I did get 4 hits in the same node spot instead of 2 when using breakpoints to slow the system down really badly, so there's definitely a chance of double generation somewhere in there. 10:53 MTDiscord But, it wasn't relevant to the y slice issue, it would be a separate bugfix 23:44 Guest72 Feature request:option in Touchscreen settings to show Aux1 button when "Virtual joystick triggers Aux1 button" enabled. Why:sometimes i need to use Aux1 button without moving but i don't have Aux1 button because virtual_joystick_triggers_aux1 enabled