Rendering my (billiard) balls in a fragment shader • Hacker News Board

Re: Rendering my (billiard) balls in a fragment shader

#11

Post by b4je7d7wb » Sun, Sep 11, 2022, 6:39 AM UTC

javawizard wrote: post #10

sysrpl wrote: post #6

Earlier quoted context omitted.

I fixed it. Thanks.

What was it originally? Hard to get more amusing than the actual article title...

The actual article was titled "Rendering Pool Balls". He fixed it by updating the article title rather than the HN submission(which I don't think you even can).

Re: Rendering my (billiard) balls in a fragment shader

#12

Post by eyelidlessness » Sun, Sep 11, 2022, 6:40 AM UTC

pixel_tracing wrote: post #3

Came for the title, stayed for the shaders. Well written and very educational

> Came for the title

Well played

Edit: I’ll take the downvotes, the author edited the thing for silly innuendo, it’s silly, I’ll have fun too and take my lashes.

Re: Rendering my (billiard) balls in a fragment shader

#13

Post by xanthine » Sun, Sep 11, 2022, 6:41 AM UTC

I happened to notice that PI is #define'd to 3.1415926538, which isn't the correctly rounded off value of 3.14159265358...

Seems like they missed a '5'.

Re: Rendering my (billiard) balls in a fragment shader

#14

Post by ketzo » Sun, Sep 11, 2022, 6:42 AM UTC

sysrpl wrote: post #7

causality0 wrote: post #5

From the HN guidelines: please use the original title, unless it is misleading or linkbait; don't editorialize. The correct title is Rendering Pool Balls , not "Rendering my balls in a fragment shader".

Fixed.

…well played

Re: Rendering my (billiard) balls in a fragment shader

#15

Post by sysrpl » Sun, Sep 11, 2022, 6:48 AM UTC

xanthine wrote: post #13

I happened to notice that PI is #define'd to 3.1415926538, which isn't the correctly rounded off value of 3.14159265358... Seems like they missed a '5'.

Lol, wow what a find. You notice the details. I corrected it. Thank you.

Re: Rendering my (billiard) balls in a fragment shader

#16

Post by [deleted] » Sun, Sep 11, 2022, 6:50 AM UTC

pfoof wrote: post #9

Cool to read about C-like GLSL on a Pascal website

[deleted]

Re: Rendering my (billiard) balls in a fragment shader

#17

Post by londons_explore » Sun, Sep 11, 2022, 6:54 AM UTC

What's the benefit of rendering using this technique over a regular sphere rendered with the usual pipeline?

Re: Rendering my (billiard) balls in a fragment shader

#18

Post by cowtools » Sun, Sep 11, 2022, 7:01 AM UTC

londons_explore wrote: post #17

What's the benefit of rendering using this technique over a regular sphere rendered with the usual pipeline?

It is faster for the case of a "top-down" 2D game. You render this and just draw a single quad per ball. You do not really have any vert shader.

Re: Rendering my (billiard) balls in a fragment shader

#19

Post by jahewson » Sun, Sep 11, 2022, 7:03 AM UTC

sysrpl wrote: post #7

causality0 wrote: post #5

From the HN guidelines: please use the original title, unless it is misleading or linkbait; don't editorialize. The correct title is Rendering Pool Balls , not "Rendering my balls in a fragment shader".

Fixed.

Outrageous! Well done.

Re: Rendering my (billiard) balls in a fragment shader

#20

Post by sysrpl » Sun, Sep 11, 2022, 7:05 AM UTC

londons_explore wrote: post #17

What's the benefit of rendering using this technique over a regular sphere rendered with the usual pipeline?

Well first of you get infinite smoothness and better lighting (and reflections if you add them) because there is no underlying geometry. It's just math. It's also much faster, as you're only giving the GPU four vertices defining the square. This can even be sped up further by using point sprites which consume only one vertex.