Newton's Cradle: Setting up Materials

[@LeutnantJoker]

As a normal dev it always amazes me looking at this stuff knowing that it is just a shader, no mesh whatsoever involved, except maybe the quad this is rendered on. It always inspires me to think about what could be a shader instead of an actual object :) Looking forward to the recursive raymarching, which is how you'll get the reflections I assume :)

[@playbyan1453]

Great implementation, probably try blending material color because I need it.

[@DoganAktay8]

I wonder if Martijn ever gets impressed by the stuff he makes :D "Hey this super cool thing I whipped up in about fifty minutes, yea it's not that cool" sips some tea

[@daviddawkins]

Could you convert the main GetDistance() to return a vec2 as you did for sdBall()? (This is what I thought you were going to do). You’d only have one set of object definitions, and make only a single “getDistAndMat()” call per frame. Excellent stuff as always, mind-blowing.

[@TheArtofCodeIsCool]

Yeah in hind sight I might have done it that way. Would have come out a little cleaner.

[@daviddawkins]

@@TheArtofCodeIsCool Maybe, but there’s a lot to be said for getting the job done without over-engineering, too.

[@RayBellis]

TBH, this is what I was expecting to see, because having to reproduce the same logic in two separate functions is pretty unreliable. In my own experiments instead of a vec2 I use a "Hit" structure that contains the distance and a vec3 colour, but I might try replacing the colour with a material index instead.

[@tobberh]

Uhhh can't wait for the real reflections! :)

[@PhilippeGauthier]

Thanks a lot, very clear, as always!

[@AFE-GmdG]

Cool Video and good explanations. One thing I don't link at your code is the naming of your variables and functions: proper naming would lead to much better readable code.

[@wafoo42]

Hey, I like your videos a lot. You're a really good instructor and you're also really entertaining. I have a suggestion however, could you reduce the webcam size, or put it in the bottom left, so we can see the whole editor. It's not a big problem as you always edit code above your face, but it's a bit distracting that as the code writes your face moves near it. Also if you ever make videos using many input channels it could be a problem. Great work anyway !

[@antoinedevldn]

Thanks a lot, very usefull!

[@thomasbob3879]

wonderful.!

[@Bleenderhead]

any reason to use const int instead of #define?

[@TheArtofCodeIsCool]

It doesn't matter much in this case

[@TankorSmash]

That 'click the bell icon' sound effect is real low quality, it always sounds weird when I hear it.

[@realcygnus]

So superb as always. One of those priceless gems for which there is surprisingly few quality tuts on still. I strongly recommend $uppurting such channels, to those who can.

[@d74g0n]

What if that is a very small cup he drinks from; and he's just an extra tiny tiny alien man. Thank you for sharing your knowledge with us tiny alien man.

[@MartinToernby]

There wouldn't be room enough for math-related neurons in his head then. But again - he knows how warp space more than most!