Sign in to follow this  
MaimaVanPersie

OpenGL Quad not drawing correctly (Beginner)

Recommended Posts

Hello guys, I only started learning OpenGL recently and I have been able to draw several primitives. I wanted to organize my code by placing it in classes and stuff as opposed to putting it all in main. I have been able to draw a quad with texture on it, now when I call render all I see is this odd result: http://imgur.com/auKpRGH

 

Here's what I have, please point out my mistake(s) I'd greatly appreciate that :)

 

Global Initializations in main.cpp: 

Vertex Vertices[] =
{ 
Vertex(glm::vec3(1.0f, 1.0f, 0.0f), glm::vec2(0.0f, 0.0f), glm::vec3(0.0f,0.0f,0.0f)),
Vertex(glm::vec3(1.0f, -1.0f, 0.0f), glm::vec2(0.0f, 1.0f), glm::vec3(0.0f,0.0f,0.0f)),
Vertex(glm::vec3(-1.0f, -1.0f, 0.0f), glm::vec2(1.0f, 1.0f), glm::vec3(0.0f,0.0f,0.0f)),
Vertex(glm::vec3(-1.0f, 1.0f, 0.0f), glm::vec2(1.0f, 0.0f), glm::vec3(0.0f,0.0f,0.0f)),
};

Render function in main.cpp: 

void Render()
{
Sprite Background(Vertices, sizeof(Vertices) / sizeof(Vertices[0]));
Background.Render();
glutSwapBuffers();}

My Sprite.h header:

class Vertex
{
public:
Vertex(const glm::vec3& pos, const glm::vec2& texCoordinates, const glm::vec3& colors) 
{
this->m_Pos = pos;
this->m_Tex = texCoordinates;
this->m_Col = colors;
}


private:
glm::vec3 m_Pos;
glm::vec2 m_Tex;
glm::vec3 m_Col;
};


class Sprite
{
public:
Sprite();
Sprite(Vertex* vertices, unsigned int numOfVertices);
~Sprite();


void Render();


private:


enum { POSITION_BUFFER, TEXTURE_BUFFER, COLOR_BUFFER, NUM_OF_BUFFERS };


GLuint m_VertexArrayObject;   
GLuint m_VertexBufferObject[NUM_OF_BUFFERS];
GLuint m_ElementBufferObject;
GLuint m_Program;
ShaderLoader m_Shader;
unsigned int m_DrawCount; 
};

My Sprite.cpp file:

#include "Sprite.h"


Sprite::Sprite()
{
m_Program = m_Shader.CreateProgram("VShader.vs", "FShader.fs");
}


Sprite::~Sprite()
{

}


Sprite::Sprite(Vertex* vertices, unsigned int numOfVertices)
{
m_DrawCount = numOfVertices;
glGenVertexArrays(1, &m_VertexArrayObject);
glBindVertexArray(m_VertexArrayObject);


glGenBuffers(1, m_VertexBufferObject);
glBindBuffer(GL_ARRAY_BUFFER, m_VertexBufferObject[POSITION_BUFFER]);
glBufferData(GL_ARRAY_BUFFER, numOfVertices * sizeof(vertices[0]), vertices, GL_STATIC_DRAW);


glVertexAttribPointer(0, 3, GL_FLOAT, GL_FALSE, 0, (GLvoid*)0);

glEnableVertexAttribArray(0);
glBindVertexArray(0);
}


void Sprite::Render()
{
glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);


glUseProgram(m_Program);
glBindVertexArray(m_VertexArrayObject);


glDrawArrays(GL_QUADS, 0, m_DrawCount);


glBindVertexArray(0);
}

Basically, I just want to draw the quad for now. And then, I want to be able to pass in the texture coordinates to display a nice picture. In the future, I want to be able to create multiple sprites like this and stuff like that. Am I doing it right? And what seems to be the problem with my code above? Why is it not producing the expected result? 

 

Thank you very much for reading my thread and I appreciate any help/advice you could give me. 

 
Edited by MaimaVanPersie

Share this post


Link to post
Share on other sites

Hello,

The problem you are experiencing has to do with the layout of your vertex data in C++, relative to the layout of your OpenGL buffer. You have already come a long way though and what you are doing is mostly correct.

First off, on the intended layout of your OpenGL buffers, it is common practice to create only one buffer for all your vertex properties whenever possible. In this case, that means that the vertex position, texture coordinate and color are combined in an interleaved form into one buffer. This means you will only need one Vertex Buffer Object. Think of it as (v1 x, v1 y, v1 z, v1 u, v1 v, V1 r, v1 g, v1 b, v2 x, v2 y, ...). This also happens to be an exact match to the vertices in your C++ Vertex array. When you call:

glBufferData(GL_ARRAY_BUFFER, numOfVertices * sizeof(vertices[0]), vertices, GL_STATIC_DRAW);

