Sign in to follow this  
wagner_fsoares

OpenGL Many questions (I promise it won't take longer to read)

Recommended Posts

While I was reading some sites, I found some interesting things about OpenGL: 1. Is that good to use quaternions? Because I tried hard to understand its concepts, but still no clue. 2. Is it true that the resulting matrix from glGetFloatv(GL_MODELVIEW_MATRIX, mat); has all the transformations I did until this call? 3. How can I reset just rotation, or just translations I did during the drawing "phase"? 4. Some old 3D games (and all particles afaik) have images that always are facing the screen, how can I accomplish that? (Actually I'm thinking on using the answer from question 3) 5. Is that good to use gluLookAt instead of glTransform and glRotate? (because this gluLookAt is a little trickier than I thought) 6. I'm thinking on using skeletal (bone or whatever) animation someday in my game (till now they're just static models, as you would expect from a side-scrolling-spaceship-shooting-game), and I read somewhere that I should use matrices for each vertex. (can't remember if it was quaternion or just the matrix from question 2) 7. My actual particle system is a real crap, I mean, I can't even set an "initial position" to each new particle, they just go with the spaceship. (Because the only thing I could think was to place the particles drawing method 1 line below the spaceship drawing method) there are too much transformations to get into the spaceship lines, so I can't think on any way to solve that. The End! Sorry to be asking too many questions, but even after a year of 3D OpenGL learning programming, I'm still a newbie. =/ Thanks!

Share this post


Link to post
Share on other sites
It seems that your biggest hurdle is a lack of math. I'd suggest either finding some Linear Algebra tutorials online or picking up a nice textbook and working your way through it. That will clear up everything about vectors and matrices for you and make a lot of your questions pretty intuitive to solve.

Otherwise:

3. You can manage the combined matrix stack by using glPushMatrix and glPopMatrix. a call to the latter will restore the matrix stack to what it was before glPushMatrix was called

4. the technique is called billboarding

5. I find that using gluLookAt is the most intuitive way of managing a camera. Which technique you use it up to you. However take a look at an implementation of gluLookAt and you will find that it's just some simple matrix math.

6. you use a matrix for each bone, which is the total offset & rotation from the bone's parent. Each vertex is then childed to a specific bone at an offset.

-me

Share this post


Link to post
Share on other sites
Quote:
Original post by wagner_fsoares
While I was reading some sites, I found some interesting things about OpenGL:

1. Is that good to use quaternions? Because I tried hard to understand its concepts, but still no clue.

2. Is it true that the resulting matrix from glGetFloatv(GL_MODELVIEW_MATRIX, mat); has all the transformations I did until this call?

3. How can I reset just rotation, or just translations I did during the drawing "phase"?

4. Some old 3D games (and all particles afaik) have images that always are facing the screen, how can I accomplish that? (Actually I'm thinking on using the answer from question 3)

5. Is that good to use gluLookAt instead of glTransform and glRotate? (because this gluLookAt is a little trickier than I thought)

6. I'm thinking on using skeletal (bone or whatever) animation someday in my game (till now they're just static models, as you would expect from a side-scrolling-spaceship-shooting-game), and I read somewhere that I should use matrices for each vertex. (can't remember if it was quaternion or just the matrix from question 2)

7. My actual particle system is a real crap, I mean, I can't even set an "initial position" to each new particle, they just go with the spaceship. (Because the only thing I could think was to place the particles drawing method 1 line below the spaceship drawing method) there are too much transformations to get into the spaceship lines, so I can't think on any way to solve that.

The End!

Sorry to be asking too many questions, but even after a year of 3D OpenGL learning programming, I'm still a newbie.
=/
Thanks!


5. gluLookAt is good. The eye is the position where you want you to be. The look at is the position where you want to be looking (this could be 1 unit in front of the eye). The up vector is whatever you want.
You can avoid gluLookAt if you want. It is up to you.

7. For particle system, the best is to transform each one using the CPU and just send world space coordinates. You would do it like this
glLoadMatrixf(CameraMatrix);
RenderParticlesInWorldSpace();

so only the camera matrix is needed to position them.
Search for some tutorials on particle stuff. Some of them might use shaders.

Share this post


Link to post
Share on other sites
1) quite essential if objects need complete freedom in rotation
2) yes
3) if you do only rotation and translation, the 4x4 matrix basically consists of a 3x3 rotation matrix R, a 1x3 translation vector T, and padding:
R R R T
R R R T
R R R T
0 0 0 1
So, if you want to reset translation, set T = {0,0,0}. If you want to reset rotation, set R = {1,0,0, 0,1,0, 0,0,1}. Beware that gl_NormalMatrix will be wrong if you reset the rotation in this way, and thus fixed-func lighting will appear wrong

