Sign in to follow this  
eigers

OpenGL Separate alpha blend enable states for MRT

Recommended Posts

Hello everyone, My application uses D3D9. I have a main render target into which the scene is rendered, and an additional render target used for writing some data which I'm using later. My problem is that when the scene is rendered with alpha blending enabled, my second RT gets blended as well, which produces meaningless values. Is there a way in D3D9 to enable alpha blending only for a specific RT? The D3D docs don't mention such an option, but I know that in OpenGL it's possible with some extension (DrawBuffers2 I think), so it's not a hardware limitation. Thanks.

Share this post


Link to post
Share on other sites
D3D10 you mean I guess...
That's the answer I was afraid of... I can't move to D3D10. Isn't there some hack to do this in D3D9, like a secret format or something (even NV-only will be fine)? I know there are formats which don't undergo any post pixel shader operations, but for some reason I couldn't get them to work properly.

Share this post


Link to post
Share on other sites
I think that though alpha blending is enabled for all render targets, the alpha of a specific target will be used for that target's rendering. In that case, just setting the alpha to 1 for the second RT will solve the problem. You're losing one output component, but that shouldn't be an insurmountable problem.

Share this post


Link to post
Share on other sites
For the source it's understood, because the pixel shader always outputs a 4-component vector, but what about the destination, which doesn't store the alpha component at all? Is it always expanded to 1?

Share this post


Link to post
Share on other sites
Actually no, I don't really have a problem there. But I do have a problem with blending modes which use the destination color (e.g. D3DRS_DESTBLEND = D3DBLEND_ONE), as I don't want the second RT blended at all.
It seems that there really is no way around this in D3D9...

Share this post


Link to post
Share on other sites
What about premultiplied alpha ?

RT1 : I want src to be multiplied by alpha and dst to be multiplied by 1-alpha and both be added together : final1 = (1-alpha1) * dstcolor1 + alpha1 *srccolor1
RT2 : I want src to be overwritten over dst : final2 = 1 * srccolor2 + 0 * dstcolor2

As a blend op you take D3DOP_ADD obviously.
As blend source you take D3DBLEND_ONE (<- important in the premultiplied alpha case)
As blend dest you take D3DBLEND_INVSRCALPHA

when you write color 0 in your pixel shader you do :
mul r0.rgb, r0.rgbb, r0.aaaa
mov oC0, r0

Assuming ro.aaaa contained alpha1 and r0.rgb contained srcColor1.rgb
oC0.rgb then contains srccolor1.rgb * alpha1
oC0.a then contains alpha1
the result of the equation is oC0.rgba * ONE + destcolor1 * (1 - oC0.a)
or srcColor1.rgb * alpha1 + destcolor1.rgb * (1 - alpha1) which is what you wanted.

when you write color 1 you :
mov r1.a, constant(1.0,1.0,1.0,1.0)
mov oC1, r1

oC1.rgb contains srcColor2.rgb
oC1.a contains 1
the result of the equation is oC1.rgb * ONE + destcolor2 * (1 - oC1.a)
or srcColor2.rgb + destColor2.rgb * 0 which is also what you wanted.

The only problem with this approach obviously is that you've replaced the alpha value. But that's a general problem with blending is that it always assume the fourth channel of anything is going to be the blending factor (and that is also true for single RT case) which means in alpha blending situations you can only effectively write 3 components at a time per rendertarget.. Use more RTs (in MRT mode) if you want to write more.

LeGreg

Share this post


Link to post
Share on other sites
Thanks for this interseting idea.

However, as ET3D pointed out, each RT is blended with its own alpha, so I don't really have a problem with the SRCALPHA/INVSRCALPHA type of blending. I just set the source alpha to 1 when writing to oC1, and so the destination is overwritten.
My problem is with blending states where the factor of the destination color is not related to the source at all (such as D3DRS_DESTBLEND = D3DBLEND_ONE), which are generally used for glowing effects. I don't see how I can overcome this without knowing the current destination color, which of course I can't. Am I'm missing something here?

Share this post


Link to post
Share on other sites
Quote:
Original post by eigers
However, as ET3D pointed out, each RT is blended with its own alpha, so I don't really have a problem with the SRCALPHA/INVSRCALPHA type of blending. I just set the source alpha to 1 when writing to oC1, and so the destination is overwritten.
My problem is with blending states where the factor of the destination color is not related to the source at all (such as D3DRS_DESTBLEND = D3DBLEND_ONE), which are generally used for glowing effects. I don't see how I can overcome this without knowing the current destination color, which of course I can't. Am I'm missing something here?


Didn't I just tell you how ? Sorry if that wasn't clear..

The problem you had was that you were using SRCALPHA/INVSRCALPHA, where what you wanted was the premultiplied alpha.

