Why would anyone do this? I have been playing around with WebGPU recently, writing a toy engine in JS and running it on Chrome. The debugging situation is great now, PIX just works and I can usually identify and fix issues quickly when they arise. However, when it comes to profiling, well the situation is not that great. For instance, AMD’s Radeon Developer Panel will detect Chrome as a DX12 app (when using the proper flags), it will attach to the process and even let me start a capture.
Fast Forward If you’ve read the article already and/or want to jump straight to profiling, go to the TL;DR section. Context WebGPU is not a native graphics API, as in no hardware vendor provides specific drivers for their GPUs targeting this API. Instead, WebGPU runtimes like web browsers must implement backends for WebGPU using modern native APIs such as DirectX12, Vulkan or Metal. Those APIs are widely used, in particular for video games, and hardware vendors have developed great profiling tools for them.
Pleased to announce many more speakers for our conference here in Europe later this year: https://www.graphicsprogrammingconference.nl/
If you haven't read the whole list, go now, as I'm super happy that we'll have a Ghost of Tsushima post mortem (and many other great talks)!
If you have a talk idea, please do sign up now as the deadline is approaching fast! We need your talk to make this a success and show that Europe can do graphics!
Put up a page about attaching PIX to Chrome for WebGPU debugging/profiling. Working on similar ones for other major graphics debuggers too.
After 1.5 years at AMD, here is finally my first blog post on GPUOpen 🥳. Let's demystify occupancy together !
Please feel free to reach out if you have questions or comments :)
Here’s another one for your holiday #gamedev reading list 🎁
Have you ever wondered what ‘occupancy’ means? Or how to identify occupancy-limited workloads?
Our new post gives an overview of #occupancy, how to measure it with tools, and ways to improve it.
🎵 On the first day of Gamesmas, my #gamedevs sent to me ...
... the first release of #AMD #FSR3! 🎵
🎁 With a bonus gift of a #UE5 plugin 🎁
https://gpuopen.com/fsr3-source-available/?utm_source=mastodon&utm_medium=social&utm_campaign=fsr3
We are very excited to announce the release of AMD FidelityFX Super Resolution 3 (FSR 3) technology on GPUOpen, complete with full source code for DirectX 12 and Unreal Engine 5.
Looking for tips on working with RGD? Take a look at our Getting Started tutorial? 📕
It shows you how to capture a #GPU crash dump and interpret the analysis file.
Feel free to share feedback here or GitHub for this highly-anticipated release!
https://gpuopen.com/learn/rgd_1_0_tutorial/?utm_source=mastodon&utm_medium=social&utm_campaign=rgd
GPC 2025
Matthäus "Anteru" Chajdas
Brandon Jones
GPUOpen