Sign in to follow this  
riruilo

OpenGL Questions about transparents meshes (alpha blending and z order) [solved]

Recommended Posts

Hi friends. I need your ideas, please. I would like to implement transparent objets in my very small engine, OpenGL of course. I know I should draw firstly all my opaque objects, and after that, my transparent objects. But! from back to front, and that is my problem. How can I implement it. My idea is to take in account just one vertex per one mesh (not every triangles), my mesh class has a GetFirstVertx method. After do a traverse I can use glGetCurrentMatrix to retrieve the currrent matrix when I am in that object, but how can I get Z? If I get that my idea is to implement a method called SetZorder and GetZorder. After get Z, I think it should be easy, just order all my meshes and render them from back to front. Can anyone help me with my implementation questions? Thank you very much. [Edited by - riruilo on May 8, 2007 10:30:08 AM]

Share this post


Link to post
Share on other sites
Forget about a so accurate sort. Besides killing your CPU, it still won't give correct results. Solving blend is a per-fragment problem.

If you REALLY need "pixel-perfect" transparency, you should look at order independant transparency and depth peeling.

In general, there are little subsets in which this is necessary. A per-OBB test would be enough.

Share this post


Link to post
Share on other sites
First you need a method that gives you the translation from model-space to world-space (the objects position).

Just sort by the distance from the camera to the objects position.

i.e.
v = cam.position - obj.position;
d = sqrt(v.x*v.x + v.y*v.y + v.z*v.z);
then sort on d

Share this post


Link to post
Share on other sites
Just be careful that if you sort by bounds/object centers, then a (large) object can be visible and have its center behind the camera (such as a large window) - in the distance from camera method above this will result in incorrect ordering. You may wish to consider adding testing againt the camera near plane to see if it is behind, and allow your algorithm to sort on negative numbers too.

Share this post


Link to post
Share on other sites
Thanks for your replies.

But I have 2 questions.

First all, I am Opengl beginner ( and english), maybe my questions are a bit stupid.

I have one arbitrary vertex of my model, in local coordinates, that vertex is transformed by modelview matrix. What operation should I do to get the transformed vertex?

And just one question more. (possibly I am wrong)

Before render my scene, I use glrotate and gltranslate with opposite values to move my world, that is to move the camera, but actually I am moving my world, not my camera. So, should I use this:

v = cam.position - obj.position;
d = sqrt(v.x*v.x + v.y*v.y + v.z*v.z);

Simply I have no camera.

Thanks a lot, I appreciate a lot your help.

Share this post


Link to post
Share on other sites
Quote:
Original post by riruilo
Thanks for your replies.

But I have 2 questions.

First all, I am Opengl beginner ( and english), maybe my questions are a bit stupid.

I have one arbitrary vertex of my model, in local coordinates, that vertex is transformed by modelview matrix. What operation should I do to get the transformed vertex?

And just one question more. (possibly I am wrong)

Before render my scene, I use glrotate and gltranslate with opposite values to move my world, that is to move the camera, but actually I am moving my world, not my camera. So, should I use this:

v = cam.position - obj.position;
d = sqrt(v.x*v.x + v.y*v.y + v.z*v.z);

Simply I have no camera.

Thanks a lot, I appreciate a lot your help.
I would think the easiest approach would be to simply transform the position of each object into camera/view space, and then sort by z value.

All you would really need would be:
depth[i] = dot(object[i].pos - camera.pos, camera.forward);
You should have your camera position available (since as you state, you're calling glTranslate() with the negative of this vector).

Ideally you should have the forward vector available as well (or be able to derive it), but if you're relying exclusively on glRotate*() this may not be the case.

Another option would be to query the modelview matrix (which at any time represents a transformation from local space to view space), apply it to your object origins, and sort based on the resulting z values.

FYI, this sort of thing is a lot easier if you use an external math library, rather than relying exclusively on OpenGL's transform functions.

Share this post


Link to post
Share on other sites
Thanks jyk

A math library? for what? for instance....

An other question, I have a transformation matrix and one vertex, what should I do to get the transformed vertex.

Thanks a lot.

Share this post


Link to post
Share on other sites
Quote:
A math library? for what? for instance...
If you're asking why a math library can be useful when working with OpenGL, the answer (in short) is that it allows you to do things that are either difficult or impossible to do solely though OpenGL transform functions.
Quote:
An other question, I have a transformation matrix and one vertex, what should I do to get the transformed vertex.
This is a good example :) OpenGL does not provide a means of 'manually' transforming geometry, or querying the geometry data after transformation, but if you have a decent math library available, this becomes quite easy. (You can do it indirectly via OpenGL, but you'd have to query the modelview matrix at the appropriate time, and then apply the transformation 'by hand' to the vertex in question.)

Share this post


Link to post
Share on other sites
Thanks jyk, you are very helpful for me.



Just one question, I promise this is the LAST.

I have the modelview matrix using glGetMatrix(modelview) and one vertex, how can I apply that transformation BY HAND to that vertex? or which theory should I know ( I´m beginnger)

By the way, I need just that operation so maybe use a library for that is not useful, I think ( maybe I am wrong )

Thanks.

Share this post


Link to post
Share on other sites
Quote:
I have the modelview matrix using glGetMatrix(modelview) and one vertex, how can I apply that transformation BY HAND to that vertex? or which theory should I know ( I´m beginnger)
To multiply a vector by a matrix (representing an affine transform) using OpenGL conventions:
x' = m[0] * x + m[4] * y + m[8] * z + m[12];
y' = m[1] * x + m[5] * y + m[9] * z + m[13];
z' = m[2] * x + m[6] * y + m[10] * z + m[14];
To learn more about what's going on here, Google 'matrix math', 'vector math', 'matrix multiplication', 'matrix vector multiplication', and similar terms. Or, just consult a good reference on linear algebra.
Quote:
By the way, I need just that operation so maybe use a library for that is not useful, I think ( maybe I am wrong )
The more 3-d programming you do, the more difficult it will become to get by without a math library. However, you can probably squeeze by without one for the time being if what you're doing isn't too involved.

Share this post


Link to post
Share on other sites
Hi friends! It works nice. Thanks a lot.

But just one thing:

I only use
glGetMatrix(modelview) and one vertex to calculate a transformed vertex with

z' = m[2] * x + m[6] * y + m[10] * z + m[14];

I dont use any camera position, because there is no camera in opengl, and when aI transform my "virtual" camera, its transformations are stored in modelview, so I didnt use:

depth[i] = dot(object[i].pos - camera.pos, camera.forward);

A screeshoot, look at lights and window panes (glass):

Image Hosted by ImageShack.us

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
      628329
    • Total Posts
      2982103
  • 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