mirror of
https://github.com/MobileGL-Dev/MobileGL
synced 2026-09-08 04:08:32 +09:00
[Feat] (DirectGLES): implement transform feedback capture
Transform feedback was frontend-only on DirectGLES: glBeginTransformFeedback just flipped MobileGL's own capture state and the real ES driver was never told to capture anything, so every capture buffer read back as whatever it held before the draw (zeros for a fresh glBufferData(NULL)). DirectVulkan drives its capture from its own draw recording, so the shared GLFunctionsTable had no entries for the span at all. Capture now runs on the real driver: - The backend program declares the capture set with glTransformFeedbackVaryings before it links. SPIRV-Cross keeps user output names verbatim in the transpiled ESSL, so the frontend's requested names carry over unchanged. - New GLFunctionsTable Begin/EndTransformFeedback entries hand the span boundaries to the backend (null for DirectVulkan, which is unaffected). - The driver-side begin is deferred to the first draw of the span: ES needs the capturing program current and the capture buffers bound, and both only become true once PrepareForDraw has run. A span that never draws never touches the driver, which is what the GL semantics amount to anyway. - The end mirrors the captured ranges back into the frontend buffer shadows - the GPU wrote them behind the frontend's back, so MapBuffer/GetBufferSubData would otherwise still return the pre-draw bytes. Takes KHR-GL32.transform_feedback from 13/21 to 19/21; the two remaining failures are the geometry-amplified primitive queries, which still go through the frontend's CPU accounting.
This commit is contained in:
@@ -945,6 +945,11 @@ namespace MobileGL::MG_Backend::DirectGLES {
|
||||
funcsTable.GL.IsQueryResultAvailable = IsQueryResultAvailable;
|
||||
funcsTable.GL.GetQueryResult64 = GetQueryResult64;
|
||||
funcsTable.GL.DeleteBackendQuery = DeleteBackendQuery;
|
||||
// Transform feedback is captured by the real ES driver rather than
|
||||
// reconstructed from the draw recording, so the frontend has to hand the
|
||||
// span boundaries over.
|
||||
funcsTable.GL.BeginTransformFeedback = XfbImpl::BeginTransformFeedback;
|
||||
funcsTable.GL.EndTransformFeedback = XfbImpl::EndTransformFeedback;
|
||||
funcsTableInitialized = true;
|
||||
}
|
||||
return funcsTable;
|
||||
|
||||
Reference in New Issue
Block a user