search

baldurk / renderdoc

RenderDoc is a stand-alone graphics debugging tool.
https://renderdoc.org
MIT License
9.01k stars 1.35k forks source link

Device memory view #546

Open edrickhong opened 7 years ago

edrickhong commented 7 years ago

Is it possible to implement a memory viewer for the new api's. Also showing overlapping regions for bound buffers and textures would be great. Thanks.

baldurk commented 7 years ago

I think this should be possible if you want to see where objects are being bound into a memory allocation. If you mean a raw memory viewer that just takes a pointer/offset into some allocation and shows you bytes, I'm not so sure about that.

It might also tie into being able to see the lifetime of resources to understand where overlap/sharing is happening, or where updates happen relative to use (better than the current timeline bar does).

edrickhong commented 7 years ago

Currently I sub allocated devicememory allocations. I mainly want a way to visualize bound regions and maybe a way to highlight recently written regions? Being able to inspect their contents would be nice I guess but it's not a concern. I think it would be a nice feature to have now that we have to manage the memory ourselves.