Show HN: WebGL Playground

#1

Post by jessevdk » Thu, Nov 20, 2014, 10:38 AM UTC

Show HN: WebGL Playground
jessevdk.github.io

Re: Show HN: WebGL Playground

#2

Post by sz4kerto » Thu, Nov 20, 2014, 11:12 AM UTC

The 'transparent' and 'wireframe' toggles should work the other way round (at least it's contraintuitive to me -- it shows 'off' when it's on). And one combination doesn't work (transparent + no wireframes falls back to non-transparent + no wireframes).

Re: Show HN: WebGL Playground

#3

Post by userbinator » Thu, Nov 20, 2014, 11:48 AM UTC

I wonder how much of this was inspired by https://www.shadertoy.com/

Re: Show HN: WebGL Playground

#4

Post by pmx » Thu, Nov 20, 2014, 11:49 AM UTC

sz4kerto wrote: post #2

The 'transparent' and 'wireframe' toggles should work the other way round (at least it's contraintuitive to me -- it shows 'off' when it's on). And one combination doesn't work (transparent + no wireframes falls back to non-transparent + no wireframes).

I think the toggles are inverted throughout the app

Re: Show HN: WebGL Playground

#5

Post by bd » Thu, Nov 20, 2014, 12:56 PM UTC

Nice, though several examples don't work on Windows with ANGLE (OpenGL seems ok):

- DX11 ANGLE: no specular in Blinn-Phong, nothing shows in Variance and Exponential Shadow Mapping, nothing shows in HDR

- DX9 ANGLE: nothing shows in Variance and Exponential Shadow Mapping, nothing shows in HDR

Tested both in current stable Chrome and stable Firefox, GPU is Nvidia Quadro 2000M, Windows 7.

------------------------

Chrome throws these errors in console:

VSM/ESM

Filter Horizontal(program): linking: Failed to create D3D shaders.

Filter Vertical(program): linking: Failed to create D3D shaders.

HDR

HDR(program): linking: Failed to create D3D shaders.

------------------------

Firefox is more verbose, relevant parts:

VSM/ESM

(14,9-30): error X3000: unrecognized identifier 'webgl_ae64c5282b720ffe'

HDR

(40,33-55): error X3090: ps_3_0 does not allow textures or samplers to be members of compound types

Re: Show HN: WebGL Playground

#6

Post by dtf » Thu, Nov 20, 2014, 1:19 PM UTC

userbinator wrote: post #3

I wonder how much of this was inspired by https://www.shadertoy.com/

I think everyone's been inspired by the likes of JSBin/JSFiddle, GLSL sandbox and the like. Shadertoy is for pure fragment shader programs - raymarchers being the most popular. Whereas this is a more traditional mesh/vertex/fragment/control program setup.

Re: Show HN: WebGL Playground

#7

Post by bhouston » Thu, Nov 20, 2014, 1:23 PM UTC

Very interesting, but it doesn't seem to work for me Chrome beta on Windows -- I tried a fwe examples and I get these errors:

site.min.js:4586 HDR(program): linking: Failed to create D3D shaders.

site.min.js:4586 Filter Horizontal(program): linking: Failed to create D3D shaders.

site.min.js:4586 Filter Vertical(program): linking: Failed to create D3D shaders.

Re: Show HN: WebGL Playground

#8

Post by deanclatworthy » Thu, Nov 20, 2014, 1:31 PM UTC

Are there any potential security implications in providing low level access to OpenGL through a WebGL abstraction? Have there been any exploits in the wild?

Re: Show HN: WebGL Playground

#9

Post by mattdesl » Thu, Nov 20, 2014, 2:17 PM UTC

It would be cool to combine this with the Requirebin.com backend so the GLSL code could use glslify, and the GL code could use stackgl (or some other family of modules) rather than just an in-house GL abstraction.

Re: Show HN: WebGL Playground

#10

Post by jessevdk » Thu, Nov 20, 2014, 2:22 PM UTC

Hi, author here. Thanks to everyone for checking this out. I'm sorry if some of the examples don't work across the board, most of these use WebGL extensions that might not be available everywhere. As some people mention in the comments here, and as mentioned in the introductionary text on the website, I've not been able to test this across a large variety of platforms and browsers and I expected there to be issues in particular on Windows using ANGLE. Please consider filing issues on github intead of/in addition to reporting them here so I can actually track them.