your OpenGL buffer is actually filled with exactly that data.

Using that buffer, it is up to you to specify where in that buffer your vertex positions are located. As you already wrote, you can use glVertexAttribPointer for that. You wrote:

glVertexAttribPointer(0, 3, GL_FLOAT, GL_FALSE, 0, (GLvoid*)0);

The first parameter here is an index to a generic vertex attribute. It is basically an index to the property in your vertex shader that will receive this bit of data. You can use glGetAttribLocation to get that index of your don't know what it is. If you have only one property, 0 is (probably?) a pretty safe bet.

The second parameter you provided is correct. 3 shows you have 3 float for this property, an xyz triplet, turned into a vec3 in glsl.

The third and fourth parameters are also correct. These denote the type and normalization of the data.

The fifth parameter is where things get interesting. This is the stride, the byte offset between consecutive generic vertex attributes. In other words, in your case, the size in bytes of your Vertex structure. This is the offset between your separate vertices. If you specify 0 here, it defaults to the size of the given property, which is the size of 3 floats in this case.

The sixth and final parameter is a 'pointer', a byte offset to the component you are referring to for this property. For each vertex, this should point to the first float (or just the vec2/vec3 itself) of the property you are declaring. C++ has a useful function here: offsetof. So you could write something like:

(void *)offsetof(Vertex, m_Pos)

I'm not entirely sure if having m_Pos private will cause problems for that call.

 

Now looking back at what you had written so far, what you actually see happening, is that your entire vertex array is interpreted as triplets of xyz. Noting that your displayed coordinates are in the [-1, 1] range for xy with an ignored z, what you see being drawn starts to make sense.

Just two more small things that I would like to point out as advice. You are using quads, which makes sense for sprites, but please note that quads are now deprecated and have even been removed in modern OpenGL versions. Instead, try to form your quads using two triangles.

Also, since you are programming in C++, try using containers for your data whenever you can. If you pass a pointer to an array and a length of that array, you could have probably used a vector instead. Those actually clean up after themselves, without you having to delete them, and you can query their size easily.

Edited by Ignifex

Share this post


Link to post
Share on other sites

Hello Ignifex, 

Thank you for your help. I have been able to fix the problem with the triangle. I also took your advice and drew the quad as two triangles. I have also used indices for efficiency as well. I guess the last thing I'm stuck on before moving on to doing other things is texturing. Here is how my code looks like right now:

 

Sprite::Sprite(Vertex* vertices, unsigned int numVertices)
{
m_NumVertices = numVertices;


GLubyte m_Background[] = { 0, 1, 3, 1, 2, 3 };


glGenVertexArrays(1, &m_VertexArrayObject);
glBindVertexArray(m_VertexArrayObject);


glGenBuffers(1, &m_VertexBufferObject);
glBindBuffer(GL_ARRAY_BUFFER, m_VertexBufferObject);
glBufferData(GL_ARRAY_BUFFER, m_NumVertices * sizeof(vertices[0]), vertices, GL_STATIC_DRAW);


glGenBuffers(1, &m_ElementBufferObject);
glBindBuffer(GL_ELEMENT_ARRAY_BUFFER, m_ElementBufferObject);
glBufferData(GL_ELEMENT_ARRAY_BUFFER, sizeof(m_Background), m_Background, GL_STATIC_DRAW);


glVertexAttribPointer(0, 3, GL_FLOAT, GL_FALSE, 5 * sizeof(GLfloat), (GLvoid*)0);
glVertexAttribPointer(1, 2, GL_FLOAT, GL_FALSE, 5 * sizeof(GLfloat), (GLvoid*)(3 * sizeof(GLfloat)));


glEnableVertexAttribArray(0);
glEnableVertexAttribArray(1);


glGenTextures(1, &m_Textures);
glBindTexture(GL_TEXTURE_2D, m_Textures);


// Texture Wrapping
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_S, GL_REPEAT);
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_T, GL_REPEAT);


// Texture Filtering 
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR);
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR);


unsigned char* image = SOIL_load_image("adventure.png", &m_iWidth, &m_iHeight, 0, SOIL_LOAD_RGBA);
glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA, m_iWidth, m_iHeight, 0, GL_RGBA, GL_UNSIGNED_BYTE, image);


SOIL_free_image_data(image);
glBindTexture(GL_TEXTURE_2D, 0);
}


void Sprite::Draw()
{
glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);


glActiveTexture(GL_TEXTURE0);
glBindTexture(GL_TEXTURE_2D, m_Textures);
glUniform1i(glGetUniformLocation(m_Program, "Texture1"), 0);


glUseProgram(m_Program);
glBindVertexArray(m_VertexArrayObject);


glDrawElements(GL_TRIANGLES, 6, GL_UNSIGNED_BYTE, 0);


glBindTexture(GL_TEXTURE_2D, 0);
glBindVertexArray(0);


