Sign in to follow this  
Luca D

OpenGL Bump Mapping with CG

Recommended Posts

Hi, I'm trying to implement bump mapping in a demo application. If I'm right I could: - use the original Blinn's idea modifing the vertex normals -> I'd need meshes with lots of polygons, because it's "per-vertex"; - use the hardware capability of modern graphics card with the new opengl multitexture features; - use fragment shaders. Since I've never studied shaders I'd like to try this way. I already have a class which contains a mesh and has a rendering method. Let's suppose to add two private attributes such as:
private bool bumpMapping;
private const char *bumpMap;

At runtime, I will have some objects which need Bump Mapping and will have the boolean = true. How would the rendering method change? Should I load the fragment shader when the application starts, and then in the rendering method do:
void Render()
{
    if(bumpMapping)
    {
        glPushAttrib(GL_CURRENT_BIT | GL_LIGHTING_BIT | GL_TEXTURE_BIT);
        cgGLBindProgram(...);
        cgGLEnableProfile(...);
        cgGLSetParameter3fv(...);
        cgGLSetParameter3fv(...);
        cgGLSetParameter3fv(...);
    }

    // Drawing...
    glBegin(...);
    ...
    glEnd();

    if(bumpMapping)
    {
        cgGLDisableProfile(...);
        glPopAttrib();
    }
}

Thanks for any advice :)

Share this post


Link to post
Share on other sites
Yes. You also need to bind and enable/disable the texture for the bump map, using

cgGLSetTextureParameter(param, bumpMapID)

to set the texture, and

cgGLEnableTextureParameter( param ),

cgGLDisableTextureParameter( param )

TO enable/disable

Share this post


Link to post
Share on other sites
I'm following this tutorial:
http://www.gamedev.net/reference/articles/article1903.asp
but there are a few things not clear..


for every vertex in the triangle {
// Bind the light vector to COLOR0 and interpolate
// it across the edge
glColor3f([lightx], [lighty], [lightz]);



The fragment shader needs the light vector as input, and here it seems it is passed with glColor.. is it something like a trick or there's a meaning I can't understand?
Moreover, the comment says "interpolate".. what does it mean? The shader will receive the light vector for each vertex and will it automatically interpolate this vector along each edge of the triangles?

About texture management you suggested the method
cgGLSetTextureParameter3fv
to bind the bump texture, but in that piece of code it isn't used, while there's:
glActiveTextureARB(GL_TEXTURE1_ARB);
glEnable(GL_TEXTURE_2D);
glBindTexture(GL_TEXTURE_2D, material.getNormalmapHandle());
glMultiTexCoord2fARB(.glMultiTexCoord2fARB(GL_TEXTURE0_ARB,
texture[Vector::X], texture[Vector::Y]);
Is it the same?
There's also this method:
glSecondaryColor3fvEXT
I looked it up with google and on the opengl website, but found nothing: isn't it commonly used? It isn't even present in the CG Reference Manual..
Sorry for the mess of arguments, but for example, regarding the question of the interpolation, where am I supposed to get information?
In Cg-2.2_April2009_ReferenceManual.pdf, pag. 614, there's a table about "VARYING INPUT SEMANTICS - Interpolated Input Semantics", but it's not really explained..
Thanks.

Share this post


Link to post
Share on other sites
Quote:
Original post by Luca D

The fragment shader needs the light vector as input, and here it seems it is passed with glColor.. is it something like a trick or there's a meaning I can't understand?
Moreover, the comment says "interpolate".. what does it mean? The shader will receive the light vector for each vertex and will it automatically interpolate this vector along each edge of the triangles?



Yes. If you know the light position and the position of the vertex, then you can compute the "light vector". Because you are using a pixel shader, you can use the color parameter for whatever you want. Specifying it as a color merely tells CG to pack the color values into the lightVector variable in the pixel shader.

The advantage of this method is that OpenGL automatically interpolates the light vector between vertices (so you don't have to), and it is probably faster.

What makes this an annoying method is that

(1) OpenGL may or may not clamp color input values to [0,1], meaning you have to pack the light vector so that all components are between 0 and 1 (this is what the tutorial does)

(2) You waste bandwidth with redundant data

My method would be to pass the light position (in your coordinate system) as a uniform value to a vertex shader in eye coordinates. You can then compute the light vector using the vertex shader for every vertex (after you transform it to eye coordinates). and pass it on in whatever variable you want (color/texture etc). This is almost certainly faster and reduces bandwidth.

Quote:
Original post by Luca D

About texture management you suggested the method
cgGLSetTextureParameter3fv
to bind the bump texture, but in that piece of code it isn't used, while there's:
glActiveTextureARB(GL_TEXTURE1_ARB);
glEnable(GL_TEXTURE_2D);
glBindTexture(GL_TEXTURE_2D, material.getNormalmapHandle());
glMultiTexCoord2fARB(.glMultiTexCoord2fARB(GL_TEXTURE0_ARB,
texture[Vector::X], texture[Vector::Y]);
Is it the same?


Yes. I have never used this - I use settextureparameter, but they do the same thing

Quote:
Original post by Luca D
There's also this method:
glSecondaryColor3fvEXT
I looked it up with google and on the opengl website, but found nothing: isn't it commonly used? It isn't even present in the CG Reference Manual..


glColor3f gets mapped to COLOR0 in the pixel shader. If you want to use COLOR1 etc, you need these functions to specify them (in the original OpenGL implementation no one conceived that you would ever need more than one color).

Quote:
Original post by Luca D
Sorry for the mess of arguments, but for example, regarding the question of the interpolation, where am I supposed to get information?
In Cg-2.2_April2009_ReferenceManual.pdf, pag. 614, there's a table about "VARYING INPUT SEMANTICS - Interpolated Input Semantics", but it's not really explained..
Thanks.


I have never used these - I have always used the built in interpolation (which is what you need to do bumpmapping).

As far as number of vertices, you don't need that many - thats the beauty of interpolation

Share this post


Link to post
Share on other sites
Ok, thanks for your answer, I'm working on what you suggested.
Studying shaders, I thought: OpenGL has only flat and gouroud illumination models (glShadeModel(GL_FLAT) and glShadeModel(GL_SMOOTH)), right?
Now, thanks to shaders, it should be very simple to realize the phong model. Is it commonly done? Does it considerably improve the visual quality?

Share this post


Link to post
Share on other sites
I've gone through all the tutorial and code, but I'd need an help to implement bump mapping in my code.
The main idea of the tutorial is to:
- calculate the objectToTangentSpace matrix transformation for each vertex of the mesh when the model is loaded.
- in the draw method of the mesh, for each vertex, bring light and half vector into tangent space and then pass all the necessary information to the fragment shader with the methods glColor3fv, glSecondaryColor3fvEXT, glMultiTexCoord2fARB, etc..
Everything is done inside glBegin(GL_TRIANGLES) and glEnd().
My problem is that I'm drawing the model with:
glVertexPointer(...);
glNormalPointer(...);
glTexCoordPointer(...);
glDrawArrays(GL_TRIANGLES, ...);
How can I pass all those parameters, for each vertex, since I'm working with array pointers?
Hope it's clear,
thanks

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
      628354
    • Total Posts
      2982236
  • Similar Content

    • By test opty
      Hi all,
       
      I'm starting OpenGL using a tut on the Web. But at this point I would like to know the primitives needed for creating a window using OpenGL. So on Windows and using MS VS 2017, what is the simplest code required to render a window with the title of "First Rectangle", please?
       
       
    • 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.
  • Popular Now