Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Interactive intro to shaders

mayerowitz.io

Post reply on HN
Print view View original

71–72 of 72 posts

Re: Interactive intro to shaders

#71

Post by araes »

sph wrote: post #37
superMayo wrote: post #2

I finally found the courage to write and expose myself to the internet. I've always wanted to learn shaders so I thought it would be nice to document my learning and share it with others.

Welcome to the Internet, superMayo! If you want to see what the Masters can do with shaders, let me introduce you to Inigo Quilez and his shader art: https://www.youtube.com/watch?v=BFld4EBO2RE EDIT: I did not notice you are the author of this article. It's very well done, and I've been looking for more approachable and interactive tutorials on the arts of shader coding.

If we're going to do the link to IQ, then probably should link to Shadertoy, where there are several thousand shaders to look at for ideas.

IQ's personal page on Shadertoy: https://www.shadertoy.com/user/iq/sort=newest&from=576&num=8

Shadertoy is created by Beautypi (Inigo Quilez and Pol Jeremias).

And all of IQ's introductory articles on using Shadertoy.

// Input - Keyboard : https://www.shadertoy.com/view/lsXGzf

// Input - Microphone : https://www.shadertoy.com/view/llSGDh

// Input - Mouse : https://www.shadertoy.com/view/Mss3zH

// Input - Sound : https://www.shadertoy.com/view/Xds3Rr

// Input - SoundCloud : https://www.shadertoy.com/view/MsdGzn

// Input - Time : https://www.shadertoy.com/view/lsXGz8

// Input - TimeDelta : https://www.shadertoy.com/view/lsKGWV

// Inout - 3D Texture : https://www.shadertoy.com/view/4llcR4

Re: Interactive intro to shaders

#72

Post by prox »

superMayo wrote: post #30
prox wrote: post #22

Earlier quoted context omitted.

I might be wrong but there are compute shaders that can retake inputs and well, do more computing on them afaik.

Indeed it's a simplification! You can use buffers to keep information from previous states or share state between pixels (for both fragment and compute shaders). Though it can greatly reduce the performance sometimes. For an intro however, I think it's simpler to assume no memory nor shared state.

Ah yes, its good to simplify in the beginning! Cool article in any case!
Post reply on HN