Using RenderDoc with Browser

1. Download and install RenderDoc Meta Fork on your PC.
2. In your Quest device, launch the browser and navigate to chrome://flags.
3. Use the search bar on the page to search for “Image”.
4. Toggle the Android ImageReader flag to Disabled.
5. After changing the flags, you’ll see a banner at the bottom of the browser. Click the “Relaunch” button.
6. Extra step if you need to work with Immersive mode:
   1. Use the search bar to search for “RenderDoc”.
   2. Toggle the RenderDoc Immersive Mode Support flag to Enabled.
   3. Click the “Relaunch” button.

1. On your PC, launch the RenderDoc Meta Fork application.
2. In the bottom-left corner of the RenderDoc UI, click Replay Context: (something) and select Meta Quest 2 Profiling Mode.
3. At this point, your Quest device should turn black with 3 white dots. Press the home button on your Quest controller to go back to the Home environment.
4. In the RenderDoc Launch Application panel, type com.oculus.browser/.PanelActivity in the Executable Path field, and click the Launch button.
5. The browser should launch with RenderDoc connected. Navigate to the page and view you want to capture, and use the RenderDoc app on your computer to capture a frame.

1. Manually launch the browser in your Quest device. You should see the RenderDoc overlay drawn on top of the browser.
2. In the RenderDoc UI, click the File menu, then click Attach to Running Instance.
3. You should see com.oculus.browser in the list.
4. Select com.oculus.browser and click the Connect to App button.

1. You should still be connected to your device. If not, set the Replay Context to Meta Quest headset. In the bottom-left corner of the RenderDoc UI, click Replay Context: (something) and select Meta Quest 2 Profiling Mode.
2. Double-click the capture to view. You are now replaying the capture on the Quest GPU.
3. In the Event Browser window, you can see each draw call that was made during your frame capture. Clicking each one lets you inspect the state of the entire rendering pipeline at the time of that call.
4. The Texture Viewer tab shows the frame buffer as you click the various calls.
   • It may display very darkly. To display with more brightness, toggle the gamma button to the left of the Subresource label that is near the top of the Texture Viewer pane.
   • In general, the rendering here is not completely accurate, but it serves as a good guide for what’s going on in each draw call.
   • Consider setting the Overlay option to Wireframe Mesh or Highlight Draw Call to identify what object is being rendered.
5. Open the Performance Counter Viewer tab and press the Capture Counters button. There are a variety of metrics here, including a couple of generic ones, and a bunch of Meta specific ones. The Meta specific metrics are described in the Draw Call Metrics topic.
   • Sorting by GPU Duration or Clocks is a great way to identify the most expensive draw calls in your scene. These timings may not be entirely accurate in terms of the actual duration when rendering the scene every frame, but they are accurate relative to one another. For example, a 1000 microsecond call is about twice as costly as a 500 microsecond call.
   • You can map the event identifiers (EIDs) in the Performance Counter Viewer window to the EIDs in the Event Browser.
6. The Pipeline State tab shows the entire state of the graphics pipeline for whatever draw call is selected in the Event Browser. To view more information about a specific stage, click the different boxes in the pipeline.