Live data from Hacker News

WebGL water scene

c1.goote.ch

31–40 of 115 posts

Re: WebGL water scene

#32

Can someone please tell me why I should be excited about these demos? Am I not just seeing an OpenGL wrapper in the browser?

Because it runs in any browser, even mobile ones and requires basically 0 time for compilation and no plugins as opposed to unity, unreal or other engines.

Re: WebGL water scene

#35
post #30

Earlier quoted context omitted.

And a very old one too. Look at the website for some really cool looking projects: goocreate.com

Two speaking mountains reading aloud random Twitter messages oO Strangest thing I've seen today http://www.mountainsofmouthness.com/

That is one of my favorite ones. It was awesome to see the guys making it having fun with it and giving them the tools they needed to do it.

Re: WebGL water scene

#37
One thing that i've seen a couple of times now with these types of demos is that the animation is pretty smooth, but the music / sound is stuttering and noisy. Anyone has that as well? I'm using Chrome on a pretty beefy (16GB) MacBook Pro.

Re: WebGL water scene

#38
post #36

Earlier quoted context omitted.

Yes

I like it. Do you have a YouTube channel or something?

There is a vimeo channel but hasn't been updated with cool videos in a while. We need to fill up the youtube and vimeo channels for sure. https://vimeo.com/gootechnologies

Re: WebGL water scene

#39
post #37

One thing that i've seen a couple of times now with these types of demos is that the animation is pretty smooth, but the music / sound is stuttering and noisy. Anyone has that as well? I'm using Chrome on a pretty beefy (16GB) MacBook Pro.

Yup. Choppy sound for me in Chrome w/ 16 GB MacBook Pro, too.

Re: WebGL water scene

#40
post #37

One thing that i've seen a couple of times now with these types of demos is that the animation is pretty smooth, but the music / sound is stuttering and noisy. Anyone has that as well? I'm using Chrome on a pretty beefy (16GB) MacBook Pro.

Yup. Choppy sound for me in Chrome w/ 16 GB MacBook Pro, too.

Same here. Reminds me of glitches typical of apps using a too small mixing buffer (in an attempt to run with a low latency?)
Post reply on HN