About 10 years ago (give or take a minute) I made the first commit to the repository that would become RenderDoc. I had no clue at all that it would turn out the way it has, but I'd say the project has been a success so far :).

A request for something I'm working on: Please share with me any captures you have where there's a draw that isn't rendering and you had to figure out why. Maybe badly set state, wrong vertex buffers, incorrect depth clear, any reason as long as the result is "my draw is missing"

FYI for RenderDoc users on Windows & Intel: D3D11 captures might crash on load with v1.2. Updating to latest drivers should fix it for most cases, otherwise use the next nightly build which is essentially v1.2 + a fix.

I'm going to update RenderDoc's README for v1.0 soon (update supported APIs/platforms, retake screenshots, etc). Does anyone think that there's some useful info that's lacking on the landing page? I try to balance useful info with over-saturation github.com/baldurk/renderdoc…

Today is the 5 yr anniversary of the first commit to @RenderDoc I wrote some nostalgic words about the early days: renderdoc.org/renderdoc-hist…

I've posted two docs describing planned changes to RenderDoc's crash reporter and analytics gist.github.com/baldurk/0ff3… gist.github.com/baldurk/4c08…

I've published a write-up with the results of the RenderDoc survey - renderdoc.org/survey Thank you everyone for responding!

Last reminder - I'll close the survey (renderdoc.org/survey) this time next week. Final chance to vote on next features & give feedback!

So far 150 responses to the renderdoc survey renderdoc.org/survey which is great! If you haven't, please take a minute to fill it out :)

PSA: if you're using RenderDoc and you have Raptr installed, disable/blacklist/etc renderdocui.exe. I see a lot of crashes caused by Raptr.

I've emailed Crytek about the broken links on the cryengine renderdoc page Latest builds are always up here renderdoc.org/builds &github

FYI: Latest AMD 14.12 drivers have fixed a long-standing 100% crash in renderdoc when stream-out'ing a tessellated draw for the mesh output.

Python integration in RenderDoc :) github.com/baldurk/renderdoc… it's a bit rough right now, but it could be really useful

For those not building the source from github, I have a beta version of @RenderDoc v0.21 if you'd like to try it. renderdoc.org/builds#beta

If you haven't already set up to build renderdoc from git, you can grab the latest nightly build which is up to date: renderdoc.org/autobuild

Particularly if it breaks or gets it wrong anywhere, but also how well it fits your needs. I like to drive development from actual use cases

I've merged a new pixel history feature into main on github github.com/baldurk/renderdoc . If anyone's brave I'd love real world tests & feedback!