Replies: 4 comments
|
Huh, now I've had one run where only the last 9 scopes have timings. Something's definitely off 😄 |
0 replies
|
Okay, it seems like the wgpu vulkan backend is the culprit. This just works with the DX12 backend. |
0 replies
|
Yeah I think you're running into |
0 replies
|
Thank you for this example! The documentation in readme is written for someone who already knows what they are doing. I was calling |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hey!
I've got roughly this setup:
The results I get back contain entries for all created scopes (the top-level one, and 3 for each iteration, so 25 in total).
However, most of the time, all of them have a recorded time of
Some(0.0..0.0). All zeros everywhere.Sometimes, I do get some results back, but always without the last 3 iterations (3 scopes each) - those are present in the results, but again with 0s as timings. What am I doing wrong here?
using wgpu v27 and the latest master commit of wgpu-profiler
All reactions