glutSwapBuffers();
}

For some reason the texture is not showing.  :(

Do you spot a mistake by any chance? 

 

Also I tried using vectors to store my vertices in but it required a bit of extra work including returning pointers from functions and things like that so for now I decided to move on with a simple pointer.   

Share this post


Link to post
Share on other sites

Nice to see you got it working already!

I found one thing that might be your problem. You are calling glUniform1i before glUseProgram. However, the uniform set by glUniform1i is actually set for the active program, set by a call to glUseProgram. This should however allow it to work in the next Draw call.

Could you post your shaders as well? If you want to test your texture coordinates, you could try rendering these out directly in your fragment shader.

Share this post


Link to post
Share on other sites

Here are my shaders: 

Vertex Shader:

#version 430 core

// Input
in layout (location = 0) vec3 VertexPos;
in layout (location = 1) vec2 TexCoordinate;
in layout (location = 2) vec4 VertexColors;


// Output 
out vec4 outputColors;
out vec2 TexCoord;

void main()
{
gl_Position = vec4(VertexPos, 1.0f);
outputColors = VertexColors;
TexCoord = TexCoordinate;
}

Fragment Shader:

#version 430 core

in vec4 outputColors;
in vec2 TexCoord;

out vec4 VertexColors;

uniform sampler2D Texture1;

void main()
{
VertexColors = texture(Texture1, TexCoord);
//VertexColors = outputColors;
}

And here is how I'm introducing vertex information and rendering the scene in main.cpp header file

Vertex Position[] =
{
Vertex(glm::vec3(1.0f, 1.0f, 0.0f), glm::vec2(0.0f, 0.0f)),
Vertex(glm::vec3(1.0f, -1.0f, 0.0f), glm::vec2(0.0f, 1.0f)),
Vertex(glm::vec3(-1.0f, -1.0f, 0.0f), glm::vec2(1.0f, 1.0f)),
Vertex(glm::vec3(-1.0f, 1.0f, 0.0f), glm::vec2(1.0f, 0.0f))
};

Render

void Render()
{
Sprite Background(Position, sizeof(Position) / sizeof(Position[0]));
Background.Draw();
}

I tried calling glUniform1i before glUseProgram but that did not fix the problem. Nevertheless I still appreciate you helping me out  :)

Edited by MaimaVanPersie

Share this post


Link to post
Share on other sites

Hmm, I can't really find any other problems just by looking over your code.

Could you try using VertexColors = vec4(TexCoord, 0.0, 1.0); in your fragment shader, to rule out texture coordinates as a problem? This should give you a fancy red/green gradient.

Do you have a debugger you could use to check whether the image data returned by SOIL_load_image is correct? If it has any variation in pixel values, it should be fine.

You could also try OpenGL's internal error logging functions. See here. If you want to test a part of your code, just call glGetError before it to clean up previous errors and call it again afterwards to get the error you are looking for.

Share this post


Link to post
Share on other sites

Could you try using VertexColors = vec4(TexCoord, 0.0, 1.0); in your fragment shader, to rule out texture coordinates as a problem? This should give you a fancy red/green gradient.

 

I still got a white screen (the two triangles). Looks like I'm having a texture coordinates problem?  

Share this post


Link to post
Share on other sites

If it is white, it indicates there is something wrong with your fragment shader or its output assignment. With that statement, vec4(TexCoord, 0.0, 1.0), the blue channel should be 0, resulting in any black/red/green/yellow tint, regardless of your texture coordinates.

Like the inputs of your vertex shader, the output of your fragment shader also needs to be mapped. In your case, you are writing directly to the backbuffer, which has 1 color output, index 0. For as far as i know, if you have one output variable in your fragment shader, that should automatically be bound to output 0, but this might be something worth checking. You can check here for more info on output assignments.

Once you have checked your output assignment, it probably helps to check if your shader program has any errors. See here and here.

Edited by Ignifex

Share this post


Link to post
Share on other sites

If it is white, it indicates there is something wrong with your fragment shader or its output assignment. With that statement, vec4(TexCoord, 0.0, 1.0), the blue channel should be 0, resulting in any black/red/green/yellow tint, regardless of your texture coordinates.

Like the inputs of your vertex shader, the output of your fragment shader also needs to be mapped. In your case, you are writing directly to the backbuffer, which has 1 color output, index 0. For as far as i know, if you have one output variable in your fragment shader, that should automatically be bound to output 0, but this might be something worth checking. You can check here for more info on output assignments.

Once you have checked your output assignment, it probably helps to check if your shader program has any errors. See here and here.

 

I did all that and it still did not report any errors. But I have been able to resolve the problem, I just needed to move the shader.create function from my Sprite constructor to my Sprite::Sprite(Vertex* vertices, unsigned int numVertices). *sigh* Thank you for your help, sorry if I exhausted you. 

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
      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