Archived

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

Elfs1der

OpenGL 8 Step Guide to surpass OpenGL NEWB!

Recommended Posts

Well I was sitting here reading a few posts and thought that I should help out the general public with the basic questions that will get people started in a theroretical way. I dunno maybe a mod should make this a sticky or something.... **** 1. Many beginners want to start off very quickly, I know this because I was one of those people. However this is not good, with my motto I always think if I jump too far I will fall back; and if you get what I mean then thats good but if you don't what I'm trying to say is not to start off with OpenGL unless you FIRMLY know C++ very well. **** 2. Start of with a really good C++, theres really no point starting off with C now because it's basically the exact same thing just less advanced. A great book to start off with is C++ Primer Plus 4th edition. I have this book and its a little over a 1000 pages but its amazing book I highly recommend this. **** 3. Most computer people like to think that they know everything, my advice to you is don't get full of yourself because if you start skipping pages when reading books I can almost promise you that it will catch up with you. Just take the few more minutes that it takes to read the pages and go on. Even with me which I am I guess Intermediate level at C++ and beginner at OpenGL, when I read C++ Primer Plus(still do because I'm a dumbass and jumped ahead) I learned a lot on the way. **** 4. A good idea for reading any programming book is when you are done reading a chapter is to take what you learned in that chapter and summarize it(some books already do this) and then sort of make your own homework questions I guess you could say and then try then out. Best way I find to learn and most programmers is to manipulate what you just learned in the chapter and do some practical work before you go on, because things start to pile up very quickly. **** 5. Good thing to do once you know C++ classes pretty well is to start thinking about game structure and design just to get your imagination a boost. Just take a peice of paper and start drawing flow charts or something, anything that can help you understand game structure better. **** 6. If you are going to school or working a lot, or busy in general TRY not to procrastinate a lot. I speak from experience because if you read a chapter and don't read the next chapter for like 2 weeks after your retention level goes down quickly(for most people). This will just result in massive frustration down the road. **** 7. When coding this applys to advanced people aswell, try not to code for a long amount of time without testing your code and compiling it. Theres nothing like getting your hopes up when you just finished coding for 30 minutes straight and then you compile it and it doesn't work. I hate that. **** 8. If you goto school, lets say high-school, don't let your programming interupt your school work because even if you know lots of C++ when you get out of school that won't matter when you don't have the marks to support it. **** Well theres my 8 step guide to surpassing an OpenGL Newb. This some of this stuff doesn't apply to all people, but for most people my age(around 17) it does. Anyways hope I helped out some people, Enjoy! [edited by - Elfs1der on October 7, 2003 10:10:57 PM]

Share this post


Link to post
Share on other sites
I have to disagree with one of your statements
quote:
Start of with a really good C++, theres really no point starting off with C now because it's basically the exact same thing just less advanced

What you mean is C is a subset of C++. This is true, however, there are plenty of people using it and using it very well. Don't try to force your personal preference on others. Since OpenGL is designed to be used in a procedural manner, there is no advantage to using C++ over C.

But other than that, good advice.

I have a more consise 3 step guide to surpassing the OpenGL newbie stage:

1) If you don't understand C, C++ or how to use your compiler, learn how before you try to use OpenGL. If you don't, you should be posting in For Beginners.

2) RTF(OpenGL)M. At least get a basic understanding of the subject before posting here. This will prevent you from asking questions which are covered better by the manual. The OpenGL pages on MSDN are very good.

3) Use this forum to ask relevant questions.

Note that these steps are to be taken IN ORDER.

[edited by - benjamin bunny on October 8, 2003 8:51:24 AM]

Share this post


Link to post
Share on other sites
I use Delphi/Kylix to program in Opengl very happily, as do much of the opengl programming community. Delphi is based on pascal which is designed as a structural, procedural language and OpenGL fits incredibly neatly into its framework.

It''s also worth remembering that opengl is a GRAPHICS library and not a GAMES library. C++ is the standard these days for game coding, but it is not a completely homonogous standard in all fields. Many applications are written in Delphi and indeed many other langauges, depending upon the requirements and purposes of the application being coded. Opengl should be treated as a seperate learning process. I originally learned Opengl on c++ and found no problems (actually less) with using it with Delphi.

Share this post


Link to post
Share on other sites
quote:
Original post by benjamin bunny
What you mean is C is a subset of C++. This is true, however, there are plenty of people using it and using it very well. Don''t try to force your personal preference on others. Since OpenGL is designed to be used in a procedural manner, there is no advantage to using C++ over C.


Let me rephrase, I wasn''t trying to force anything, I was just saying that if you are pure beginner then really you might as well learn c++ rather than c.

Share this post


Link to post
Share on other sites
quote:
Original post by Elfs1der
Let me rephrase, I wasn''t trying to force anything, I was just saying that if you are pure beginner then really you might as well learn c++ rather than c.

No, if you are a pure beginner then either one will do. Both C and C++ contain the fundamentals of procedural programming, which is a good place for a beginner to begin. Eventually you''ll have to learn both (including the C-only parts of C which you usually do not learn in any depth when learning C++), so you may as well start with either.


How appropriate. You fight like a cow.

Share this post


Link to post
Share on other sites
I know this is going to sound unfair, but i really dont think this thread belongs here. Sure, its a great thread full of a lot of useful advice, but, i mean, you''re concentrating on empasising learning the language, which effectively is one step. Theres not really any newcomer friendly opengl advice in here...

Sorry to sound so picky..

Share this post


Link to post
Share on other sites
quote:
Original post by jonbell
Many (maybe most) console games are coded in C.


Thats because you dont really need an easy to maintain and reusable engine structure. Theres hardly any relicencing and patching going on in console games nowadays. Plus, c ''feels'' closer to the hardware haha

Share this post


Link to post
Share on other sites
Well if you learn c++ you basically know C, so i dont see what the problem is because if u know C++ you could still make same games in it. And another thing is if you are pure beginner you wouldn''t start out with c++ anyways maybe VB or turing, thats what I started on.

Share this post


Link to post
Share on other sites
When I was a pure beginner I started out with BASIC. That was a while ago, though. . .

I''d say the best language to start out with is Pascal (from which Delphi is derived). That one can also do OpenGL programming with it is certainly a nice bonus, too. C is just a step up from Pascal, IMHO, while VB is sigificantly different from C.

Share this post


Link to post
Share on other sites
the best language to start off with is the one you can relate to the most. Surely it is better to learn the princples of programming first before worrying about what language you learn? It is no good sitting a newbie down infront of C++ to learn the basics of programming when they might learn the idea faster from something like basic or pascal or java or anything like that. All too many ppl seem to put down basic because thats what it is, basic, a beginners language, which hides the nasty stuff and allows you to learn the basics of programing without having to worry.

Share this post


Link to post
Share on other sites
Personally, I found C++ far more intuitive. I dunno maybe it has to do with why people are always calling me a genious or something. Anyways, I like to go hard, then figure out the little things I don''t know. It''s like with any language, the best way to learn it, is to immerse yourself in it.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Announcements

  • Forum Statistics

    • Total Topics
      628294
    • Total Posts
      2981882
  • 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