Skip to content

Instantly share code, notes, and snippets.

@Popov72

Popov72/using_pix_with_canary.md

Last active April 12, 2025 19:25
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save Popov72/41f71cbf8d55f2cb8cae93f439eee347 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save Popov72/41f71cbf8d55f2cb8cae93f439eee347 to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. Popov72 revised this gist Dec 26, 2023. No changes.
  2. Popov72 revised this gist Oct 16, 2023. 1 changed file with 4 additions and 5 deletions.
    9 changes: 4 additions & 5 deletions using_pix_with_canary.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,23 +1,22 @@
    In PIX, **Select Target Process** => **Launch Win32** and set the following 2 entries according to where Canary is installed:
    In PIX, **Select Target Process** => **Launch Win32** and set the following 2 entries according to where Canary / Chrome is installed:
    * Path to executable: **"C:\Users\alexis\AppData\Local\Google\Chrome SxS\Application\chrome.exe"**
    * Working directory: **"C:\Users\alexis\AppData\Local\Google\Chrome SxS\Application\"**
    * Command line arguments: **--disable-gpu-sandbox --disable-direct-composition**
    * You can add those arguments if you want to be able to see the disassembled shader code: **--enable-dawn-features=emit_hlsl_debug_symbols,disable_symbol_renaming**
    * You may also need to enable WebGPU support through the command line: **--enable-unsafe-webgpu**
    * **Launch Suspended** unchecked, **Launch for GPU capture** and **Force D3D11On12** checked

    Then click on "Launch".

    **Important**: you should close all your Canary windows/processes before clicking on the "Launch" button!
    **Important**: you should close all your Canary / Chrome windows/processes before clicking on the "Launch" button!

    To Capture a frame (**GPU Capture** frame):
    * Choose **Present-to-Present**
    * Click on the **Capture** icon
    * If the capture does not work, try to set 2 frames for the **Capture frame count** value: at some point I had to set 2 here, 1 did not work...
    * You probably need to set **Capture frame count** to 2 (I had to), otherwise the capture won't contain your commands, only those of Canary / Chrome
    * If you do other captures you can get an "An error occurred during capture" popup: just close it, the capture does work (at least it works for me).

    If you want the debug markers to work inside PIX, you need to perform those steps: [https://dawn.googlesource.com/dawn/+/refs/heads/main/docs/debug_markers.md](https://dawn.googlesource.com/dawn/+/refs/heads/chromium/4479/docs/debug_markers.md)

    Notes:
    * I could not locate the *libdawn_native.dll* file: I have simply copied the *WinPixEventRuntime.dll* file into **"C:\Users\alexis\AppData\Local\Google\Chrome SxS\Application\<version>\"** and it did work
    * If you update Canary, this file will be removed, you will have to copy it again
    * If you update Canary / Chrome, this file will be removed, you will have to copy it again
  3. Popov72 revised this gist Jun 11, 2023. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion using_pix_with_canary.md
    View file
    Original file line number Diff line number Diff line change
    @@ -16,7 +16,7 @@ To Capture a frame (**GPU Capture** frame):
    * If the capture does not work, try to set 2 frames for the **Capture frame count** value: at some point I had to set 2 here, 1 did not work...
    * If you do other captures you can get an "An error occurred during capture" popup: just close it, the capture does work (at least it works for me).

    If you want the debug markers to work inside PIX, you need to perform those steps: https://dawn.googlesource.com/dawn/+/refs/heads/main/docs/debug_markers.md
    If you want the debug markers to work inside PIX, you need to perform those steps: [https://dawn.googlesource.com/dawn/+/refs/heads/main/docs/debug_markers.md](https://dawn.googlesource.com/dawn/+/refs/heads/chromium/4479/docs/debug_markers.md)

    Notes:
    * I could not locate the *libdawn_native.dll* file: I have simply copied the *WinPixEventRuntime.dll* file into **"C:\Users\alexis\AppData\Local\Google\Chrome SxS\Application\<version>\"** and it did work
  4. Popov72 revised this gist May 17, 2023. 1 changed file with 0 additions and 6 deletions.
    6 changes: 0 additions & 6 deletions using_pix_with_canary.md
    View file
    Original file line number Diff line number Diff line change
    @@ -21,9 +21,3 @@ If you want the debug markers to work inside PIX, you need to perform those step
    Notes:
    * I could not locate the *libdawn_native.dll* file: I have simply copied the *WinPixEventRuntime.dll* file into **"C:\Users\alexis\AppData\Local\Google\Chrome SxS\Application\<version>\"** and it did work
    * If you update Canary, this file will be removed, you will have to copy it again

    --

    Private use, regular Chrome paths:
    * Path to executable: "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"
    * Working directory: "C:\Program Files (x86)\Google\Chrome\Application\"
  5. Popov72 revised this gist Jan 28, 2022. 1 changed file with 1 addition and 0 deletions.
    1 change: 1 addition & 0 deletions using_pix_with_canary.md
    View file
    Original file line number Diff line number Diff line change
    @@ -23,6 +23,7 @@ Notes:
    * If you update Canary, this file will be removed, you will have to copy it again

    --

    Private use, regular Chrome paths:
    * Path to executable: "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"
    * Working directory: "C:\Program Files (x86)\Google\Chrome\Application\"
  6. Popov72 revised this gist Jan 28, 2022. 1 changed file with 2 additions and 1 deletion.
    3 changes: 2 additions & 1 deletion using_pix_with_canary.md
    View file
    Original file line number Diff line number Diff line change
    @@ -19,9 +19,10 @@ To Capture a frame (**GPU Capture** frame):
    If you want the debug markers to work inside PIX, you need to perform those steps: https://dawn.googlesource.com/dawn/+/refs/heads/main/docs/debug_markers.md

    Notes:
    * I could not locate the *libdawn_native.dll* file: I have simply copied the *WinPixEventRuntime.dll* file into **"C:\Users\alexis\AppData\Local\Google\Chrome SxS\Application\88.0.4307.0\"** and it did work
    * I could not locate the *libdawn_native.dll* file: I have simply copied the *WinPixEventRuntime.dll* file into **"C:\Users\alexis\AppData\Local\Google\Chrome SxS\Application\<version>\"** and it did work
    * If you update Canary, this file will be removed, you will have to copy it again

    --
    Private use, regular Chrome paths:
    * Path to executable: "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"
    * Working directory: "C:\Program Files (x86)\Google\Chrome\Application\"
  7. Popov72 revised this gist Jan 28, 2022. 1 changed file with 2 additions and 2 deletions.
    4 changes: 2 additions & 2 deletions using_pix_with_canary.md
    View file
    Original file line number Diff line number Diff line change
    @@ -12,9 +12,9 @@ Then click on "Launch".

    To Capture a frame (**GPU Capture** frame):
    * Choose **Present-to-Present**
    * click on the **Capture** icon
    * Click on the **Capture** icon
    * If the capture does not work, try to set 2 frames for the **Capture frame count** value: at some point I had to set 2 here, 1 did not work...
    * if you do other captures you can get an "An error occurred during capture" popup: just close it, the capture does work (at least it works for me).
    * If you do other captures you can get an "An error occurred during capture" popup: just close it, the capture does work (at least it works for me).

    If you want the debug markers to work inside PIX, you need to perform those steps: https://dawn.googlesource.com/dawn/+/refs/heads/main/docs/debug_markers.md

  8. Popov72 revised this gist Jan 28, 2022. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion using_pix_with_canary.md
    View file
    Original file line number Diff line number Diff line change
    @@ -6,7 +6,7 @@ In PIX, **Select Target Process** => **Launch Win32** and set the following 2 en
    * You may also need to enable WebGPU support through the command line: **--enable-unsafe-webgpu**
    * **Launch Suspended** unchecked, **Launch for GPU capture** and **Force D3D11On12** checked

    Then click on "Launch" => dismiss the popup with the "GPU starting pid" value
    Then click on "Launch".

    **Important**: you should close all your Canary windows/processes before clicking on the "Launch" button!

  9. Popov72 revised this gist Jan 28, 2022. 1 changed file with 1 addition and 0 deletions.
    1 change: 1 addition & 0 deletions using_pix_with_canary.md
    View file
    Original file line number Diff line number Diff line change
    @@ -3,6 +3,7 @@ In PIX, **Select Target Process** => **Launch Win32** and set the following 2 en
    * Working directory: **"C:\Users\alexis\AppData\Local\Google\Chrome SxS\Application\"**
    * Command line arguments: **--disable-gpu-sandbox --disable-direct-composition**
    * You can add those arguments if you want to be able to see the disassembled shader code: **--enable-dawn-features=emit_hlsl_debug_symbols,disable_symbol_renaming**
    * You may also need to enable WebGPU support through the command line: **--enable-unsafe-webgpu**
    * **Launch Suspended** unchecked, **Launch for GPU capture** and **Force D3D11On12** checked

    Then click on "Launch" => dismiss the popup with the "GPU starting pid" value
  10. Popov72 revised this gist Oct 4, 2021. 1 changed file with 2 additions and 2 deletions.
    4 changes: 2 additions & 2 deletions using_pix_with_canary.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,8 +1,8 @@
    In PIX, **Select Target Process** => **Launch Win32** and set the following 2 entries according to where Canary is installed:
    * Path to executable: **"C:\Users\alexis\AppData\Local\Google\Chrome SxS\Application\chrome.exe"**
    * Working directory: **"C:\Users\alexis\AppData\Local\Google\Chrome SxS\Application\"**
    * Command line arguments: **--disable-gpu-sandbox --gpu-startup-dialog --disable-direct-composition**
    * maybe it would work without *--gpu-startup-dialog* but it works with so I didn't bother checking!
    * Command line arguments: **--disable-gpu-sandbox --disable-direct-composition**
    * You can add those arguments if you want to be able to see the disassembled shader code: **--enable-dawn-features=emit_hlsl_debug_symbols,disable_symbol_renaming**
    * **Launch Suspended** unchecked, **Launch for GPU capture** and **Force D3D11On12** checked

    Then click on "Launch" => dismiss the popup with the "GPU starting pid" value
  11. Popov72 revised this gist Apr 23, 2021. 1 changed file with 2 additions and 0 deletions.
    2 changes: 2 additions & 0 deletions using_pix_with_canary.md
    View file
    Original file line number Diff line number Diff line change
    @@ -7,6 +7,8 @@ In PIX, **Select Target Process** => **Launch Win32** and set the following 2 en

    Then click on "Launch" => dismiss the popup with the "GPU starting pid" value

    **Important**: you should close all your Canary windows/processes before clicking on the "Launch" button!

    To Capture a frame (**GPU Capture** frame):
    * Choose **Present-to-Present**
    * click on the **Capture** icon
  12. Popov72 revised this gist Oct 31, 2020. 1 changed file with 3 additions and 1 deletion.
    4 changes: 3 additions & 1 deletion using_pix_with_canary.md
    View file
    Original file line number Diff line number Diff line change
    @@ -15,7 +15,9 @@ To Capture a frame (**GPU Capture** frame):

    If you want the debug markers to work inside PIX, you need to perform those steps: https://dawn.googlesource.com/dawn/+/refs/heads/main/docs/debug_markers.md

    Note that I could not locate the *libdawn_native.dll* file: I have simply copied the file into **"C:\Users\alexis\AppData\Local\Google\Chrome SxS\Application\88.0.4307.0\"** and it did work
    Notes:
    * I could not locate the *libdawn_native.dll* file: I have simply copied the *WinPixEventRuntime.dll* file into **"C:\Users\alexis\AppData\Local\Google\Chrome SxS\Application\88.0.4307.0\"** and it did work
    * If you update Canary, this file will be removed, you will have to copy it again

    Private use, regular Chrome paths:
    * Path to executable: "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"
  13. Popov72 revised this gist Oct 29, 2020. 1 changed file with 4 additions and 0 deletions.
    4 changes: 4 additions & 0 deletions using_pix_with_canary.md
    View file
    Original file line number Diff line number Diff line change
    @@ -13,6 +13,10 @@ To Capture a frame (**GPU Capture** frame):
    * If the capture does not work, try to set 2 frames for the **Capture frame count** value: at some point I had to set 2 here, 1 did not work...
    * if you do other captures you can get an "An error occurred during capture" popup: just close it, the capture does work (at least it works for me).

    If you want the debug markers to work inside PIX, you need to perform those steps: https://dawn.googlesource.com/dawn/+/refs/heads/main/docs/debug_markers.md

    Note that I could not locate the *libdawn_native.dll* file: I have simply copied the file into **"C:\Users\alexis\AppData\Local\Google\Chrome SxS\Application\88.0.4307.0\"** and it did work

    Private use, regular Chrome paths:
    * Path to executable: "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"
    * Working directory: "C:\Program Files (x86)\Google\Chrome\Application\"
  14. Popov72 created this gist Sep 30, 2020.
    18 changes: 18 additions & 0 deletions using_pix_with_canary.md
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,18 @@
    In PIX, **Select Target Process** => **Launch Win32** and set the following 2 entries according to where Canary is installed:
    * Path to executable: **"C:\Users\alexis\AppData\Local\Google\Chrome SxS\Application\chrome.exe"**
    * Working directory: **"C:\Users\alexis\AppData\Local\Google\Chrome SxS\Application\"**
    * Command line arguments: **--disable-gpu-sandbox --gpu-startup-dialog --disable-direct-composition**
    * maybe it would work without *--gpu-startup-dialog* but it works with so I didn't bother checking!
    * **Launch Suspended** unchecked, **Launch for GPU capture** and **Force D3D11On12** checked

    Then click on "Launch" => dismiss the popup with the "GPU starting pid" value

    To Capture a frame (**GPU Capture** frame):
    * Choose **Present-to-Present**
    * click on the **Capture** icon
    * If the capture does not work, try to set 2 frames for the **Capture frame count** value: at some point I had to set 2 here, 1 did not work...
    * if you do other captures you can get an "An error occurred during capture" popup: just close it, the capture does work (at least it works for me).

    Private use, regular Chrome paths:
    * Path to executable: "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"
    * Working directory: "C:\Program Files (x86)\Google\Chrome\Application\"