Sign in to follow this  
sofakng

OpenGL How can I learn the different blending types? (eg. additive, solid, alpha, etc...)

Recommended Posts

I'd like to create a simple 2D game and it seems like "blending" type is very important. If I understand correctly, the blending is used to determine what to do if you're drawing on top of existing pixels. (eg. drawing a blue quad on top of a red quad). I'm not sure which API I'll be using (OpenGL or DirectX), but I was wondering if any really in-depth tutorials (or examples) exist for teaching me the differences between them (and tips on when to use each type). Thanks... - John

Share this post


Link to post
Share on other sites
In the recent DirectX SDK versions there is a tutorial called "Tutorial 14: State Management" that goes over quite a bit about the differences in blending, culling, stenciling and other things having to do with device state changes. The documentation with the tutorial is also very easy to understand. The app itself allows you to toggle a bunch of different states and blend functions to see the results.

You can grab the latest SDK version here.

Hope this helps.

Share this post


Link to post
Share on other sites
Blending is one of the most simple, and yet most-oft confused concepts in graphics. It simply determines what happens when a fragment (pixel, color) is to be drawn to the screen (texture, wherever).

The equation used is:

Result = Source * SourceFunction + Destination * DestinationFunction

That's it!

Result is the final color output to the screen.
Source is the "new" color that has been generated.
Destination is the color that was previously in the framebuffer at that location.

The two functions are what makes it so powerful, and make it actually useful.

Some functions include:
One, Zero, Source Alpha, One Minus Source Alpha, etc (look them up!).

Basically, by specifying the correct functions, you can create a variety of blending effects. If you specify, for example, One for your SourceFunction, and Zero for your DestinationFunction, the equation simplifies down to:

Result = Source

Basically, no blending at all!

Specifying (One, One) (One for the SourceFunc and One for the DestFunc) will give you:

Result = Source + Destination - additive blending! The two colors will be added together to give the final result color!

Transparency can be done using (One, One Minus Source Alpha) - the equation becomes

Result = Source + (1 - Source.A)*Destination - the amount of color that shows through the new fragment is scaled by the alpha value of the source texture. If you specify your source color from a texture, you can use the texture's alpha channel to determine how much "light" to let through!

Basically, I suggest you look up the different functions you can use (there are really only a small number of them), and work out the math so you can see exactly what is being accomplished.

Share this post


Link to post
Share on other sites
Thanks for the very helpful information!

If I understand correctly,

One = The color just as it is
Zero = Don't use any color

So...

Source (Zero) + Destination (One) = Destination just as it was before [eg. no change, aka pointless??]

Source (One) + Destination (Zero) = The source just as it is and ignore what was previously there

Thanks again for the help!!

Share this post


Link to post
Share on other sites
Just an extra note. You can change the + in the middle of the equation. In D3D it's D3DRS_BLENDOP. You can use subtract(src-dest), revsubtract (dest-src), min, and max.

Also, in D3D9, some cards allow you to blend the alpha seperately with it's own blending options, which can be useful in some cases. (Only useful if you've made a backbuffer or render target that contains alpha bits).

Share this post


Link to post
Share on other sites
Wow... it seems like there is a metric crap-load of different ways to blend colors together.

