USAGE:(1)
๐ USAGE:(1) โ the manual page for gfxrecon-capture ๐
okay bestie, listen. this is the manual page for gfxrecon-capture, and it lives in section 1 of the manual (that's the (1) bestie, user commands, the fun section โจ). let's get into it ๐ซถ
๐ธ NAME ๐ธ
gfxrecon-capture โ create a capture of a Vulkan program. that's it, that's the whole job, and she does it flawlessly ๐
โจ DESCRIPTION โจ
so the usage line is literally:
usage: gfxrecon-capture.py [-h]
[-w dir]
[-o captureFile] [-f captureFrames] [--no-file-timestamp]
[--trigger {F1-F12,TAB,CTRL}] [--compression-type
{LZ4,ZLIB,ZSTD,NONE}] [--file-flush] [--log-level
{debug,info,warn,error,fatal}] [--log-file <file>]
[--memory-tracking-mode {page_guard,assisted,unassisted}]
<program> [<programArgs>]
and what does she actually do? Create a capture of a Vulkan program. simple as that. she's the main character, you're just running a program, and she's taking the receipts ๐ธ
๐ positional arguments: ๐
<program> [<program args>]โ the program you wanna capture, and if you want, you can tack the program's arguments on after it too ๐ฆ
๐ optional arguments: ๐
-h,--helpโ shows this help message and dips. classic. iconic. no notes ๐-w <dir>,--working-dir <dir>โ sets the CWD (current working directory, bestie) to this directory before running the program. like moving house but for one process ๐-o <captureFile>,--capture-file <captureFile>โ the name of the capture file. the default?gfxrecon_capture.gfxrโจ-f <captureFrames>,--capture-frames <captureFrames>โ a list of frames to capture. default is all frames โ yes, all of them, she's not shy ๐--no-file-timestampโ don't add a timestamp to the capture file name. sometimes you just want the plain name, and that's valid ๐โ--trigger {F1,F2,F3,F4,F5,F6,F7,F8,F9,F10,F11,F12,TAB,CTRL}โ pick a hotkey that starts and stops the capture. your very own secret combo ๐ฎ--compression-type {LZ4,ZLIB,ZSTD,NONE}โ the type of compression used in the capture file. default is LZ4 ๐๏ธ--file-flushโ flushes the output stream after each packet gets written to the capture file. every. single. packet. commitment ๐ซก--log-level {debug,info,warn,error,fatal}โ the highest level message that gets logged. default is info ๐--log-file logFileโ the name of the log file. want to disable logging entirely? pass an empty string. default is stdout/stderr ๐ชต--memory-tracking-mode {page_guard,assisted,unassisted}โ the method used to track changes to memory mapped objects. here are the three, bestie, read carefully:page_guard: use pageguard to track changes (this is the default) ๐ก๏ธassisted: the application will callvkFlushMappedMemoryRangesfor memory to be written to the capture file ๐unassisted: all mapped memory will be written to the capture file duringVkQueueSubmitandVkUnmapMemory๐ซ
and then the usage block gets repeated at you one more time, because apparently once was not enough, so here it is again in all her glory:
[-w dir]
[-o captureFile] [-f captureFrames] [--no-file-timestamp]
[--trigger {F1-F12,TAB,CTRL}] [--compression-type
{LZ4,ZLIB,ZSTD,NONE}] [--file-flush] [--log-level
{debug,info,warn,error,fatal}] [--log-file <file>]
[--memory-tracking-mode {page_guard,assisted,unassisted}]
<program> [<programArgs>]
๐ฅ SEE ALSO ๐ฅ
the full documentation for usage: is maintained as a Texinfo manual ๐. if the info and usage: programs are properly installed at your site, then this command:
info usage:
should give you access to the complete manual. go forth and read, bestie ๐ง
fr fr, that's the whole page. no cap. ๐
later, legend ๐ซถ โ this page is gfxrecon-capture, dated June 2021, and it says USAGE:(1) up top and gfxrecon-capture + June 2021 + USAGE:(1) at the bottom, which we have now lovingly folded into this sign-off so nothing gets lost ๐โจ๐
๐ฆ where this page comes from
- debian bookworm: gfxreconstruct 0.9.18+dfsg-1 ยท MIT
- ubuntu noble: gfxreconstruct 1.0.2+dfsg-1 ยท MIT
- ubuntu questing: gfxreconstruct 1.0.4+dfsg-1
- ๐ girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms