Archived

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

kaiel090x

OpenGL What exactly is OpenGL for anyway?

Recommended Posts

Allright, OpenGL is obviosly a powerful API, but it mainly makes graphics. I want to program games, not make graphics(?!?!?!?!?!??!) Why should I need to know OpenGL? I really dont quite understand that. If the programmer makes the graphics in opengl, what does a graphic artist do? Please, someone explain this to me. Maybe its because I havent learned much of OpenGL yet, though I currently am, while reading my book, I was thinking to myself, "Why should I have to do all this, I just want to make it say hey attack now, rip his head off, feed him to the rabid monkees, and through his body to the zombies on the fourth floor." Thats just a ridiculus example(lol) but I mean, I dont mind dealing with the graphics, I just dont understand then what a graphic artist is for. "He who fights monsters should look to it that he himself does not become a monster... when you gaze long into the abyss, the abyss also gazes into you."~Friedrich Nietzsche Edited by - kaiel090x on August 19, 2001 3:03:33 AM

Share this post


Link to post
Share on other sites
OpenGL is an API for showing graphics already made BY artists, it''s not like Photoshop or anything like that, it''s used to show triangles, textures, make effects and things like that, an artists doesn''t need to know how to program to make the graphics, but is you are going to use OpenGL you NEED to know how to program.

Share this post


Link to post
Share on other sites
Basically, a graphic artist has to make the graphics. The programmer then has to get the computer to display those graphics on screen. This is what OpenGL and other APIs (like DirectX) are for. A graphic artist can make a 2D texture or something within a graphics program. But to use that in your game, you have to have some way of displaying that texture.

I think you''ve confused two things. Programming games doesn''t have to do with making graphics, but rather, displaying graphics. That''s why you would benefit from knowing OpenGL. Without using OpenGL, or another API, you''d have to write your own software routines for displaying graphics.

Share this post


Link to post
Share on other sites
Hi, kaiel090x!
Judging by what you said it seems to do a mod for an existing game (-engine) like q3 or ut would be more what you should be looking into. When programming a mod you don''t have to mess with opengl or directx instead you can load your models and write in your code
model->ripHeadOff(targetModell); //(veeeeeerrrryyyy simplified ;-)
Hope you get what I meen. This way you can concentrate on creating your models an maps and only have to code the game logics not the graphics routines.

baumep

Share this post


Link to post
Share on other sites
Actualy I want to make 2d games in OpenGL and C++, I know C++ and I am learning OpenGL(well, I know a decent amount of C++, the extremely advanced stuff I am still learning). But, im better off reading a book and actually learning openGL then just taking tutorials on 2d, cuz they assume you know some of OpenGL anyway, plus they are hard to find. I didnt understand why I should need to make the graphics for the game a program, because if I did what is the point of having a grafic designer? But I understand now, and I just dont agree with it, but if its what I have to do to be a programmer, I will do it. Its not muhc a of a deal. THank you everyone for answering my question.
quote:
Original post by baumep
Hi, kaiel090x!
Judging by what you said it seems to do a mod for an existing game (-engine) like q3 or ut would be more what you should be looking into. When programming a mod you don't have to mess with opengl or directx instead you can load your models and write in your code
model->ripHeadOff(targetModell); //(veeeeeerrrryyyy simplified ;-)
Hope you get what I meen. This way you can concentrate on creating your models an maps and only have to code the game logics not the graphics routines.

baumep




"He who fights monsters should look to it that he himself does not become a monster... when you gaze long into the abyss, the abyss also gazes into you."~Friedrich Nietzsche

Edited by - kaiel090x on August 19, 2001 1:21:27 PM

Share this post


Link to post
Share on other sites
quote:
Original post by kaiel090x
I didnt understand why I should need to make the graphics for the game a program, because if I did what is the point of having a grafic designer? But I understand now, and I just dont agree with it, but if its what I have to do to be a programmer, I will do it.

Er, what''s to disagree with? Artists do the art. They are in charge of something looks. The programmer is in charge of how it acts. Objects move around the map and obscure other objects. This is tracked in code. Therefore the code has to decide how and where to draw things, and what to draw. It''s just the same with sprites: the artist draws the sprite, but the programmer still has to tell the program when and where and how to draw it.

