Admin ADMIN
2026.08.05
AdminBug reports 23Suggestions 4Exploits 0Confirmed and fixed. Good diagnosis - the waypoints being there while the map is not is exactly what was happening.
Everything in that window except the painting is already in memory: the frame, the spots, the markers, the tooltips. The region art itself is packed separately and was only fetched when you FIRST opened the window - one chunk of a ~19MB set - so the window rendered complete except for the one thing it is actually about.
It now fetches the current region's painting when you enter a map, in the background, so by the time you press the world-map key it is already there. It also warms the continent page one click up. It is queued behind the map's own art so it never competes with the field you are standing in, and if you do beat it to the punch you just get today's behaviour rather than anything worse.
(On the dev branch - it will be in the next published build, not v32.)
Everything in that window except the painting is already in memory: the frame, the spots, the markers, the tooltips. The region art itself is packed separately and was only fetched when you FIRST opened the window - one chunk of a ~19MB set - so the window rendered complete except for the one thing it is actually about.
It now fetches the current region's painting when you enter a map, in the background, so by the time you press the world-map key it is already there. It also warms the continent page one click up. It is queued behind the map's own art so it never competes with the field you are standing in, and if you do beat it to the punch you just get today's behaviour rather than anything worse.
(On the dev branch - it will be in the next published build, not v32.)