How to reproduce:
1. Install and set up RenderDoc
2. Open the attached “IN-106167” project with command line argument “-load-renderdoc -force-gles“
3. Open the “TerminalScene“ and open the Game view
4. Press the camera icon in the Game view toolbar to capture the frame
5. Open the capture file in RenderDoc by double clicking the image
6. In the Event Browser, navigate to FrameTime.GPU > UIR.DrawChain > UniversalRenderPipeline.RenderSingleCameraInternal: MainCamera > ScriptableRenderer.Execute: PC_High_Renderer > DrawOpaqueObjects > RenderLoop.DrawSRPBatcher > glDrawElements(*any number*)
7. Open the Mesh Viewer (Window > Mesh Viewer) and view the VS Output
8. Observe the result
9. Open the Pipeline State (Window > Pipeline State) and click on the “FB” button to view the Framebuffer Output
10. Observe the result

Expected result: VS Output and Framebuffer Output has valid data
Actual result: VS Output and Framebuffer Output has no data

Reproducible with: 2022.2.14f1, 2022.3.64f1, 6000.0.52f1, 6000.1.11f1, 6000.2.0b9, 6000.3.0a1
Could not test with: 2022.1.0a1, 2022.2.13f1 (5f5de2657605) )(Unable to view the necessary frame data due to material issues from downgrading)

Reproduced on: Windows 11
Not reproduced on: No other environment tested

Notes:
- Tested with RenderDoc v 1.39 and OpenGLES 3.2
- Issue also happens when OpenGLES is manually set in the Player settings
- Issue does not happen with OpenGLCore