Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@Lensflare but it's also quite rewarding.
-
Thr joy of vulkan synchronization
Turns out I didn't insert a pipeline barrier between writing dispatch indirect params and the dispatch indirect itself
RenderDoc seems to insert some barriers, so it was visible there, but in reality the two dispatches where racing so the dispatch indirect still saw the cleared buffer (and thus 0*0*0 dispatch dims) -
@thebiochemic I think rocket science is too. You design a rocket and it can succeed or fail. You want it to succeed, but if it fails its like a giant ass firecracker that you collect data from.
-
@Demolishun where do I insert a debugger watch into my giant ass firecracker?
that seems like the hard part. -
@Wisecrack I am only going to partially quote you from now on: "where do I insert a debugger watch into my giant ass"
-
@Demolishun you could also change the word order "where do I insert a giant firecracker into my ass"
-
@Demolishun quotation level: Legendary
Name one thing more fun than atomically writing values into a gpu buffer and them mysteriously vanishing into the aether immediately after the compute shader invocation
I can literally see them in the buffer using RenderDoc and then as soon as I go to the next command the buffer is completely filled with zeros again as if the values never existed
?? like how ??
rant
vulkan
fml