qining
qining
Yes, PR #115 is not completed yet. I think we need to fix the spec and then work on it. My feeling is that we can have a 'quick but...
Confirmed, this is a bug in the current DCE.
@pmuetschard Is this also triggered by `gapit screenshot --frame 1 smoketest.gfxtrace`? And it is not using a trace generated on another machine right?
@pmuetschard, by generated on another machine, I mean, the trace is captured and replayed on the same machine right?
Odd, I can not reproduce it on my machine. Let me try it later on my home desktop which uses an Intel driver.
It seems like this is closed automatically. Hopefully this is fixed now @pmuetschard
@pmuetschard, this is because renderpass group is actually an api.CmdIDGroup, not a api.Command or api.SubCmdRoot or api.SubCmdIdx. Do you think [371, 0, 0, 0]-[371, 0, 0, 6] is a valid...
@pmuetschard, and in terms of framebuffer request, the subcommand for [1, 0, 7, 0, 0, 0] (RenderPass) should be [371, 0, 0, 6]
Hmm, I will put up an CL with minimized changes to make the CommandRange a SubCommandRange. Probably not align with how we will fix #1134, but at least makes sense...
Here is a situation why I think mine is better: ``` - 371: vkQueueSubmit - 371.0: [371 0] [indicate the SubmitInfo index] - 371.0.0: [371 0 0] (range 371.0.0) [indicate...