Frames Map 3D

v1.0.11 — Framed maps are no longer misaligned with their frame

Fix

• 3D maps no longer render detached from their item frame. Broken since 1.0.10: the new persistent GPU geometry cache bakes vertices in map-local space and drew them using the frame's pose as the model-view matrix, but that pose only carries the frame's camera-relative position and rotation. The camera orientation lives in RenderSystem's own model-view stack (the frustum matrix LevelRenderer pushes before rendering entities), not in the entity's PoseStack, so it was silently dropped — the terrain was drawn aligned to the world axes instead of to the frame, which made it slide across the screen whenever you moved or turned the camera. Draws now compose the full matrix (RenderSystem.getModelViewMatrix() × the frame's pose), which is exactly what vanilla does implicitly by baking the pose into the vertices and reusing RenderSystem's matrix.

Notes

• Client rendering only; server-side capture and the network payload format are unchanged.
• Cost is one Matrix4f per visible map per frame — negligible next to the CPU geometry rebuild the cache already removed in 1.0.10.
• Requires 1.0.11 or newer; 1.0.10 renders framed 3D maps incorrectly.

JAR: frames_map_3d-1.21.1-neoforge-21.1.249-1.0.11.jar

Tag: 1.21.1-neoforge-1.0.11