• Advertisement
Sign in to follow this  

OpenGL Reflection Mapping and OpenGL's ModelView matrix problem

This topic is 2903 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I'm having a slight problem with getting reflection/environment mapping working, everything seems to work ok until I start moving the camera around the reflection does not follow with it, this is because I am using an 'eye-space' reflection vector to index a 'world-space' cube-map. here is the glsl code: vertex shader:
	varying vec3 reflectVec;
	void main()
		vec3 normal = normalize(gl_NormalMatrix * gl_Normal);
		gl_Position = ftransform();
		reflectVec = reflect(vec3(gl_ModelViewMatrix * gl_Vertex), normal);

fragment shader:
	uniform samplerCube tex;
	varying vec3 reflectVec;
	void main()
		gl_FragColor = textureCube( tex, normalize(reflectVec) );

Is there anyway to convert the reflection vector back into world space without it going through the Model matrix but just rather by the inverse of the View matrix so that it can access the cube map?

Share this post

Link to post
Share on other sites
Do you have the eye position of your camera? If yes, then I would have a uniform that stores that position and then do the following in my vertex shader:

gl_Position = ftransform();
reflectVec = reflect(gl_Vertex.xyz - eyePosition, gl_Normal);

Note that here I'm assuming the model itself has no "local" transformations, and that the verticies/normals going into the vertex shader are already in world space. If there are transformations local to take the model into world space, you'll need to have uniforms for those.

I think this approach will be simpler, but if you really want to play around in view space, getting back to world space would require you to use the inverse (possibly transpose) of the top-left 3x3 submatrix of the "world -> view" matrix. Again, if there are no transformations taking the model into world space, this will simply be the inverse of gl_NormalMatrix. If you need a little more clarification, just let me know!

Disclaimer: I've never implemented this before ;P

[Edited by - aryx on March 9, 2010 11:18:31 AM]

Share this post

Link to post
Share on other sites

Note that here I'm assuming the model itself has no "local" transformations

thats exactly the problem, because opengl treats the view and model matrix as one I can't simply transform the vertices and normals into world space without also transforming them into view space.

I think the fastest method would be to store a separate world matrix as a uniform in the shader but how would I be able to get the world matrix while still making calls to glRotatef and glTranslatef, would I be better to wrap these into other functions e.g.

_glRotatef(float angle, float x, float y, float z)
glRotatef(angle, x, y, z);
glGetFloatfv(GL_MODELVIEW_MATRIX, &g_WorldMatrix);

glRotatef(angle, x, y, z);

or is there a simpler way I am overlooking?

[Edited by - staticVoid2 on March 9, 2010 1:02:26 PM]

Share this post

Link to post
Share on other sites
My apologies for not replying sooner, but an old friend dropped by for a visit. One possible approach is the way you've shown. The only thing I would do differently is to fetch the matrix after it's fully constructed instead of every time I make a rotate/translate/scale call.

