Archived

This topic is now archived and is closed to further replies.

MrSandman666

OpenGL using models in OpenGL (CAUTION! NEWBIE INSIDE!)

Recommended Posts

Ok, this is probably very basic and stupid but I''m a pretty stupid newbie (especially in the field of 3d graphics and OpenGL) so please bear with me. In my program I need to handle more or less complex models. Well, they are far too complex to hardcode every single polygon by hand. So how do i get models into my program? I don''t have a 3D modeler right now and I''m not a great 3D artist. So what would you recommend for me? How could I create my models, how should I store them in a file? How would I load them again (this one is probably pretty straight forward. I just have to do the storing process the other way ''round) and how should I display ''em then? How do you handle models? Or how would you handle models if you had to? So many questions and all I have is an empty brain. Please help a desperate newbie out. There was a time where you were newbies too and needed help like I do right now. ANY input is more than welcome. Thanx for reading till here. And pleeeeeaaze help me if you can. "Mr Sandman bring me a dream"

Share this post


Link to post
Share on other sites
quote:
Original post by MrSandman666

In my program I need to handle more or less complex models. Well, they are far too complex to hardcode every single polygon by hand.

So how do i get models into my program? I don''t have a 3D modeler right now and I''m not a great 3D artist. So what would you recommend for me?



You can use 3D studio (max) to create your models or another modeling package.

quote:
How could I create my models, how should I store them in a file? How would I load them again (this one is probably pretty straight forward. I just have to do the storing process the other way ''round) and how should I display ''em then?

How do you handle models? Or how would you handle models if you had to?


Best to save in 3DS format or just the standard file from that modeller. There are a lot of conversion tools out there to convert the modeller file, to C(++) or a simple AscII format or binary or whatever. If this conversion still isn''t good enough, I would recommend converting to simple AscII and writing your own convertor.

To display them, might not be so easy if you haven''t written any OGL or D3D program yet. If you''re new at this - I would suggest a visit to nehe.gamedev.net for source code and tutorials and www.opengl.org for the SDK.

Share this post


Link to post
Share on other sites
3D STUDIO MAX??? *cough*
I''m not rich for crying out loud! I''m only a hobby programmer.
Still, that''s not the main reason for me not to use some expensive modelling kit. I know there are even freeware ones out there.
I would just like to have my own file format to keep things simple. It is usually pretty hard (I think) to convert a 3d file (*.3ds for example) to something that works with OpenGL.
I mean, if someone knows a very simple and plain 3d file format out there or I find one, I''ll be very happy to have a look and try my luck with it, but 3ds is definately too complicated for me (I already had a look at it and didn''t understand a word).
I thought of having a list of vertices, each with position data and a material attached to it.
From that I can calculate the single polygons (which will be pretty hard though) and the normals from these polys.
The polygons can be rendered pretty easily then.

The problem is, where do I get the vertices from, how do I store them in a file so that they can be read easily later and how do I create polygons from these vertices.
Another problem for me would be the internal storage of the vertices and polygons. You''ll never know the nmber of verices or polys in a model in beforehand so the intuitive approach for me would be a linked list, but wouldn''t that be incredibly slow to read later? A dynamicaly declared array could be a solution.

BTW: I''m new to OpenGL, but that doesn''t mean that I have no experience at all with it. I''m just learning it at the moment, so i know the basic theories of rendering triangels, moving and lighting them and this kind of stuff. I havent mastered texture mapping yet, though.
Ohhhh, sh...! Texture mapping! I didn''t think about that one! If my model is defined by vertices initialy, how the hell would I specify the textures for them??? Ok, probably I have to store polys right away. So, where do I get poly''s from?
Oh my... Questions over questions. WHy does 3d have to be so hard

Anyways:
Thank you very much for your reply! I apologize if my answer sounded somehow rude or so. That just happens to me sometimes.
I really appreciated your help

"Mr Sandman bring me a dream"

Share this post


Link to post
Share on other sites
a nice one is md2 files (plenty of character models around for code to load a md2 check the milkshake site)
"3d exportation"? converts various 3d file formats
milkshake + blender r modelling apps

http://members.xoom.com/myBollux

Share this post


Link to post
Share on other sites
Pauly, on your site you said that vertex arrays are somewhat fasionable and that they have certain advantages compared to display lists.
I''ve never heard of vertex arrays though. Wouldn''t display lists be faster? What are the advantages of vertex arrays?

"Mr Sandman bring me a dream"

Share this post


Link to post
Share on other sites
I would say, download Milkshape 3D. On the millshape site there are some links to tutorials on how to model and how to use the program. Its shareware so it works normal for 30 days, after that it will not save or export. The cost to register is only $20. If you can''t afford 3d studio max, im sure you can afford this one.

-Snyper

Share this post


Link to post
Share on other sites
In fact, I already DID download Milkshape. And the SDK and the avi tutorials. I haven''t registered it yet, but I guess I will do so soon. In my opinion it''s a really cool program.
But that doesn''t help me with my vertex array question. can anyone help me with that?

"Mr Sandman bring me a dream"

Share this post


Link to post
Share on other sites
Data in display lists is static. You can''t change it after you''ve compiled the display list without recompiling the display list again.

