GAPID is a collection of tools that allows you to inspect, tweak and replay calls from an application to a graphics driver.
GAPID can trace any Android debuggable application, or if you have root access to the device any application can be traced. GAPID can also trace any Desktop Vulkan application.
|
|
|
|
GAPID is still in development but already can be used to debug many Android OpenGL ES and Vulkan applications.
The UI runs on Windows, Linux and MacOS and can currently be used to trace GLES on Android as well as Vulkan on Windows, Linux and Android. We also plan to be able to trace OpenGL ES applications on hosts that support the API.
Pre-release downloadable binaries can be found here.
Detailed current status for Vulkan can be found here.
See Building GAPID.
| Windows | MacOS / Linux |
|---|---|
cd %GOPATH%\src\github.com\google\gapid |
cd $GOPATH/src/github.com/google/gapid |
GAPID consists of the following sub-components:
gapii: Graphics API Interceptor
A layer that sits between the application / game and the GPU driver, recording all the calls and memory accesses.
gapis: Graphics API Server
A process that analyses capture streams reporting incorrect API usage, processes the data for replay on various target devices, and provides an RPC interface to the client.
gapir: Graphics API Replay daemon
A stack-based VM used to playback capture files, imitating the original application’s / game's calls to the GPU driver. Supports read-back of any buffer / framebuffer, and provides profiling functionality.
gapic: Graphics API Client
The frontend user interface application. Provides visual inspection of the capture data, memory, resources, and frame-buffer content.
gapil: Graphics API Language
A new domain specific language to describe a graphics API in its entirety. Combined with our template system to generate huge parts of the interceptor, server and replay systems.
The GAPII, GAPIS, GAPIR and GAPIC components can all run on different (or the same) device, allowing for distrubuted workflows.