From 0fa4a98139c8e03a6c1953c8b238fbf7a54db721 Mon Sep 17 00:00:00 2001 From: Swung0x48 Date: Sun, 20 Sep 2026 19:56:27 -0400 Subject: [PATCH] [MG_Backend] drop the invented point count from the handle arm's memo comment The record carries eleven surfaces, but the walk writes the attachment points only - eight colour plus depth and stencil - and the read surface is applied by ApplyReadBufferFromRecord rather than by the walk. Say "the SAME attachment points on it" instead of a count that is wrong for the walk. --- MobileGL/MG_Backend/DirectGLES/Managers.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/MobileGL/MG_Backend/DirectGLES/Managers.h b/MobileGL/MG_Backend/DirectGLES/Managers.h index c3b2bd7f..cf75f73b 100644 --- a/MobileGL/MG_Backend/DirectGLES/Managers.h +++ b/MobileGL/MG_Backend/DirectGLES/Managers.h @@ -2305,8 +2305,8 @@ namespace MobileGL::MG_Backend::DirectGLES { // ONE FOR THE OBJECT, NOT ONE PER TARGET, and that is the difference that matters. // Attachments belong to the driver FBO OBJECT: glFramebufferTexture2D and // glFramebufferRenderbuffer write the object behind whichever binding happens to be - // current, so a walk run for Draw and a walk run for Read write the SAME eleven - // points. Per-target slots let the two keep separate, individually true and jointly + // current, so a walk run for Draw and a walk run for Read write the SAME attachment + // points on it. Per-target slots let the two keep separate, individually true and jointly // false accounts of one physical state: a composite framebuffer synced as DRAW in a // depth pre-pass detaches the points its other attachment state attaches, and the // end-of-frame sync of that same record on the READ side then found its own slot