If you want to replace, you set output alpha to one (without changing the source color). If you want to add (src+dst as in the glow effect) you output alpha to zero : that way dest is multiplied by (1-zero) before being added to the srccolor (that you don't modify either). You can also emulate the srcalpha/invsrcalpha case by premultiplying (hence the premultiplied alpha name) the srccolor by the alpha before outputing it.

A thing that doesn't work with this approach is if you want different alpha per channel to affect the dest color before combining (say dest.r * (1- alpha1), dest.g * (1 - alpha2), dest.b * (1 - alpha3) ). Well that level would require an extra color being output and used in the blend equation, which is only possible in dual blend mode using the Direct3D10 API.

LeGreg

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  

  • Announcements

  • Forum Statistics

    • Total Topics
      628334
    • Total Posts
      2982147
  • Similar Content

    • By DejayHextrix
      Hi, New here. 
      I need some help. My fiance and I like to play this mobile game online that goes by real time. Her and I are always working but when we have free time we like to play this game. We don't always got time throughout the day to Queue Buildings, troops, Upgrades....etc.... 
      I was told to look into DLL Injection and OpenGL/DirectX Hooking. Is this true? Is this what I need to learn? 
      How do I read the Android files, or modify the files, or get the in-game tags/variables for the game I want? 
      Any assistance on this would be most appreciated. I been everywhere and seems no one knows or is to lazy to help me out. It would be nice to have assistance for once. I don't know what I need to learn. 
      So links of topics I need to learn within the comment section would be SOOOOO.....Helpful. Anything to just get me started. 
      Thanks, 
      Dejay Hextrix 
    • By mellinoe
      Hi all,
      First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
      Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
      The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
      Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.
    • By aejt
      I recently started getting into graphics programming (2nd try, first try was many years ago) and I'm working on a 3d rendering engine which I hope to be able to make a 3D game with sooner or later. I have plenty of C++ experience, but not a lot when it comes to graphics, and while it's definitely going much better this time, I'm having trouble figuring out how assets are usually handled by engines.
      I'm not having trouble with handling the GPU resources, but more so with how the resources should be defined and used in the system (materials, models, etc).
      This is my plan now, I've implemented most of it except for the XML parts and factories and those are the ones I'm not sure of at all:
      I have these classes:
      For GPU resources:
      Geometry: holds and manages everything needed to render a geometry: VAO, VBO, EBO. Texture: holds and manages a texture which is loaded into the GPU. Shader: holds and manages a shader which is loaded into the GPU. For assets relying on GPU resources:
      Material: holds a shader resource, multiple texture resources, as well as uniform settings. Mesh: holds a geometry and a material. Model: holds multiple meshes, possibly in a tree structure to more easily support skinning later on? For handling GPU resources:
      ResourceCache<T>: T can be any resource loaded into the GPU. It owns these resources and only hands out handles to them on request (currently string identifiers are used when requesting handles, but all resources are stored in a vector and each handle only contains resource's index in that vector) Resource<T>: The handles given out from ResourceCache. The handles are reference counted and to get the underlying resource you simply deference like with pointers (*handle).  
      And my plan is to define everything into these XML documents to abstract away files:
      Resources.xml for ref-counted GPU resources (geometry, shaders, textures) Resources are assigned names/ids and resource files, and possibly some attributes (what vertex attributes does this geometry have? what vertex attributes does this shader expect? what uniforms does this shader use? and so on) Are reference counted using ResourceCache<T> Assets.xml for assets using the GPU resources (materials, meshes, models) Assets are not reference counted, but they hold handles to ref-counted resources. References the resources defined in Resources.xml by names/ids. The XMLs are loaded into some structure in memory which is then used for loading the resources/assets using factory classes:
      Factory classes for resources:
      For example, a texture factory could contain the texture definitions from the XML containing data about textures in the game, as well as a cache containing all loaded textures. This means it has mappings from each name/id to a file and when asked to load a texture with a name/id, it can look up its path and use a "BinaryLoader" to either load the file and create the resource directly, or asynchronously load the file's data into a queue which then can be read from later to create the resources synchronously in the GL context. These factories only return handles.
      Factory classes for assets:
      Much like for resources, these classes contain the definitions for the assets they can load. For example, with the definition the MaterialFactory will know which shader, textures and possibly uniform a certain material has, and with the help of TextureFactory and ShaderFactory, it can retrieve handles to the resources it needs (Shader + Textures), setup itself from XML data (uniform values), and return a created instance of requested material. These factories return actual instances, not handles (but the instances contain handles).
       
       
      Is this a good or commonly used approach? Is this going to bite me in the ass later on? Are there other more preferable approaches? Is this outside of the scope of a 3d renderer and should be on the engine side? I'd love to receive and kind of advice or suggestions!
      Thanks!
    • By nedondev
      I 'm learning how to create game by using opengl with c/c++ coding, so here is my fist game. In video description also have game contain in Dropbox. May be I will make it better in future.
      Thanks.
    • By Abecederia
      So I've recently started learning some GLSL and now I'm toying with a POM shader. I'm trying to optimize it and notice that it starts having issues at high texture sizes, especially with self-shadowing.
      Now I know POM is expensive either way, but would pulling the heightmap out of the normalmap alpha channel and in it's own 8bit texture make doing all those dozens of texture fetches more cheap? Or is everything in the cache aligned to 32bit anyway? I haven't implemented texture compression yet, I think that would help? But regardless, should there be a performance boost from decoupling the heightmap? I could also keep it in a lower resolution than the normalmap if that would improve performance.
      Any help is much appreciated, please keep in mind I'm somewhat of a newbie. Thanks!
  • Popular Now