4) billboarding, as answered. 2 triangles per billboard, that are created and calculated on the cpu on every frame.
5) gluLookAt is recommended

Share this post


Link to post
Share on other sites
Sorry, I'm like 3h delayed...

OK, about linear algebra, I'm graduated from computer science, so I know the basics.
The problem is how this quaternion holds all the data and how is like working with it, the same as for GL_MODELVIEW_MATRIX.

So using or not gluLookAt hasn't any effect at all huh!
I'd some problems understanding and using it.
I still didn't do with gluLookAt what these 2 lines did:

glTranslatef(0.0f, 0.0f, -30.0f);
glRotatef(27 - (m_scroll * 2), -1.0f, 0.0f, 0.0f);
glTranslatef(0.0f, m_scroll / 2, 0.0f);

Just place all the objects far from the "view" and rotate and get near as the spaceship goes.

And about particles, it won't work, cuz I want these particles to be behind the spaceship as it moves on the screen and at the same time, keep all particles facing the screen.

Palidine, about reseting rotation and translation, yeah you're right, it's time for me to be more organized. =)
About answer 4, I didn't know it had a name. =P
Gonna start reading about this billboarding.


What about quaternions, do you guys use it?
Can I still be happy without using it?

Thanks for the answers!

[EDIT]
Sorry idinev, I didn't see your post, I think we've posted at the same time. =P
Whatever.
Gonna start learning (again) this quaternion thing, do you have a good source so I can learn?
And about billboard, what do you think about this one: http://nehe.gamedev.net/data/articles/article.asp?article=19 ? (I was pretty sure everything I ever code but "gl" functions, was calculated on the CPU)

[Edited by - wagner_fsoares on December 28, 2009 9:03:59 PM]

Share this post


Link to post
Share on other sites
Ok, I've some news:

I'm now working with gluLookAt, and I got the logic behind quaternions.
But I'm still stuck with billboards, I've following this article: http://nehe.gamedev.net/data/articles/article.asp?article=19 , but I think I'm not getting the right values for the object's world coordinate.
I'm using this logic: http://www.lighthouse3d.com/opengl/billboarding/index.php?billWhere to get the object's world position, but I think I'm missing something.

here's my code for billboarding:


inline QVector3D objWorldPos(QVector3D &camPos) {
GLfloat modelview[16];
glGetFloatv(GL_MODELVIEW_MATRIX, modelview);

QVector3D worldPos;

worldPos.setX(camPos.x() + (modelview[12] * modelview[0]) + (modelview[13] * modelview[1]) + (modelview[14] * modelview[2]));
worldPos.setY(camPos.y() + (modelview[12] * modelview[4]) + (modelview[13] * modelview[5]) + (modelview[14] * modelview[6]));
worldPos.setZ(camPos.z() + (modelview[12] * modelview[8]) + (modelview[13] * modelview[9]) + (modelview[14] * modelview[10]));

return worldPos;
}

inline void billboardSphericalBegin(QVector3D camPos, QVector3D objPos) {
QVector3D objLook, objUp, objRight;

objLook = camPos - objPos;
objLook.normalize();

QVector3D camUp(0, 1, 0);

objRight = QVector3D::crossProduct(camUp, objLook);

objUp = QVector3D::crossProduct(objLook, objRight);

GLfloat mat[] = { objRight.x(), objRight.y(), objRight.z(), 0,
objUp.x(), objUp.y(), objUp.z(), 0,
objLook.x(), objLook.y(), objLook.z(), 0,
objPos.x(), objPos.y(), objPos.z(), 1
};

glPushMatrix();
glMultMatrixf(mat);
}

//the draw

glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);
glLoadIdentity();
m_modelView.setToIdentity();

//the rest of the cam values are 0
m_camEye.setZ(10);
m_camLook.setX(m_camMove.x());
m_camLook.setY(m_camMove.y());
m_camUp.setY(1);

m_modelView.lookAt(m_camEye, m_camLook, m_camUp);
qMultMatrix(m_modelView);