Vertex arrays let you render primitives with indices (reducing geometry bandwidth) and if you use copmiled vertex arrays and the proper datatypes, they can be as fast as display lists. The bonus is they aren''t static so you can change the data in them if needs be.

Thats just a primer, there''s loads of stuff been written about the pros and cons on graphics message boards all over the place.

Paul.

Share this post


Link to post
Share on other sites
Thanx man!
Now I finally understand it.

I started diggin into the material you have on your homepage and to say the least: I''m confused! This is all so complicated that I have the feeling that I have to take another approach or find a reeeeeaaally simple tutorial. I mean, your tutorial is prbably great for someone who has some experience doing stuff like that, but for me this is the first time I have to actually write my own engine for my game. Until know I always used some 3rd party engine to get my graphics onto the screen. I have actually no idea what to do with all the data given by Milkshape and - I''m sorry - your tutorial doesn''t help me much. After all it''s basically only some source code with a few comments. I need someone to take my hand, walk me through this step by step and explain every single bit in detail.
It''s a pitty that NeHe doesn''t have a tutorial on Model Loading. The rest of his tutorials are great!
I really am pretty desperate. I need to get this done and I don''t kno how to approach it.
How did you learn it?

"Mr Sandman bring me a dream"

Share this post


Link to post
Share on other sites
How did I learn about model loaders? I wrote one myself. That simple meshloader uses I format that I dreamt up.

3d programs usually export vertices, face and material data. The first part of the parser reads the vertices into an array.
Eg:
0.0 0.0 0.0 // element [ 0 ]
1.0 0.0 0.0 // element [ 1 ]
0.0 1.0 0.0 // element [ 2 ]
0.0 0.0 0.0 // element [ 3 ]


The face data in the file are indices to the vertices in the array. So one particular triangle might look like:
0 1 2
That would reference the coordinates at positions 0, 1 and 2 in the vertex array - thus making a triangle.

I thought this was fairly easy to pick up from what I''d written - I guess I''ll go back to it and rewrite it a bit when I have the time.

Thanks for the feedback,
Paul.

Share this post


Link to post
Share on other sites
Well, I guess I just have to dig my way through the Milkshape Ascii file specs and come up with a new loader from scratch.
But I still got a few questions:

1. Why didn''t you take the normals from Milkshape but generate your own ones?

2. Did any one make it to read the binary version of the Milkshape file format? If so: how? I don''t undertand their concept. Are there tutorials on this? Example loaders?

Any further help woudl be veeery welcome!


"Mr Sandman bring me a dream"

Share this post


Link to post
Share on other sites
1.
Because I have no idea what Mete (the author) was taking when he designed Milkshapes smoothing group mechanism. And I had the code lying around from my Lightwave object parser.

2.
There aren''t any ''formal'' specs. for the binary version of the files. You get a text file with a bunch of C structs in it - if you try to use those in your program it doesn''t seem to work

Its easy to load binary files if you know their structure. Lets take the ASCII simple meshloader file and make it into a binary format. To make it easier to read we could rearrange the file structure so that the object stats are all together. So at the start of your binary file you''d have two unsigned integers that tell us the number of vertices in the object and the number of (triangular) faces it has.

We''ll collect this together in a type called tObjectInfo. Below are the types that we need to define and some variables of the types we need to store our object data.


/* Type definitions */
typedef struct {
unsigned int num_vertices;
unsigned int num_faces;
} tObjectInfo;

typedef float tVertex[3];
typedef unsigned int tIndex[3];

/* Variable declarations */
tObjectInfo object_stats;
tVertex *object_verts;
tIndex *object_indices;


So you''d open the file with fopen (or whatever you use) set in binary mode, then:

fread ( object_stats, ( sizeof ( tObjectInfo )), 1, file );

That reads data that is the size of a tObjectInfo into a record variable "object_stats". The "1" is the number of times to perform the same read. The "file" is the open file pointer.

You''d use these stats to create arrays of vertices and indices:

object_verts = ( tVertex* ) malloc ( sizeof ( tVertex * object_stats.num_vertices ));

object_indices = ( tIndex* ) malloc ( sizeof ( tIndex * object_stats.num_indices ));


In the code above you''re casting the result of a malloc call to the arrays of either tVertex or tIndex. The "sizeof" part makes sure we allocate the correct number of bytes. It''s good pratice to check whether these return NULL or not. If using C++ you''d call the new operator instead of using malloc.

Next, your file would have a bunch of floats that represented the vertices, so you''d read these in like:

fread ( &object_verts, ( sizeof ( tVertex )), object_stats.num_vertices, file );

And then the indices:

fread ( &object_indices, ( sizeof ( tIndex )), object_stats.num_indices, file );

So as you can see at this level, reading binary files is easy. You just have to know the structure. In reality most 3d binary file formats are made up of ''chunks''. Each chunk has an Id header and its size in there to. But as long as you know the format of each chunk then reading them isn''t a problem.

The bonus of having chunks with their size in the header is that if you want to ignore the data in the chunk you can just fseek past it with the current chunk''s size.

Phew! Wrote a lot there - still it helps with the touch typing -- You can tell I''m bored can''t you

Share this post


Link to post
Share on other sites

  • Announcements

  • Forum Statistics

    • Total Topics
      628327
    • Total Posts
      2982091
  • 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