Repository navigation
Capturing too much? #16
Description
Activity
Textures have a "state" that can be "destroyed" if they are a canvas texture that has been presented. The UI could filter them out maybe? (and we could add the same for command buffers etc). However it seems hard to know exactly what resources to capture or not on beginTrace because textures may be referenced in bind groups that are referenced in commands etc. So I don't know that we can remove these from the trace.
So I added a Resource view. At the top of the "Steps" pane, click "Resources". It shows all the objects (textures, buffers, etc...)
It's saving too much. I guess if capture is not on we can discard any canvas textures and after a frame or so discard any command buffers that have been submitted?