m_modelView.setToIdentity();
m_modelView.translate(-1, -1, -10);
qMultMatrix(m_modelView);

QVector3D objWPos = objWorldPos(m_camEye);
billboardSphericalBegin(m_camEye, objWPos);

glBindTexture(GL_TEXTURE_2D, m_tex_grass);
glBegin(GL_TRIANGLE_FAN);
glVertex3f(10, -12, 0);
glVertex3f(10, 12, 0);
glVertex3f(-10, 12, 0);
glVertex3f(-10, -12, 0);
glEnd();

billboardEnd();

Share this post


Link to post
Share on other sites
Quote:
1) quite essential if objects need complete freedom in rotation
That's actually not true. Quaternions have the same fundamental behavior with respect to rotations as do matrices; in other words, if you can do it with a quaternion, you can do it with a matrix.

@The OP: Quaternions do some things more elegantly and/or efficiently than matrices and therefore it can sometimes be advantageous to use them, but if you're fairly new to 3-d math I'd suggest just sticking with matrices for the time being.

Share this post


Link to post
Share on other sites
I've got billboarding to work like this:


GLfloat matrix[16];
glGetFloatv(GL_MODELVIEW_MATRIX, matrix);
matrix[0] = 1.0f; matrix[1] = 0.0f; matrix[2] = 0.0f;
matrix[4] = 0.0f; matrix[5] = 1.0f; matrix[6] = 0.0f;
glPushMatrix();
glLoadMatrixf(matrix);


