Added raymarching reflect example.

[gam0022]

I added an example of raymarching reflect using ShaderMaterial.

[WestLangley]

Nice!

http://ci.threejs.org/api/pullrequests/7860/examples/webgl_raymarching_reflect.html

Consider using THREE.RawShaderMaterial, instead, as that is all that is required.

If you do so, you will have to add

    attribute vec3 position;

to the vertex shader.

[WestLangley]

Should renderer.setPixelRatio( window.devicePixelRatio ); be added?

[mrdoob]

Nice! Thanks!

[mrdoob]

@WestLangley Implemented your suggestions.

However... I think it would be cool if, instead of passing mouse and time to the shader we would simply pass the camera. I guess for that we have to decompose the camera matrix into position and direction?

[gam0022]

Thank you for the comment and the merging!

[WestLangley]

I think it would be cool if, instead of passing mouse and time to the shader we would simply pass the camera. I guess for that we have to decompose the camera matrix into position and direction?

Agreed. camera.getWorldPosition( worldPos ) and camera.getWorldDirection( worldDir ) should do it.

@gam0022 Would you be willing to have a go at that?

[gam0022]

Agreed. camera.getWorldPosition( worldPos ) and camera.getWorldDirection( worldDir ) should do it.
@gam0022 Would you be willing to have a go at that?

Yes, I got it.
Do you think that I should pass cameraPos and cameraDir to the shader as type: 'v3'?

[gam0022]

Is this alright?
gam0022@f68e1fb

But screen began to black out by the cameraPos...

[gam0022]

It was solved by adding dummyCamera for renderer.render().
gam0022@f94947d

Do you think it is this a good ?

[WestLangley]

Hmmm. I just realized you are instantiating a THREE.Camera() and using a simplified vertex shader. This was also done in http://threejs.org/examples/webgl_shader.html. Personally, I would use an orthographic camera to render the quad, but your approach does appear to work...

@mrdoob -- Do you have an opinion on this?

[gam0022]

I thank that there is no need to use the orthographic camera.
It's because projectionMatrix was not used in VertexShader.

[gam0022]

In #7863, I used two cameras.

1. Camera to render the THREE.PlaneBufferGeometry. (dummyCamera)
2. Camera in the raymarching world.(camera)

[WestLangley]

I think that there is no need to use the orthographic camera.
It's because projectionMatrix was not used in VertexShader.

gl_Position must be in Normalized Device Coordinate space. So your approach only works because, in addition to the omission of the projection matrix, the PlaneBufferGeometry is 2 X 2 and centered at the origin.

I assume you copied this from another example, but I expect this will be confusing to users.

@greggman Have you seen this as a common technique for rendering a full-screen quad? (simplified vertex shader, careful positioniing of the quad so the projection matrix is not required)

[greggman]

@WestLangley seems common to me. Isn't that what glslsandbox.com and shadertoy.com do? Isn't it also what http://threejs.org/examples/webgl_shader.html does? Or am I mis-understanding?

[WestLangley]

@greggman It is what webgl_shader.html does. I expect the OP copied that example. I am wondering if this is confusing to users -- especially since @mrdoob suggested:

I think it would be cool if, instead of passing mouse and time to the shader we would simply pass the camera.

At this point, I am no longer sure how that suggestion makes sense in the context of this example.

[gam0022]

Thank you for comments.

gl_Position must be in Normalized Device Coordinate space. So your approach only works because, in addition to the omission of the projection matrix, the PlaneBufferGeometry is 2 X 2 and centered at the origin.

I now finally understand what you mean.

I assume you copied this from another example,

Yes, it is.

but I expect this will be confusing to users.

I think that there is some truth in what you says.

[gam0022]

gl_Position must be in Normalized Device Coordinate space. So your approach only works because, in addition to the omission of the projection matrix, the PlaneBufferGeometry is 2 X 2 and centered at the origin.

Should I explain the above points at comments in webgl_raymarching_reflect.html to avoid confusing to users?

[WestLangley]

My preference would be to use an orthographic camera. THREE.Camera() was not intended to be used directly -- at least that was my understanding. But since what you have implemented works, I'll leave it up to @mrdoob to decide.

I am not sure it makes sense to pass the camera "position".

[mrdoob]

I am not sure it makes sense to pass the camera "position".

The idea was to pass a camera into the shader, so the three world is more integrated with the raymarcher world. Ideally we could pass camera.matrixWorld and camera.projectionMatrix and decompose inside the shader.

[WestLangley]

Thing is, there are no objects in the scene. This is just a full-screen quad with a shader rendererd on it.

I do not feel strongly about this, but the whole thing to me is strange -- now that I think about it.

[mrdoob]

Yes, but imagine that we wanted to animate the camera. We have a lot of code for animating stuff now. We can animate the camera outside instead of replicating animation code inside the shader.