{"id":91254,"date":"2018-06-25T13:33:43","date_gmt":"2018-06-25T13:33:43","guid":{"rendered":"http:\/\/www.sickgaming.net\/blog\/2018\/06\/25\/creating-toon-water-for-the-web-part-3\/"},"modified":"2018-06-25T13:33:43","modified_gmt":"2018-06-25T13:33:43","slug":"creating-toon-water-for-the-web-part-3","status":"publish","type":"post","link":"https:\/\/sickgaming.net\/blog\/2018\/06\/25\/creating-toon-water-for-the-web-part-3\/","title":{"rendered":"Creating Toon Water for the Web: Part 3"},"content":{"rendered":"

Welcome back to this three-part series on creating stylized toon water in PlayCanvas using vertex shaders.\u00a0In Part 2<\/a> we covered buoyancy & foam lines. In this final part, we’re going to apply the underwater distortion as a post-process effect. <\/p>\n

Refraction & Post-Process Effects<\/h2>\n

Our goal is to visually communicate the refraction of light through water. We’ve already covered how to create this sort of distortion in a fragment shader in a previous tutorial<\/a> for a 2D scene. The only difference here is that we’ll need to figure out which area of the screen is underwater and only apply the distortion there.\u00a0<\/p>\n

Post-Processing<\/h3>\n

In general, a post-process effect is anything applied to the whole scene after it is rendered, such as a colored tint or an old CRT screen effect<\/a>. Instead of rendering your scene directly to the screen, you first render it to a buffer or texture, and then render that to the screen, passing through a custom shader.<\/p>\n

In PlayCanvas, you can set up a post-process effect by creating a new script. Call it Refraction.js<\/strong>, and copy this template to start with:<\/p>\n

\/\/--------------- POST EFFECT DEFINITION------------------------\/\/\npc.extend(pc, function () { \/\/ Constructor - Creates an instance of our post effect var RefractionPostEffect = function (graphicsDevice, vs, fs, buffer) { var fragmentShader = \"precision \" + graphicsDevice.precision + \" float;\\n\"; fragmentShader = fragmentShader + fs; \/\/ this is the shader definition for our effect this.shader = new pc.Shader(graphicsDevice, { attributes: { aPosition: pc.SEMANTIC_POSITION }, vshader: vs, fshader: fs }); this.buffer = buffer; }; \/\/ Our effect must derive from pc.PostEffect RefractionPostEffect = pc.inherits(RefractionPostEffect, pc.PostEffect); RefractionPostEffect.prototype = pc.extend(RefractionPostEffect.prototype, { \/\/ Every post effect must implement the render method which \/\/ sets any parameters that the shader might require and \/\/ also renders the effect on the screen render: function (inputTarget, outputTarget, rect) { var device = this.device; var scope = device.scope; \/\/ Set the input render target to the shader. This is the image rendered from our camera scope.resolve(\"uColorBuffer\").setValue(inputTarget.colorBuffer); \/\/ Draw a full screen quad on the output target. In this case the output target is the screen. \/\/ Drawing a full screen quad will run the shader that we defined above pc.drawFullscreenQuad(device, outputTarget, this.vertexBuffer, this.shader, rect); } }); return { RefractionPostEffect: RefractionPostEffect };\n}()); \/\/--------------- SCRIPT DEFINITION------------------------\/\/\nvar Refraction = pc.createScript('refraction'); Refraction.attributes.add('vs', { type: 'asset', assetType: 'shader', title: 'Vertex Shader'\n}); Refraction.attributes.add('fs', { type: 'asset', assetType: 'shader', title: 'Fragment Shader'\n}); \/\/ initialize code called once per entity\nRefraction.prototype.initialize = function() { var effect = new pc.RefractionPostEffect(this.app.graphicsDevice, this.vs.resource, this.fs.resource); \/\/ add the effect to the camera's postEffects queue var queue = this.entity.camera.postEffects; queue.addEffect(effect); this.effect = effect; \/\/ Save the current shaders for hot reload this.savedVS = this.vs.resource; this.savedFS = this.fs.resource;\n}; Refraction.prototype.update = function(){ if(this.savedFS != this.fs.resource || this.savedVS != this.vs.resource){ this.swap(this); }\n}; Refraction.prototype.swap = function(old){ this.entity.camera.postEffects.removeEffect(old.effect); this.initialize(); };<\/pre>\n
This is just like a normal script, but we define a RefractionPostEffect<\/code> class that can be applied to the camera. This needs a vertex and a fragment shader to render. The attributes are already set up, so let’s create Refraction.frag<\/strong> with this content:<\/p>\n
precision highp float; uniform sampler2D uColorBuffer;\nvarying vec2 vUv0; void main() { vec4 color = texture2D(uColorBuffer, vUv0); gl_FragColor = color;\n}\n<\/pre>\n
And Refraction.vert<\/strong> with a basic vertex shader:<\/p>\n
attribute vec2 aPosition;\nvarying vec2 vUv0; void main(void)\n{ gl_Position = vec4(aPosition, 0.0, 1.0); vUv0 = (aPosition.xy + 1.0) * 0.5;\n}\n<\/pre>\n
Now attach the Refraction.js<\/strong> script to the camera, and assign the shaders to the appropriate attributes. When you launch the game, you should see the scene exactly as it was before. This is a blank post effect that simply re-renders the scene. To verify that this is working, try giving the scene a red tint. <\/p>\n
In Refraction.frag, instead of simply returning the color, try setting the red component to 1.0, which should look like the image below.<\/p>\n
\"Scene<\/figure>\n
Distortion Shader<\/h3>\n
We need to add a time uniform for the animated distortion, so go ahead and create one in Refraction.js, inside this constructor for the post effect:<\/p>\n
var RefractionPostEffect = function (graphicsDevice, vs, fs) { var fragmentShader = \"precision \" + graphicsDevice.precision + \" float;\\n\"; fragmentShader = fragmentShader + fs; \/\/ this is the shader definition for our effect this.shader = new pc.Shader(graphicsDevice, { attributes: { aPosition: pc.SEMANTIC_POSITION }, vshader: vs, fshader: fs }); \/\/ >>>>>>>>>>>>> Initialize the time here this.time = 0; };<\/pre>\n
Now, inside this render function, we pass it to our shader and increment it:<\/p>\n
RefractionPostEffect.prototype = pc.extend(RefractionPostEffect.prototype, { \/\/ Every post effect must implement the render method which \/\/ sets any parameters that the shader might require and \/\/ also renders the effect on the screen render: function (inputTarget, outputTarget, rect) { var device = this.device; var scope = device.scope; \/\/ Set the input render target to the shader. This is the image rendered from our camera scope.resolve(\"uColorBuffer\").setValue(inputTarget.colorBuffer); \/\/\/ >>>>>>>>>>>>>>>>>> Pass the time uniform here scope.resolve(\"uTime\").setValue(this.time); this.time += 0.1; \/\/ Draw a full screen quad on the output target. In this case the output target is the screen. \/\/ Drawing a full screen quad will run the shader that we defined above pc.drawFullscreenQuad(device, outputTarget, this.vertexBuffer, this.shader, rect); }\n});<\/pre>\n
Now we can use the same shader code from the water distortion tutorial, making our full fragment shader look like this:<\/p>\n
precision highp float; uniform sampler2D uColorBuffer;\nuniform float uTime; varying vec2 vUv0; void main() { vec2 pos = vUv0; float X = pos.x*15.+uTime*0.5; float Y = pos.y*15.+uTime*0.5; pos.y += cos(X+Y)*0.01*cos(Y); pos.x += sin(X-Y)*0.01*sin(Y); vec4 color = texture2D(uColorBuffer, pos); gl_FragColor = color;\n}\n<\/pre>\n
If it all worked out, everything should now look like as if it’s underwater, as below.<\/p>\n
\"Underwater<\/figure>\n
\nChallenge #1: Make the distortion only apply to the bottom half of the screen. <\/em>\n<\/p><\/blockquote>\n
Camera Masks
\n<\/h3>\n
We’re almost there. All we need to do now is to apply this distortion effect just on the underwater part of the screen. The most straightforward way I’ve come up with to do this is to re-render the scene with the water surface rendered as a solid white, as shown below.<\/p>\n
\"Water<\/figure>\n
This would be rendered to a texture that would act as a mask. We would then pass this texture to our refraction shader, which would only distort a pixel in the final image if the corresponding pixel in the mask is white. <\/p>\n
Let’s add a boolean attribute on the water surface to know if it’s being used as a mask. Add this to Water.js:<\/p>\n
Water.attributes.add('isMask', {type:'boolean',title:\"Is Mask?\"});<\/pre>\n
We can then pass it to the shader with material.setParameter('isMask',this.isMask);<\/code> as usual. Then declare it in Water.frag and set the color to white if it’s true.<\/p>\n
\/\/ Declare the new uniform at the top\nuniform bool isMask; \/\/ At the end of the main function, override the color to be white \/\/ if the mask is true if(isMask){ color = vec4(1.0); }<\/pre>\n
Confirm that this works by toggling the “Is Mask?” property in the editor and relaunching the game. It should look white, as in the earlier image. <\/p>\n
Now, to re-render the scene, we need a second camera. Create a new camera in the editor and call it CameraMask<\/strong>. Duplicate the Water entity in the editor as well, and call it WaterMask<\/strong>. Make sure the “Is Mask?” is false for the Water entity but true for the WaterMask. <\/p>\n
To tell the new camera to render to a texture instead of the screen, create a new script called CameraMask.js<\/strong> and attach it to the new camera. We create a RenderTarget<\/a> to capture this camera’s output like this:<\/p>\n
\/\/ initialize code called once per entity\nCameraMask.prototype.initialize = function() { \/\/ Create a 512x512x24-bit render target with a depth buffer var colorBuffer = new pc.Texture(this.app.graphicsDevice, { width: 512, height: 512, format: pc.PIXELFORMAT_R8_G8_B8, autoMipmap: true }); colorBuffer.minFilter = pc.FILTER_LINEAR; colorBuffer.magFilter = pc.FILTER_LINEAR; var renderTarget = new pc.RenderTarget(this.app.graphicsDevice, colorBuffer, { depth: true }); this.entity.camera.renderTarget = renderTarget;\n};<\/pre>\n
Now, if you launch, you’ll see this camera is no longer rendering to the screen. We can grab the output of its render target in Refraction.js<\/strong> like this:<\/p>\n
Refraction.prototype.initialize = function() { var cameraMask = this.app.root.findByName('CameraMask'); var maskBuffer = cameraMask.camera.renderTarget.colorBuffer; var effect = new pc.RefractionPostEffect(this.app.graphicsDevice, this.vs.resource, this.fs.resource, maskBuffer); \/\/ ... \/\/ The rest of this function is the same as before };<\/pre>\n
Notice that I pass this mask texture as an argument to the post effect constructor. We need to create a reference to it in our constructor, so it looks like:<\/p>\n
\/\/\/\/ Added an extra argument on the line below\nvar RefractionPostEffect = function (graphicsDevice, vs, fs, buffer) { var fragmentShader = \"precision \" + graphicsDevice.precision + \" float;\\n\"; fragmentShader = fragmentShader + fs; \/\/ this is the shader definition for our effect this.shader = new pc.Shader(graphicsDevice, { attributes: { aPosition: pc.SEMANTIC_POSITION }, vshader: vs, fshader: fs }); this.time = 0; \/\/\/\/ <<<<<<<<<<<<< Saving the buffer here this.buffer = buffer; };<\/pre>\n
Finally, in the render function, pass the buffer to our shader with:<\/p>\n
scope.resolve(\"uMaskBuffer\").setValue(this.buffer); <\/pre>\n
Now to verify that this is all working, I’ll leave that as a challenge. <\/p>\n
Challenge #2: Render the uMaskBuffer to the screen to confirm it is the output of the second camera. \n<\/p><\/blockquote>\n
One thing to be aware of is that the render target is set up in the initialize of CameraMask.js, and that needs to be ready by the time Refraction.js is called. If the scripts run the other way around, you’ll get an error. To make sure they run in the right order, drag the CameraMask to the top of the entity list in the editor, as shown below.<\/p>\n
\"PlayCanvas<\/figure>\n
The second camera should always be looking at the same view as the original one, so let’s make it always follow its position and rotation in the update of CameraMask.js:<\/p>\n
CameraMask.prototype.update = function(dt) { var pos = this.CameraToFollow.getPosition(); var rot = this.CameraToFollow.getRotation(); this.entity.setPosition(pos.x,pos.y,pos.z); this.entity.setRotation(rot);\n};<\/pre>\n
And define CameraToFollow<\/code> in the initialize:<\/p>\n
this.CameraToFollow = this.app.root.findByName('Camera');<\/pre>\n
Culling Masks
\n<\/h3>\n
Both cameras are currently rendering the same thing. We want the mask camera to render everything except the real water, and we want the real camera to render everything except the mask water.<\/p>\n
To do this, we can use the camera’s culling bit mask. This works similarly to collision masks<\/a> if you’ve ever used those. An object will be culled (not rendered) if the result of a bitwise AND<\/code> between its mask and the camera mask is 1. <\/p>\n
Let’s say the Water will have bit 2 set, and WaterMask will have bit 3. Then the real camera needs to have all bits set except for 3, and the mask camera needs to have all bits set except for 2. An easy way to say “all bits except N” is to do:<\/p>\n
~(1 << N) >>> 0<\/pre>\n
You can read more about bitwise operators here<\/a>. <\/p>\n
To set up the camera culling masks, we can put this inside CameraMask.js’<\/strong>s initialize at the bottom:<\/p>\n
 \/\/ Set all bits except for 2 this.entity.camera.camera.cullingMask &= ~(1 << 2) >>> 0; \/\/ Set all bits except for 3 this.CameraToFollow.camera.camera.cullingMask &= ~(1 << 3) >>> 0; \/\/ If you want to print out this bit mask, try: \/\/ console.log((this.CameraToFollow.camera.camera.cullingMask >>> 0).toString(2));<\/pre>\n
Now, in Water.js, set the Water mesh’s mask on bit 2, and the mask version of it on bit 3:<\/p>\n
\/\/ Put this at the bottom of the initialize of Water.js \/\/ Set the culling masks var bit = this.isMask ? 3 : 2; meshInstance.mask = 0; meshInstance.mask |= (1 << bit);<\/pre>\n
Now, one view will have the normal water, and the other will have the solid white water. The left half of the image below is the view from the original camera, and the right half is from the mask camera.<\/p>\n
\"Split<\/figure>\n
Applying the Mask<\/h3>\n
One final step now! We know the areas underwater are marked with white pixels. We just need to check if we’re not at a white pixel, and if so, turn off the distortion in Refraction.frag<\/strong>:<\/p>\n
\/\/ Check original position as well as new distorted position\nvec4 maskColor = texture2D(uMaskBuffer, pos);\nvec4 maskColor2 = texture2D(uMaskBuffer, vUv0);\n\/\/ We're not at a white pixel?\nif(maskColor != vec4(1.0) || maskColor2 != vec4(1.0)){ \/\/ Return it back to the original position pos = vUv0;\n}<\/pre>\n
And that should do it! <\/p>\n
One thing to note is that since the texture for the mask is initialized on launch, if you resize the window at runtime, it will no longer match the size of the screen. <\/em><\/p>\n
Anti-Aliasing<\/h3>\n
As an optional clean-up step, you might have noticed that edges in the scene now look a little sharp. This is because when we applied our post effect, we lost anti-aliasing.\u00a0<\/p>\n
We can apply an additional anti-alias on top of our effect as another post effect. Luckily, there’s one available in the PlayCanvas store<\/a> we can just use. Go to the script asset page<\/a>, click the big green download button, and choose your project from the list that appears. The script will appear in the root of your asset window as posteffect-fxaa.js<\/strong>. Just attach this to the Camera entity, and your scene should look a little nicer!\u00a0 <\/p>\n
Final Thoughts
\n<\/h2>\n
If you’ve made it this far, give yourself a pat on the back! We covered a lot of techniques in this series. You should now be comfortable with vertex shaders, rendering to textures, applying post-processing effects, selectively culling objects, using the depth buffer, and working with blending and transparency. Even though we were implementing this in PlayCanvas, these are all general graphics concepts you’ll find in some form on whatever platform you end up in.<\/p>\n
All these techniques are also applicable to a variety of other effects. One particularly interesting application I’ve found of vertex shaders is in this talk on the art of Abzu<\/a>,\u00a0where they explain how they used vertex shaders to efficiently animate tens of thousands of fish on screen. <\/p>\n
You should now also have a nice water effect you can apply to your games! You could easily customize it now that you’ve put together every detail yourself. There’s still a lot more you can do with water (I haven’t even mentioned any sort of reflection at all). Below are a couple of ideas.<\/p>\n
Noise-Based Waves
\n<\/h4>\n
Instead of simply animating the waves with a combination of sine and cosines, you can sample a noise texture to make the waves look a bit more natural and unpredictable. <\/p>\n
Dynamic Foam Trails<\/h4>\n
Instead of completely static water lines on the surface, you could draw onto that texture when objects move, to create a dynamic foam trail. There are a lot of ways to go about doing this, so this could be its own project. <\/p>\n
Source Code<\/h2>\n
You can find the finished hosted PlayCanvas project here<\/a>. A Three.js port is also available in this repository<\/a>.<\/p>\n
<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"
Welcome back to this three-part series on creating stylized toon water in PlayCanvas using vertex shaders.\u00a0In Part 2 we covered buoyancy & foam lines. In this final part, we’re going to apply the underwater distortion as a post-process effect. Refraction & Post-Process Effects Our goal is to visually communicate the refraction of light through water. […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-91254","post","type-post","status-publish","format-standard","hentry","category-tutorials"],"_links":{"self":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/91254","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/comments?post=91254"}],"version-history":[{"count":0,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/91254\/revisions"}],"wp:attachment":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/media?parent=91254"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/categories?post=91254"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/tags?post=91254"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}