Another approach would be to have your own matrix manipulation code. The fixed-function stuff is all labeled as deprecated in the OpenGL 3 specs (but they'll still function for quite some time). If you're not doing anything too complicated then you'll probably only need some rotate/scale/translate functionality along with matrix multiplication. With this approach you'll be more prepared to switch to OpenGL 3 (e.g., glLoadMatrix will simply be replaced by a call to set some matrix uniforms in your shaders). This way you can separate the model transformations and view transformations yourself by keeping track of them separately.

Share this post

Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By LifeArtist
      Good Evening,
      I want to make a 2D game which involves displaying some debug information. Especially for collision, enemy sights and so on ...
      First of I was thinking about all those shapes which I need will need for debugging purposes: circles, rectangles, lines, polygons.
      I am really stucked right now because of the fundamental question:
      Where do I store my vertices positions for each line (object)? Currently I am not using a model matrix because I am using orthographic projection and set the final position within the VBO. That means that if I add a new line I would have to expand the "points" array and re-upload (recall glBufferData) it every time. The other method would be to use a model matrix and a fixed vbo for a line but it would be also messy to exactly create a line from (0,0) to (100,20) calculating the rotation and scale to make it fit.
      If I proceed with option 1 "updating the array each frame" I was thinking of having 4 draw calls every frame for the lines vao, polygons vao and so on. 
      In addition to that I am planning to use some sort of ECS based architecture. So the other question would be:
      Should I treat those debug objects as entities/components?
      For me it would make sense to treat them as entities but that's creates a new issue with the previous array approach because it would have for example a transform and render component. A special render component for debug objects (no texture etc) ... For me the transform component is also just a matrix but how would I then define a line?
      Treating them as components would'nt be a good idea in my eyes because then I would always need an entity. Well entity is just an id !? So maybe its a component?
    • By QQemka
      Hello. I am coding a small thingy in my spare time. All i want to achieve is to load a heightmap (as the lowest possible walking terrain), some static meshes (elements of the environment) and a dynamic character (meaning i can move, collide with heightmap/static meshes and hold a varying item in a hand ). Got a bunch of questions, or rather problems i can't find solution to myself. Nearly all are deal with graphics/gpu, not the coding part. My c++ is on high enough level.
      Let's go:
      Heightmap - i obviously want it to be textured, size is hardcoded to 256x256 squares. I can't have one huge texture stretched over entire terrain cause every pixel would be enormous. Thats why i decided to use 2 specified textures. First will be a tileset consisting of 16 square tiles (u v range from 0 to 0.25 for first tile and so on) and second a 256x256 buffer with 0-15 value representing index of the tile from tileset for every heigtmap square. Problem is, how do i blend the edges nicely and make some computationally cheap changes so its not obvious there are only 16 tiles? Is it possible to generate such terrain with some existing program?
      Collisions - i want to use bounding sphere and aabb. But should i store them for a model or entity instance? Meaning i have 20 same trees spawned using the same tree model, but every entity got its own transformation (position, scale etc). Storing collision component per instance grats faster access + is precalculated and transformed (takes additional memory, but who cares?), so i stick with this, right? What should i do if object is dynamically rotated? The aabb is no longer aligned and calculating per vertex min/max everytime object rotates/scales is pretty expensive, right?
      Drawing aabb - problem similar to above (storing aabb data per instance or model). This time in my opinion per model is enough since every instance also does not have own vertex buffer but uses the shared one (so 20 trees share reference to one tree model). So rendering aabb is about taking the model's aabb, transforming with instance matrix and voila. What about aabb vertex buffer (this is more of a cosmetic question, just curious, bumped onto it in time of writing this). Is it better to make it as 8 points and index buffer (12 lines), or only 2 vertices with min/max x/y/z and having the shaders dynamically generate 6 other vertices and draw the box? Or maybe there should be just ONE 1x1x1 cube box template moved/scaled per entity?
      What if one model got a diffuse texture and a normal map, and other has only diffuse? Should i pass some bool flag to shader with that info, or just assume that my game supports only diffuse maps without fancy stuff?
      There were several more but i forgot/solved them at time of writing
      Thanks in advance
    • By RenanRR
      Hi All,
      I'm reading the tutorials from learnOpengl site (nice site) and I'm having a question on the camera (https://learnopengl.com/Getting-started/Camera).
      I always saw the camera being manipulated with the lookat, but in tutorial I saw the camera being changed through the MVP arrays, which do not seem to be camera, but rather the scene that changes:
      Vertex Shader:
      #version 330 core layout (location = 0) in vec3 aPos; layout (location = 1) in vec2 aTexCoord; out vec2 TexCoord; uniform mat4 model; uniform mat4 view; uniform mat4 projection; void main() { gl_Position = projection * view * model * vec4(aPos, 1.0f); TexCoord = vec2(aTexCoord.x, aTexCoord.y); } then, the matrix manipulated:
      ..... glm::mat4 projection = glm::perspective(glm::radians(fov), (float)SCR_WIDTH / (float)SCR_HEIGHT, 0.1f, 100.0f); ourShader.setMat4("projection", projection); .... glm::mat4 view = glm::lookAt(cameraPos, cameraPos + cameraFront, cameraUp); ourShader.setMat4("view", view); .... model = glm::rotate(model, glm::radians(angle), glm::vec3(1.0f, 0.3f, 0.5f)); ourShader.setMat4("model", model);  
      So, some doubts:
      - Why use it like that?
      - Is it okay to manipulate the camera that way?
      -in this way, are not the vertex's positions that changes instead of the camera?
      - I need to pass MVP to all shaders of object in my scenes ?
      What it seems, is that the camera stands still and the scenery that changes...
      it's right?
      Thank you
    • By dpadam450
      Sampling a floating point texture where the alpha channel holds 4-bytes of packed data into the float. I don't know how to cast the raw memory to treat it as an integer so I can perform bit-shifting operations.

      int rgbValue = int(textureSample.w);//4 bytes of data packed as color
      // algorithm might not be correct and endianness might need switching.
      vec3 extractedData = vec3(  rgbValue & 0xFF000000,  (rgbValue << 8) & 0xFF000000, (rgbValue << 16) & 0xFF000000);
      extractedData /= 255.0f;
    • By Devashish Khandelwal
      While writing a simple renderer using OpenGL, I faced an issue with the glGetUniformLocation function. For some reason, the location is coming to be -1.
      Anyone has any idea .. what should I do?
  • Advertisement