I don't know if it's the right thing to do but... oh hell it's working!

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
      628314
    • Total Posts
      2982023
  • Similar Content

    • 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!
    • By test opty
      Hi,
      I'm trying to learn OpenGL through a website and have proceeded until this page of it. The output is a simple triangle. The problem is the complexity.
      I have read that page several times and tried to analyse the code but I haven't understood the code properly and completely yet. This is the code:
       
      #include <glad/glad.h> #include <GLFW/glfw3.h> #include <C:\Users\Abbasi\Desktop\std_lib_facilities_4.h> using namespace std; //****************************************************************************** void framebuffer_size_callback(GLFWwindow* window, int width, int height); void processInput(GLFWwindow *window); // settings const unsigned int SCR_WIDTH = 800; const unsigned int SCR_HEIGHT = 600; const char *vertexShaderSource = "#version 330 core\n" "layout (location = 0) in vec3 aPos;\n" "void main()\n" "{\n" " gl_Position = vec4(aPos.x, aPos.y, aPos.z, 1.0);\n" "}\0"; const char *fragmentShaderSource = "#version 330 core\n" "out vec4 FragColor;\n" "void main()\n" "{\n" " FragColor = vec4(1.0f, 0.5f, 0.2f, 1.0f);\n" "}\n\0"; //******************************* int main() { // glfw: initialize and configure // ------------------------------ glfwInit(); glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 3); glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 3); glfwWindowHint(GLFW_OPENGL_PROFILE, GLFW_OPENGL_CORE_PROFILE); // glfw window creation GLFWwindow* window = glfwCreateWindow(SCR_WIDTH, SCR_HEIGHT, "My First Triangle", nullptr, nullptr); if (window == nullptr) { cout << "Failed to create GLFW window" << endl; glfwTerminate(); return -1; } glfwMakeContextCurrent(window); glfwSetFramebufferSizeCallback(window, framebuffer_size_callback); // glad: load all OpenGL function pointers if (!gladLoadGLLoader((GLADloadproc)glfwGetProcAddress)) { cout << "Failed to initialize GLAD" << endl; return -1; } // build and compile our shader program // vertex shader int vertexShader = glCreateShader(GL_VERTEX_SHADER); glShaderSource(vertexShader, 1, &vertexShaderSource, nullptr); glCompileShader(vertexShader); // check for shader compile errors int success; char infoLog[512]; glGetShaderiv(vertexShader, GL_COMPILE_STATUS, &success); if (!success) { glGetShaderInfoLog(vertexShader, 512, nullptr, infoLog); cout << "ERROR::SHADER::VERTEX::COMPILATION_FAILED\n" << infoLog << endl; } // fragment shader int fragmentShader = glCreateShader(GL_FRAGMENT_SHADER); glShaderSource(fragmentShader, 1, &fragmentShaderSource, nullptr); glCompileShader(fragmentShader); // check for shader compile errors glGetShaderiv(fragmentShader, GL_COMPILE_STATUS, &success); if (!success) { glGetShaderInfoLog(fragmentShader, 512, nullptr, infoLog); cout << "ERROR::SHADER::FRAGMENT::COMPILATION_FAILED\n" << infoLog << endl; } // link shaders int shaderProgram = glCreateProgram(); glAttachShader(shaderProgram, vertexShader); glAttachShader(shaderProgram, fragmentShader); glLinkProgram(shaderProgram); // check for linking errors glGetProgramiv(shaderProgram, GL_LINK_STATUS, &success); if (!success) { glGetProgramInfoLog(shaderProgram, 512, nullptr, infoLog); cout << "ERROR::SHADER::PROGRAM::LINKING_FAILED\n" << infoLog << endl; } glDeleteShader(vertexShader); glDeleteShader(fragmentShader); // set up vertex data (and buffer(s)) and configure vertex attributes float vertices[] = { -0.5f, -0.5f, 0.0f, // left 0.5f, -0.5f, 0.0f, // right 0.0f, 0.5f, 0.0f // top }; unsigned int VBO, VAO; glGenVertexArrays(1, &VAO); glGenBuffers(1, &VBO); // bind the Vertex Array Object first, then bind and set vertex buffer(s), //and then configure vertex attributes(s). glBindVertexArray(VAO); glBindBuffer(GL_ARRAY_BUFFER, VBO); glBufferData(GL_ARRAY_BUFFER, sizeof(vertices), vertices, GL_STATIC_DRAW); glVertexAttribPointer(0, 3, GL_FLOAT, GL_FALSE, 3 * sizeof(float), (void*)0); glEnableVertexAttribArray(0); // note that this is allowed, the call to glVertexAttribPointer registered VBO // as the vertex attribute's bound vertex buffer object so afterwards we can safely unbind glBindBuffer(GL_ARRAY_BUFFER, 0); // You can unbind the VAO afterwards so other VAO calls won't accidentally // modify this VAO, but this rarely happens. Modifying other // VAOs requires a call to glBindVertexArray anyways so we generally don't unbind // VAOs (nor VBOs) when it's not directly necessary. glBindVertexArray(0); // uncomment this call to draw in wireframe polygons. //glPolygonMode(GL_FRONT_AND_BACK, GL_LINE); // render loop while (!glfwWindowShouldClose(window)) { // input // ----- processInput(window); // render // ------ glClearColor(0.2f, 0.3f, 0.3f, 1.0f); glClear(GL_COLOR_BUFFER_BIT); // draw our first triangle glUseProgram(shaderProgram); glBindVertexArray(VAO); // seeing as we only have a single VAO there's no need to // bind it every time, but we'll do so to keep things a bit more organized glDrawArrays(GL_TRIANGLES, 0, 3); // glBindVertexArray(0); // no need to unbind it every time // glfw: swap buffers and poll IO events (keys pressed/released, mouse moved etc.) glfwSwapBuffers(window); glfwPollEvents(); } // optional: de-allocate all resources once they've outlived their purpose: glDeleteVertexArrays(1, &VAO); glDeleteBuffers(1, &VBO); // glfw: terminate, clearing all previously allocated GLFW resources. glfwTerminate(); return 0; } //************************************************** // process all input: query GLFW whether relevant keys are pressed/released // this frame and react accordingly void processInput(GLFWwindow *window) { if (glfwGetKey(window, GLFW_KEY_ESCAPE) == GLFW_PRESS) glfwSetWindowShouldClose(window, true); } //******************************************************************** // glfw: whenever the window size changed (by OS or user resize) this callback function executes void framebuffer_size_callback(GLFWwindow* window, int width, int height) { // make sure the viewport matches the new window dimensions; note that width and // height will be significantly larger than specified on retina displays. glViewport(0, 0, width, height); } As you see, about 200 lines of complicated code only for a simple triangle. 
      I don't know what parts are necessary for that output. And also, what the correct order of instructions for such an output or programs is, generally. That start point is too complex for a beginner of OpenGL like me and I don't know how to make the issue solved. What are your ideas please? What is the way to figure both the code and the whole program out correctly please?
      I wish I'd read a reference that would teach me OpenGL through a step-by-step method. 
  • Popular Now