Share this post


Link to post
Share on other sites
quote:

I didnt understand why I should need to make the graphics for the game a program, because if I did what is the point of having a grafic designer? But I understand now, and I just dont agree with it, but if its what I have to do to be a programmer, I will do it.



Um, kaiel090x, I don''t think you''re quite understanding this.

OpenGL is an API, interfaced to by C functions, which is used by programmers to communicate with 3D hardware, basically to draw triangles. The graphic designer will still make the graphics in a 3D modeller such as 3DSMax. As the coder, you have to write the code needed to load and draw the objects the artist makes, which is where OpenGL comes in (with the drawing, anyway, not the loading).

If using an API is a problem, you''d better start learning ASM.


www.elf-stone.com

Share this post


Link to post
Share on other sites
I am sorry if you didnt quite understandme correctly. I know OpenGL is an API. I know what it can do, and I know whats its for. I said in m last response that learning it really isnt much a problem for me. What I DIDNT(notice it is dont anymore) was why the programmer has to screw with graphcs, I understand it now, PROGRAMMERS LOAD THE TEXTURES INTO THE TRIANGLES/ECT WE MAKE. Then we can control the graphcs.
quote:
Original post by benjamin bunny
[quote]
I didnt understand why I should need to make the graphics for the game a program, because if I did what is the point of having a grafic designer? But I understand now, and I just dont agree with it, but if its what I have to do to be a programmer, I will do it.



Um, kaiel090x, I don''t think you''re quite understanding this.

OpenGL is an API, interfaced to by C functions, which is used by programmers to communicate with 3D hardware, basically to draw triangles. The graphic designer will still make the graphics in a 3D modeller such as 3DSMax. As the coder, you have to write the code needed to load and draw the objects the artist makes, which is where OpenGL comes in (with the drawing, anyway, not the loading).

If using an API is a problem, you''d better start learning ASM.


www.elf-stone.com



"He who fights monsters should look to it that he himself does not become a monster... when you gaze long into the abyss, the abyss also gazes into you."~Friedrich Nietzsche

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
quote:
Original post by Galileo430
2D? Learn Direct Draw.

Lots of nice books out there on it.

I think that kaiel090x has the right idea, OpenGL is postable to just about every system instead of being stuck on Windows.

Share this post


Link to post
Share on other sites
al right, all right... Ok. I KNOW (cleaer to say printf or cout in front for some of ya? lol) that i CAN(see C_A_N- Can- being able to) do 2d, and I know its WORKS just as welll as Direct Draw, but I dont know HOW to put 2D into the game. But, a very great person, the best guy in the world, lol, ShiningKnight told me hes makin a tutorial SO i dcided just to wait till than. Thank for trying to help me

"He who fights monsters should look to it that he himself does not become a monster... when you gaze long into the abyss, the abyss also gazes into you."~Friedrich Nietzsche

Share this post


Link to post
Share on other sites
Hmm Im a bit bored so I''ll put in some info here.

OK, now assume you have some sprites that you want to animate in 2D [your characters/fighters/backgrounds/weapons/etc]. Your graphics are already drawn.

You have these drawn out already in something like photoshop and they are bitmaps [or JPEGS or whatever.. they''re images in some form]

Now you have to have something that puts it all together. Your program in C++ calls OpenGL in order to draw the pixels to the screen.

In the case of 3D, OpenGL is actually calculating the position, lighting, texturing/etc for each triangle. It is converting from the XYZ coordinates you specify into actual pixels that are to be displayed on the screen.

In the case of 2D, OpenGL allows you to draw and animate your existing 2D sprites. It will load in the images you have made and move them around the screen based on the instructions you give it. It can layer images [like putting a character on top of a background] or blend images together [using transparancy/etc]. You can rotate/scale the images, and tons of other stuff.

OpenGL is not what you use to create the images, it is what you use to display the final result.

The graphics artist will make the content that OpenGL uses to display on the screen, but the programmer must tell OpenGL how to use that content.

Anyway, hope this helps.
~Dom C.
binary1230

Share this post


Link to post
Share on other sites

  • Forum Statistics

    • Total Topics
      628293
    • Total Posts
      2981869
  • 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