Sign in to follow this  
akuda

OpenGL Managing Meshes

Recommended Posts

Hi, As part of the Bachelor's degree I'm writing (with 3 other students) a computer game. We write in OpenGL and C++; I have a question about how the models are managed in RAM memory - I fully understand the idea of re-using geometry with VBO, I also know how skeletal animation works (and we're about to implement it). We were asked to keep the OpenGL-specific code in a separate module, so after frustum culling we need to create a command-list to the rendering device (we think that a tree-based data structure would be the best choice for this). My question is: how to organize (in classes) the skeletal-animated objects in memory, so a set of orders could be easily generated for the device. I found out that most engines define "Mesh" structure to contain geometry data, but the meaning of "Mesh class" vary between engines - some contains only raw geometry information, and some other contains also material and texture id's. Some do contain bones informations, some does not. Considering skinning as a part of process of skeletal animation, I have some problems defining how to divide a complete textured and animated model into any kind of "meshes" (as most of faces are bound with more than just one bone), "bones" and "animations" other than just "everything-in-one" which probably isn't the best idea. What I want to do with the representation of data? Well, be able to animate it with shaders on GPU, be able to attach some other objects to specific bones in skeleton, and efficiently code it into a set of instructions "independent" on rendering system. For specifications we can agree that the model format is similar to Milkshape ms3d one. What's your suggestions? Regards, akuda

Share this post


Link to post
Share on other sites
I´ve been writing an engine using OpenGL and C++ for two years now, in my spare time. I´ve gathered a bit of experience and i can tell you what i do in my engine, but it probably isn´t the best way to do things.

I have an abstract class "Renderer" which is subclassed by "OpenGLRenderer" and others. The abstract class has virtual methods for common rendering operations (draw a chunk of vertices, change alpha blend mode, current shader, etc.) I implement these methods for each renderer i want to have, and when starting the program I instantiate a "Renderer* rend" variable to be one of the renderers. So that the rest of the engine is independent of the rendering API.

I also have a Mesh class that stores a bunch of vertices, normals, and UVs. I have a method that can blend Meshes together. Then i have a Node class which stores spatial transformations and can have other Nodes as childs. This way you can have a hierarchy of nodes which ad their transform to their parent´s. Nodes can also have Animations applied which are just a sequence of transforms over time.

To attach a Mesh to a Node, if there is no skinning (just a static entity like a table, for example) i just draw the Mesh after setting the Node´s transform as the current one. If i want a hierarchy of nodes to act as a skeleton to a mesh, I use a vertex shader to transform the Mesh vertices accordingly, for each vertex i select the affecting Node´s transforms and blend them togehter using the vertex bone weights.

To me this has proven to be quite flexible since you can have Animations for each node and blend animations together, change the animation for just some bones of the character, and attach weapons and stuff to the character´s bones by just attaching a new Node to their bone (Node) hierarchy.

[Edited by - ArKano22 on November 5, 2009 12:42:03 PM]

Share this post


Link to post
Share on other sites
this is very similar to what I have planned (I guess we read the same books :) ), but I wonder - does that mean, that you're having an information "below subtree is a skeleton" attached to some node, and this information is applying a shader? To which node a geometry data (for skinning) are connected - to the root of animation?

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  

  • Partner Spotlight

  • Forum Statistics

    • Total Topics
      627644
    • Total Posts
      2978373
  • Similar Content

    • By xhcao
      Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness. 
    • By cebugdev
      hi guys, 
      are there any books, link online or any other resources that discusses on how to build special effects such as magic, lightning, etc. in OpenGL? i mean, yeah most of them are using particles but im looking for resources specifically on how to manipulate the particles to look like an effect that can be use for games,. i did fire particle before, and I want to learn how to do the other 'magic' as well.
      Like are there one book or link(cant find in google) that atleast featured how to make different particle effects in OpenGL (or DirectX)? If there is no one stop shop for it, maybe ill just look for some tips on how to make a particle engine that is flexible enough to enable me to design different effects/magic 
      let me know if you guys have recommendations.
      Thank you in advance!
    • By dud3
      How do we rotate the camera around x axis 360 degrees, without having the strange effect as in my video below? 
      Mine behaves exactly the same way spherical coordinates would, I'm using euler angles.
      Tried googling, but couldn't find a proper answer, guessing I don't know what exactly to google for, googled 'rotate 360 around x axis', got no proper answers.
       
      References:
      Code: https://pastebin.com/Hcshj3FQ
      The video shows the difference between blender and my rotation:
       
    • By Defend
      I've had a Google around for this but haven't yet found some solid advice. There is a lot of "it depends", but I'm not sure on what.
      My question is what's a good rule of thumb to follow when it comes to creating/using VBOs & VAOs? As in, when should I use multiple or when should I not? My understanding so far is that if I need a new VBO, then I need a new VAO. So when it comes to rendering multiple objects I can either:
      * make lots of VAO/VBO pairs and flip through them to render different objects, or
      * make one big VBO and jump around its memory to render different objects. 
      I also understand that if I need to render objects with different vertex attributes, then a new VAO is necessary in this case.
      If that "it depends" really is quite variable, what's best for a beginner with OpenGL, assuming that better approaches can be learnt later with better understanding?
       
    • By test opty
      Hello all,
       
      On my Windows 7 x64 machine I wrote the code below on VS 2017 and ran it.
      #include <glad/glad.h>  #include <GLFW/glfw3.h> #include <std_lib_facilities_4.h> using namespace std; void framebuffer_size_callback(GLFWwindow* window , int width, int height) {     glViewport(0, 0, width, height); } //****************************** void processInput(GLFWwindow* window) {     if (glfwGetKey(window, GLFW_KEY_ESCAPE) == GLFW_PRESS)         glfwSetWindowShouldClose(window, true); } //********************************* int main() {     glfwInit();     glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 3);     glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 3);     glfwWindowHint(GLFW_OPENGL_PROFILE, GLFW_OPENGL_CORE_PROFILE);     //glfwWindowHint(GLFW_OPENGL_FORWARD_COMPAT, GL_TRUE);     GLFWwindow* window = glfwCreateWindow(800, 600, "LearnOpenGL", nullptr, nullptr);     if (window == nullptr)     {         cout << "Failed to create GLFW window" << endl;         glfwTerminate();         return -1;     }     glfwMakeContextCurrent(window);     if (!gladLoadGLLoader((GLADloadproc)glfwGetProcAddress))     {         cout << "Failed to initialize GLAD" << endl;         return -1;     }     glViewport(0, 0, 600, 480);     glfwSetFramebufferSizeCallback(window, framebuffer_size_callback);     glClearColor(0.2f, 0.3f, 0.3f, 1.0f);     glClear(GL_COLOR_BUFFER_BIT);     while (!glfwWindowShouldClose(window))     {         processInput(window);         glfwSwapBuffers(window);         glfwPollEvents();     }     glfwTerminate();     return 0; }  
      The result should be a fixed dark green-blueish color as the end of here. But the color of my window turns from black to green-blueish repeatedly in high speed! I thought it might be a problem with my Graphics card driver but I've updated it and it's: NVIDIA GeForce GTX 750 Ti.
      What is the problem and how to solve it please?
  • Popular Now