About halfway through the video I let out a long "AAAaaaahhhh...". Then it clicked, after writing several half-working compute shaders, watching many videos on them, reading guides, it wasn't until your examples that it suddenly made complete sense. This is both what I love and hate about programming; it feels impenetrable and extremely complex until it's suddenly the most natural thing in the world and you're embarrassed that you didn't get it before. That's what my electronics teacher told me when he was teaching the binary system; "you need to be stupid enough to understand this". I had the same feeling here, I over-complicated it until you succinctly and simply explained it to me. Thank you so much!
Very informative! Many people who make compute shader videos, however useful, either don't know or don't inform on what the kernel size actually really does. This is super useful and clears up a lot! Thank you!
I slept to this video, calmest voice ever. I didn't understand anything yet, I'll attempt to do that when I'm awake. Please make more videos like this where you explain programming stuff calmly. Thank you.
This is surprisingly good, especially for a beginner like me. The teaching style is very different from most youtube videos or udemy courses, but it works so well with a topic like this. I was even more impressed when I saw you take inspiration from biology for your shaders, as I'm a biologist myself. Unfortunately, I can't afford the course, but I will follow your channel closely. Thanks for this amazing tutorial.
Hey thanks! I have a whole workshop on the subject here: paprika.studio/workshops/compute/index.html. This is just the first video of many that are in the workshop.
Please make as many of your class videos available as possible, I'm not able to afford $400 but am starting the process of learning how to use computer shaders and would appreciate all the materials I can access.
the id determined by the thread index, not the group index. feel free to sign up for the workshop (link in description) if you're interested in more detail
Hey! It’s a combo of prerecorded videos, a very active Discord group, and assignment deadlines. I usually start a cohort every two months. More info in the link in my twitter bio here: Twitter.com/psychobiotik
You can dispatch multiple groups, so the GPU will just process them in turn if the grid that you dispatch has more threads than can be processed in one go. More here: notochord.xyz/compute-shader-class.html
Say I have a bunch of particles where I want to do physics simulations off of. I understand in the shader I could pass some known values to and the particle's id into the shader. However, what about returning the values computed from the shader (position / velocity)? if these are happening in parallel, how do I get this data back outside of the GPU?
Depends on the shader framework, but usually there is a way to get data from a GPU buffer and put it into a CPU array. More here: notochord.xyz/compute-shader-class.html
What are workgroup and invocation in workgroup.Are invocation referred to cell?So in each work group given cell will perform same computation and different workgroup cells will do different work?that is how is it arranged?
For everyone who didnt understand: 1. His explanation was brilliant what cant you understand about that 2. In case you still dont get it: he is basically god and the only person on earth that can comfirtably work with compute shaders.
What a great channel! I feel like this channel would explode if you put a little bit more energy into the voiceover, but I love your videos nonetheless!
@@arsiliath No idea if you want this channel to explode like Mr. Frippertronics wants, but I prefer the calm tone. I can't stand artificial excitement, clickbait titles, bouncing around in the chair, the latest slang, and generally trying to appeal to TikTok fans. Keep doing what you are doing, IMO.