Even after I understand what is going on for each different blending operation, how in the world would I know when to use them? Right now I can understand how alpha-blending could be used, but I have no idea for the other modes. It seems like each of them is for creating special effects? (but how do you even begin to realize what the special effect will look like unless you try every single mode?)

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  

  • Forum Statistics

    • Total Topics
      627740
    • Total Posts
      2978884
  • Similar Content

    • By DelicateTreeFrog
      Hello! As an exercise for delving into modern OpenGL, I'm creating a simple .obj renderer. I want to support things like varying degrees of specularity, geometry opacity, things like that, on a per-material basis. Different materials can also have different textures. Basic .obj necessities. I've done this in old school OpenGL, but modern OpenGL has its own thing going on, and I'd like to conform as closely to the standards as possible so as to keep the program running correctly, and I'm hoping to avoid picking up bad habits this early on.
      Reading around on the OpenGL Wiki, one tip in particular really stands out to me on this page:
      For something like a renderer for .obj files, this sort of thing seems almost ideal, but according to the wiki, it's a bad idea. Interesting to note!
      So, here's what the plan is so far as far as loading goes:
      Set up a type for materials so that materials can be created and destroyed. They will contain things like diffuse color, diffuse texture, geometry opacity, and so on, for each material in the .mtl file. Since .obj files are conveniently split up by material, I can load different groups of vertices/normals/UVs and triangles into different blocks of data for different models. When it comes to the rendering, I get a bit lost. I can either:
      Between drawing triangle groups, call glUseProgram to use a different shader for that particular geometry (so a unique shader just for the material that is shared by this triangle group). or
      Between drawing triangle groups, call glUniform a few times to adjust different parameters within the "master shader", such as specularity, diffuse color, and geometry opacity. In both cases, I still have to call glBindTexture between drawing triangle groups in order to bind the diffuse texture used by the material, so there doesn't seem to be a way around having the CPU do *something* during the rendering process instead of letting the GPU do everything all at once.
      The second option here seems less cluttered, however. There are less shaders to keep up with while one "master shader" handles it all. I don't have to duplicate any code or compile multiple shaders. Arguably, I could always have the shader program for each material be embedded in the material itself, and be auto-generated upon loading the material from the .mtl file. But this still leads to constantly calling glUseProgram, much more than is probably necessary in order to properly render the .obj. There seem to be a number of differing opinions on if it's okay to use hundreds of shaders or if it's best to just use tens of shaders.
      So, ultimately, what is the "right" way to do this? Does using a "master shader" (or a few variants of one) bog down the system compared to using hundreds of shader programs each dedicated to their own corresponding materials? Keeping in mind that the "master shaders" would have to track these additional uniforms and potentially have numerous branches of ifs, it may be possible that the ifs will lead to additional and unnecessary processing. But would that more expensive than constantly calling glUseProgram to switch shaders, or storing the shaders to begin with?
      With all these angles to consider, it's difficult to come to a conclusion. Both possible methods work, and both seem rather convenient for their own reasons, but which is the most performant? Please help this beginner/dummy understand. Thank you!
    • By JJCDeveloper
      I want to make professional java 3d game with server program and database,packet handling for multiplayer and client-server communicating,maps rendering,models,and stuffs Which aspect of java can I learn and where can I learn java Lwjgl OpenGL rendering Like minecraft and world of tanks
    • By AyeRonTarpas
      A friend of mine and I are making a 2D game engine as a learning experience and to hopefully build upon the experience in the long run.

      -What I'm using:
          C++;. Since im learning this language while in college and its one of the popular language to make games with why not.     Visual Studios; Im using a windows so yea.     SDL or GLFW; was thinking about SDL since i do some research on it where it is catching my interest but i hear SDL is a huge package compared to GLFW, so i may do GLFW to start with as learning since i may get overwhelmed with SDL.  
      -Questions
      Knowing what we want in the engine what should our main focus be in terms of learning. File managements, with headers, functions ect. How can i properly manage files with out confusing myself and my friend when sharing code. Alternative to Visual studios: My friend has a mac and cant properly use Vis studios, is there another alternative to it?  
    • By ferreiradaselva
      Both functions are available since 3.0, and I'm currently using `glMapBuffer()`, which works fine.
      But, I was wondering if anyone has experienced advantage in using `glMapBufferRange()`, which allows to specify the range of the mapped buffer. Could this be only a safety measure or does it improve performance?
      Note: I'm not asking about glBufferSubData()/glBufferData. Those two are irrelevant in this case.
    • By xhcao
      Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness. 
  • Popular Now