Sign in to follow this  
luridcortex

OpenGL Image Space Motion Blur Algorithm

Recommended Posts

luridcortex    162
Im trying to implement the motion blur algorithm described in the paper "Stupid OpenGL Shader Tricks" -> http://developer.nvidia.com/docs/IO/8230/GDC2003_OpenGLShaderTricks.pdf by Simon Green. Im having a some trouble visualizing the order of operations in the algorithm. In the slides it goes as such: 1. Render current scene to texture 2. Calculate velocity at each pixel 3. Render motion blurred scene What I am doing is: 1. Rendering scene to texture 2. Render blurred scene to texture a. Calculate velocity from prev frame to cur frame in vertex shader b. Sample prev render frame and cur render frame in frag shader 3. Blend blurred scene over cur render frame Im just getting a little confused as to whether the final render should be applied as a post process effect or not. I guess you would have to split it up into two steps and have the fragment shader write the velocity to a texture?

Share this post


Link to post
Share on other sites
joanusdmentia    1060
While I haven't looked at the paper, I would have thought you'd be able to perform steps 2 & 3 in one fragment shader. You're already accessing the current frame's texture in step 2 so why not perform the blend (which I'm presuming is just a normal pixel-by-pixel blend) at the same time?

Share this post


Link to post
Share on other sites
luridcortex    162
Yeah, that is how I am doing it. I had just confused myself with how the blur would be applied 'outside' of the image. But thats what the whole geometry stretching deal solves... even tho I dont see this effect in the nvidia demo.

Share this post


Link to post
Share on other sites
OrangyTang    1298
Quote:
Original post by luridcortex
What I am doing is:

1. Rendering scene to texture
2. Render blurred scene to texture

a. Calculate velocity from prev frame to cur frame in vertex shader
b. Sample prev render frame and cur render frame in frag shader

3. Blend blurred scene over cur render frame

You can't just blur the scene beforehand (your step 2) as the velocity is supposed to affect the direction of the blur at that pixel.

Step 2 and 3 (calc velocity and add blur) should be done in one pass. The vertex shader extrudes the mesh and generates the velocity as the output colour. The pixel shader then uses this velocity to take multiple samples *of the original scene* to generate the directional blur for this pixel.

Share this post


Link to post
Share on other sites
luridcortex    162
I meant a/b to part of step 2, a little confusing, sorry!

Thanks for the explanation OrangyTang :)

The main problem I am having now is with calculating the previous vertex position. I was using the trick in the demo to transform the incoming vertex by the previous modelview matrix. However I am thinking this wont work in my case since I am testing with an animated model using vertex animation.

edit: Problem solved, maybe! Anyway, I just wasnt getting the correct modelview from the application - the above formula should work I think.


[Edited by - luridcortex on April 16, 2006 9:56:27 PM]

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Similar Content

    • By povilaslt2
      Hello. I'm Programmer who is in search of 2D game project who preferably uses OpenGL and C++. You can see my projects in GitHub. Project genre doesn't matter (except MMO's :D).
    • By ZeldaFan555
      Hello, My name is Matt. I am a programmer. I mostly use Java, but can use C++ and various other languages. I'm looking for someone to partner up with for random projects, preferably using OpenGL, though I'd be open to just about anything. If you're interested you can contact me on Skype or on here, thank you!
      Skype: Mangodoor408
    • By tyhender
      Hello, my name is Mark. I'm hobby programmer. 
      So recently,I thought that it's good idea to find people to create a full 3D engine. I'm looking for people experienced in scripting 3D shaders and implementing physics into engine(game)(we are going to use the React physics engine). 
      And,ye,no money =D I'm just looking for hobbyists that will be proud of their work. If engine(or game) will have financial succes,well,then maybe =D
      Sorry for late replies.
      I mostly give more information when people PM me,but this post is REALLY short,even for me =D
      So here's few more points:
      Engine will use openGL and SDL for graphics. It will use React3D physics library for physics simulation. Engine(most probably,atleast for the first part) won't have graphical fron-end,it will be a framework . I think final engine should be enough to set up an FPS in a couple of minutes. A bit about my self:
      I've been programming for 7 years total. I learned very slowly it as "secondary interesting thing" for like 3 years, but then began to script more seriously.  My primary language is C++,which we are going to use for the engine. Yes,I did 3D graphics with physics simulation before. No, my portfolio isn't very impressive. I'm working on that No,I wasn't employed officially. If anybody need to know more PM me. 
       
    • By Zaphyk
      I am developing my engine using the OpenGL 3.3 compatibility profile. It runs as expected on my NVIDIA card and on my Intel Card however when I tried it on an AMD setup it ran 3 times worse than on the other setups. Could this be a AMD driver thing or is this probably a problem with my OGL code? Could a different code standard create such bad performance?
    • By Kjell Andersson
      I'm trying to get some legacy OpenGL code to run with a shader pipeline,
      The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
      I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
      I've got a version 330 vertex shader to somewhat work:
      #version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
      What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
      Question:
      What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?
       
      Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.
  • Popular Now