Upload to npm please

I realise it's a work in progress, but can you say anything about likely choice of software license(s)?

e899581….js:30849 THREE.WebGLProgram: shader error: 0 gl.VALIDATE_STATUS false gl.getProgramInfoLog invalid shaders ERROR: 0:124: '=' : global variable initializers must be constant expressions

hi,

very nice work on the shader plugin for three.js. your default instructions on how to implement wagner with three.js has some console errors though. This is what i get to console when i use exact methods on instructions and latest version of three.js. i dont have any shader knowledge so i'm helpless..

is there a solution for this?

It tries to grab old/missing resources, shaders, libs. I will try to figure out what's not there anymore and then create a PR.

There are a couple files referenced by the examples that do not appear to be checked in:

Wagner.experimental.js
fragment-shaders/led-fs.glsl

(happens to me all the time)

Otherwise, it looks really good, especially on Retina display. I'm looking forward to ripping off borrowing some of your shaders.

The above error is triggered by the shader compiler in an up-to-date Chrome (Version 48.0.2564.116).

Of course, all the dependent getAttribLocation / vertexAttribPointer etc. won't work then ... so there are a bunch of those errors afterwards.

Error

THREE.WebGLShader: gl.getShaderInfoLog() 0:110(57): error: sampler arrays indexed with non-constant expressions are forbidden in GLSL 1.30 and later

Screenshot

I uploaded a screenshot from your demo to imgur here.

Another suggestion I'd like to make is to have something like window.onblur = function() { stop_renderloop(); } - at least for the demo.

Crashing programs are pretty much impossible to debug while an endless loop of errors is still running.

To make development of features easier, it would be good to add a build step using Grunt or similar.
I could put work into this if there is interest, I would propose:

• Breaking passes and discreet classes into separate files (concatenated on build)
• Concatenate shader code into main library file for distributable build to reduce http requests (current minefield example makes over 40 requests just for shaders).

Hi,

I just finished a GodrayPass for Wagner, but I encounter some weird stuff with the renderer.clear and the toTexture.

    @composer.renderer.autoClear = false
    @composer.renderer.setClearColor(0x333333,1)
    @composer.reset()
    @composer.renderer.clear()
    @composer.render(@occlusion.scene, @camera)
    @composer.toTexture(@occlusion.texture)

    @godrayPass.params.occlusionTexture         = @occlusion.texture
    @composer.pass( @godrayPass )
    @composer.toTexture(@occlusion.texture)

    # Force to render to another texture here
    @composer.toTexture(@occlusion.texture2)

    @composer.reset()
    @composer.renderer.clear()
    @composer.render(@scene, @camera)
    @blendPass.params.tInput2 = @occlusion.texture
    @composer.pass(@blendPass)
    @composer.toScreen()

After rendering the occlusionScene + the godray pass I want to blend so I needed to reset / clear / draw the scene but the clear will also clear the latest texture used in composer.toTexture.

To fixed it, I used a second texture so the first one is not clear.. but I'm sure there is a better way wihout this extra renderer.

see the screenshot below where texture & texture2 are render on 2 plane for debugging :

Let me know if I miss something!

That's what i have in console:

[GroupMarkerNotSet(crbug.com/242999)!:DC0E0406]GL ERROR :GL_INVALID_OPERATION : glDrawArrays: Source and destination textures of the draw are the same.

Is planned does rewriting as ES6 module?

Hi, thanks for the great library. I am looking to use wagner to make a live glsl node based editor. I am currently stuck on what would be the best way to chain a bunch of shaders without rendering a scene first. Simply a two triangle plane given a sequence of shaders. I would like the first pass to receive the texture from the last pass (backbuffer). An example of this would be great. Thanks!

[.CommandBufferContext]RENDER WARNING: there is no texture bound to the unit 0

Babylon is better than three, so can you make a port?

I'm looking at this older example:
http://www.neveroccurs.com/lab/three.js/gpu_particles/index.html?particles=256

and see that they use two passes that aren't available:
WagnerPositionPass.js
WagnerVelocityPass.js

I was wondering why they got dropped, or if they still exist but are called something else?

I'm working on a project that has tens of thousands of particles and I need to animate them using vertex shaders -- would using wagner be a viable solution?

I'm a big fan of Wagner! It's very impressive, and easy to use.

I visited the demo at www.clicktorelease.com/tmp/wagner/ and that works perfectly.
However, the current version of index.html in the repo (of commit 2ee57a) freezes up Chrome and crashes my GPU when I serve it locally in Chrome.
I suspect it's a problem with ANGLE that was inadvertently caused by changes from the previous version to the current one.
I was hoping to use Wagner for my next project. Help is much appreciated!

OS: Windows 8.1 64 bit
GPU: Geforce GTX 750M
Chrome: 33.0.1750.154 m

For minefield example :

GET http://127.0.0.1:8888/Wagner/Wagner.experimental.js

undefined:
controls = new THREE.OrbitControls( camera );

I didnt check all examples, but i suppose there are others missing files too !

Issue: Three JS output scene is black. The scene flashes up on screen ( for 1 frame ) then goes black. This is using the toon.html demo from GIT ( no changes )

This happens only in Windows and the shader words as expect in OSX.
Setup: Chrome 33.0.1750.154 m (windows)
Tested in: Windows 7 & 8 ( all patched up)
Also happens in Internet Explorer.

Console output from Chrome:

Compiled Wagner.js:12
Could not initialise shader
VALIDATE_STATUS: false, gl error [0] three.min.js:494
Program Info Log: (350,29-95): error X3507: '_nearestLevel': Not all control paths return a value

Warning: D3D shader compilation failed with
default
flags.
Retrying with
avoid flow control
.

(350,29-95): error X3507: '_webgl_f362b64cb55e5d08': Not all control paths return a value

Warning: D3D shader compilation failed with
avoid flow control
flags.
Retrying with
prefer flow control
.

(350,29-95): error X3507: '_webgl_f362b64cb55e5d08': Not all control paths return a value

Warning: D3D shader compilation failed with
prefer flow control
flags.
Failed to create D3D shaders.
three.min.js:495
11
WebGL: INVALID_OPERATION: getUniformLocation: program not linked toon.html:1
21
WebGL: INVALID_OPERATION: getAttribLocation: program not linked toon.html:1
WebGL: INVALID_OPERATION: useProgram: program not valid toon.html:1
WebGL: INVALID_OPERATION: vertexAttribPointer: no bound ARRAY_BUFFER toon.html:1
WebGL: INVALID_OPERATION: useProgram: program not valid

In the examples/ssao.html it's missing a script tag:

Also missing:
GET http://localhost:7000/Wagner.experimental.js 404 (File not found)

The output is also unexpected:

I get the following warnings and error:

WebGL: INVALID_VALUE: shaderSource: string not ASCII

THREE.WebGLShader: Shader couldn't compile.

THREE.WebGLProgram: shader error: 1281 gl.VALIDATE_STATUS false gl.getProgramInfoLog invalid shaders ERROR: 0:? : '' : syntax error

Actually, I have two questions,
1 where do you discuss this thing, any ML, irc channel, skype chat? issues are not really proper tool; and
2 does this thing handle transparent objects with e.g. dof? Recently I had to fight with three.js in order to get it working, but would prefer some ootb solution.

I would love to use this in my project, but the "main" field is referenced incorrectly and the library assumes a browser environment. Is this planned?