The Only Tool You Need To Succeed In Graphics Programming (how to debug with renderdoc)

[@DetectivePoofPoof]

Damn, I heard about this. but didn't know it was THIS amazing! I just started learning opengl a little while ago but I'm definitely going to start using this thing now. I had no idea you could have this much information and debug capabilities for graphics programming!

[@MyBucketL1st]

I mean if "debugging" means ripping models from games and stuff, call me a debugger 👀

[@SilverEchoDreamer]

if u debuger, place like to this comment. Im also Debugger) But my debug software little bit different... with shuriken in icon.

[@bubby1595]

​@@SilverEchoDreamer ninja ripper, don't try to gatekeep

[@haloshiroe]

Less about gatekeeping and more about keeping a low profile, for what I hope are obvious reasons

[@w花b]

​@@haloshiroe Idk what you're talking about

[@tykobrising5339]

Great video, Oskar! Managed to squeeze in more useful stuff than an hour and a half of lectures. Though admittedly with the high pace it's more of a guide to what to look for than actually learning. I like that format.

[@lunarthicclipse8219]

This tool is literally my lord and saviour. It saved me from countless hours of debugging and hair pulling 😂😂 it's so powerful I love it.

[@skeleton_craftGaming]

this seems like an open source version of nsight exept w/o the driver level integration that makes nsight so helpful

[@oskar_schramm]

Nsight definitely has its strengths, when it comes to pinpointing GPU bottlenecks or timing shader performance, it’s absolutely invaluable, but I wouldnt debug with nsight. It's just way to slow and clunky, and for everyday use, I don't need that info. I just need something fast and easy to debug with, which is renderdoc for me and alot of other people.

[@mmj-video-logs]

Thank you Oskar for making it.

[@Chrzanof]

I just found your channel. Brooo you're an absolute gem!

[@Liam-pf7ih]

Haha its so true that its taken for granted I don't even remember where I heard about it, and ever since I started using it a few years ago I don't think I've ever heard someone else mention it. Glad to watch this though since I never properly learnt about all its features

[@slendi9623]

i personally cant live without the metal graphics debugger

[@JavierAlessandro]

Thanks for this !!

[@niamhleeson3522]

I love renderdoc so much lol. I'm no pro but it's literally so useful

[@billjeason6635]

Sadlly RenderDoc don`t support DX12 Raytracing Shader debuging

[@oskar_schramm]

Yeah recently heard about that. Will probably do a follow up video on PIX in the future, which should cover that aswell.

[@saurabhjadhav6496]

i have used apitrace can this be used for debugging webgl through browser ?

[@mikk5428]

i can't use it. im using bindless textures.

[@dragoons_net]

WOW Oskar thank you so much! I didn't know about this tool, which appears almost too good to be true !!! But on Unity, getting error message under DX12: Assertion failed on expression: 'IsRealGfxDeviceThread() || (GetGfxThreadingMode() == kGfxThreadingModeNonThreaded)' / will try to use it indirectly

[@therealpeter2267]

Some Unity versions may be bugged / graphics APIs can be bugged, try DX11 or a different Unity version Edit: also make sure to load RenderDoc before you run the play mode when booting the project up, an already loaded project can mess it up

[@dragoons_net]

@@therealpeter2267 Thanks a lot for your input. I am stuck wtih DX12 both for the targetted platforms AND the use of intrinsics (prefixsum, etc). The message indicated above is appearing when I load RenderDocs in Unity. But this seems to be so awesome! Not dropping the case...

[@robostep9829]

No ray tracing debugging ☹️

[@aswinaswin5672]

Good..

[@dimarichmain]

Renderdoc is solid, but Nsight is better in most cases.

[@oskar_schramm]

Feature wise I agree, fastness of iteration I don’t. Nsight is just not nearly as fast at getting a quick glance, and quick glances is what graphics programming is 95% of the time

[@dimarichmain]

@@oskar_schramm Nsight handles error better. In some snapshots loading times in renderdoc get too long. I also notices a few graphical bugs when replaying my recordings. The resource history in Nsight is very usefull, too, and so are the stats. I use renderdoc for debugging a lot but Nsight's profiler is more precise and provides more info.

[@kotofyt]

Thank god Im forced to use nsight to debug hwrt