Sign in to follow this  
NandoSoftIndieGames

OpenGL 2D in Opengl 3.2?

Recommended Posts

Hello all

I was wondering if there is a simple way of doing 2D in the new OpenGL

Ive traveled the whole web for tutorials and all of these guys just keen on using screen coordinates for their purposes (-1,-1, 1,1)

Yes ofcourse one could think to start dividing all your coords by your screen space but that is not a clean way of doing it specially if you want to render worlds bigger than your screen
(In other words I dont want to have it that way on my project)



So if anybody in here could teach me step by step on how to do this I would be thankful

I already know how to create shader programs and all that stuff, the part that is really messing me up is;

- where to set up my coordinate system
- how to set it up

Share this post


Link to post
Share on other sites
I suggest that you do what other games are doing. Make the usual orthographic projection matrix.
They usually call glOrtho(0.0, windowWidth, 0.0, windowHeight, znear, zfar)

Some people invert the y axis because they want it to go from top (0.0) to bottom (windowHeight) so you just swap your values
glOrtho(0.0, windowWidth, windowHeight, 0.0, znear, zfar)

Share this post


Link to post
Share on other sites
Replicate the functionality of it instead if you cannot use it. The point is not that you should use that particular function, but that you should use the projection is produces. Just create the corresponding matrix and load it into your shader if that's how you want to do it. The idea is still the same; use an orthographic projection, and create it using the parameters corresponding to the call V-man showed. Any decent documentation or reference manual will show you what the matrix from glOrtho looks like.

Share this post


Link to post
Share on other sites
You need to build an ortho projection matrix and get it to your shader as a uniform mat4.

You can either look up the what the function is on your own it is described here [url="http://www.opengl.org/sdk/docs/man/xhtml/glOrtho.xml"]http://www.opengl.or...tml/glOrtho.xml[/url] but it looks like the syntax is kind of confusing.

An ortho projection function is available in the GLM library [url="http://glm.g-truc.net/api-0.9.1/a00237.html#ga71777a3b1d4fe1729cccf6eda05c8127"]http://glm.g-truc.ne...cccf6eda05c8127[/url]

I haven't done any 2D games so I don't know how you want to handle your coordinates but I have used screen coordinates for my on-screen drawing with sampler2DRect in my fragment shader

Share this post


Link to post
Share on other sites
code to build ortho matrix:

[font=Monaco,][quote][color="#666600"]void [/color][color=#660066]Ortho[/color][color=#666600](float *m, [/color][color=#000088]float[/color][color=#000000] left[/color][color=#666600],[/color][color=#000000] [/color][color=#000088]float[/color][color=#000000] right[/color][color=#666600],[/color][color=#000000] [/color][color=#000088]float[/color][color=#000000] top[/color][color=#666600],[/color][color=#000000] [/color][color=#000088]float[/color][color=#000000] bottom[/color][color=#666600],[/color][color=#000000] [/color][color=#000088]float[/color][color=#000000] znear[/color][color=#666600],[/color][color=#000000] [/color][color=#000088]float[/color][color=#000000] zfar[/color][color=#666600])[/color][color=#000000]
[/color][color=#666600]{[/color][color=#000000]
[/color][color=#000000] [/color][color=#000088]float[/color][color=#000000] tx [/color][color=#666600]=[/color][color=#000000] [/color][color=#666600]-[/color][color=#000000] [/color][color=#666600]([/color][color=#000000]right [/color][color=#666600]+[/color][color=#000000] left[/color][color=#666600])[/color][color=#000000] [/color][color=#666600]/[/color][color=#000000] [/color][color=#666600]([/color][color=#000000]right [/color][color=#666600]-[/color][color=#000000] left[/color][color=#666600]);[/color][color=#000000]
[/color][color=#000000] [/color][color=#000088]float[/color][color=#000000] ty [/color][color=#666600]=[/color][color=#000000] [/color][color=#666600]-[/color][color=#000000] [/color][color=#666600]([/color][color=#000000]top [/color][color=#666600]+[/color][color=#000000] bottom[/color][color=#666600])[/color][color=#000000] [/color][color=#666600]/[/color][color=#000000] [/color][color=#666600]([/color][color=#000000]top [/color][color=#666600]-[/color][color=#000000] bottom[/color][color=#666600]);[/color][color=#000000]
[/color][color=#000000] [/color][color=#000088]float[/color][color=#000000] tz [/color][color=#666600]=[/color][color=#000000] [/color][color=#666600]-[/color][color=#000000] [/color][color=#666600]([/color][color=#000000]zfar [/color][color=#666600]+[/color][color=#000000] znear[/color][color=#666600])[/color][color=#000000] [/color][color=#666600]/[/color][color=#000000] [/color][color=#666600]([/color][color=#000000]zfar [/color][color=#666600]-[/color][color=#000000] znear[/color][color=#666600]);[/color][color=#000000]
[/color][color=#000000]
[/color][color=#000000] Identity(m); //identity matrix[/color][color=#000000]
[/color][color=#000000]
[/color][color=#000000] m[/color][color=#666600][[/color][color=#006666]0[/color][color=#666600]][/color][color=#000000] [/color][color=#666600]=[/color][color=#000000] [/color][color=#006666]2.0f[/color][color=#000000] [/color][color=#666600]/[/color][color=#000000] [/color][color=#666600]([/color][color=#000000]right [/color][color=#666600]-[/color][color=#000000] left[/color][color=#666600]);[/color][color=#000000]
[/color][color=#000000] m[/color][color=#666600][[/color][color=#006666]12[/color][color=#666600]][/color][color=#000000] [/color][color=#666600]=[/color][color=#000000] tx[/color][color=#666600];[/color][color=#000000]
[/color][color=#000000] m[/color][color=#666600][[/color][color=#006666]5[/color][color=#666600]][/color][color=#000000] [/color][color=#666600]=[/color][color=#000000] [/color][color=#006666]2[/color][color=#000000] [/color][color=#666600]/[/color][color=#000000] [/color][color=#666600]([/color][color=#000000]top [/color][color=#666600]-[/color][color=#000000] bottom[/color][color=#666600]);[/color][color=#000000]
[/color][color=#000000] m[/color][color=#666600][[/color][color=#006666]13[/color][color=#666600]][/color][color=#000000] [/color][color=#666600]=[/color][color=#000000] ty[/color][color=#666600];[/color][color=#000000]
[/color][color=#000000] m[/color][color=#666600][[/color][color=#006666]10[/color][color=#666600]][/color][color=#000000] [/color][color=#666600]=[/color][color=#000000] [/color][color=#666600]-[/color][color=#006666]2[/color][color=#000000] [/color][color=#666600]/[/color][color=#000000] [/color][color=#666600]([/color][color=#000000]zfar [/color][color=#666600]-[/color][color=#000000] znear[/color][color=#666600]);[/color][color=#000000]
[/color][color=#000000] m[/color][color=#666600][[/color][color=#006666]14[/color][color=#666600]][/color][color=#000000] [/color][color=#666600]=[/color][color=#000000] tz[/color][color=#666600];[/color][color=#000000]
[/color][color=#000000]
[/color][color=#000000] [/color][color=#000088]return[/color][color=#000000] m[/color][color=#666600];[/color][color=#000000]
[/color][color=#666600]}[/color][/quote][color=#666600][/color][/font]

Share this post


Link to post
Share on other sites
in a shader u would transform your vertex positions as normal with the projection matrix.

also I would recomment NOT to use your screen size for creating your matrix. Just think about how many world-units the player should see in one direction and calculate the size of the other with your screen ratio.

for example you want the player to see 10 in width u have to set a height of 7.5 (ratio: 4/3), I think this is importandt because you wouldn't want the player to see more of the game depeding on their screen resolution.

Another thing I like to do is to set the center of the screen in the center of the projection, so instead of
ortho(0, 10, 0, 7.5 ...

I use
ortho(-5, 5, -3.75, 3.75 ...

Share this post


Link to post
Share on other sites
[quote name='Danny02' timestamp='1306417907' post='4816039']
in a shader u would transform your vertex positions as normal with the projection matrix.

also I would recomment NOT to use your screen size for creating your matrix. Just think about how many world-units the player should see in one direction and calculate the size of the other with your screen ratio.

for example you want the player to see 10 in width u have to set a height of 7.5 (ratio: 4/3), I think this is importandt because you wouldn't want the player to see more of the game depeding on their screen resolution.

Another thing I like to do is to set the center of the screen in the center of the projection, so instead of
ortho(0, 10, 0, 7.5 ...

I use
ortho(-5, 5, -3.75, 3.75 ...
[/quote]

Oh but Im doing 2D so I want to map vertices to pixel coordinates

with this I have no geometry being rendered (if I toggle the ortho projection it displays the polygon tho)


[code]
GLint _uniform_location_matrix = -1;

glm::mat4 _projection(1.0f);
_projection = glm::ortho(0, 800, 600, 0, -100, 100);

CreateVBO();

Shader _basic_shader("..\\Resources\\Shaders\\Basic.v.glsl", "..\\Resources\\Shaders\\Basic.f.glsl");
_basic_shader.Compile(); if ( _basic_shader.GetProgramId() == NULL ) return;

glUseProgram(_basic_shader.GetProgramId());

_uniform_location_matrix = glGetUniformLocation(_basic_shader.GetProgramId(), "mvpMatrix");

glUniformMatrix4fv(_uniform_location_matrix, 1, GL_FALSE, glm::value_ptr(_projection));

while(true)Render();
[/code]

[code]
#version 400

uniform mat4 mvpMatrix;

layout(location=0) in vec4 in_Position;
layout(location=1) in vec4 in_Color;
out vec4 ex_Color;

void main(void)
{
gl_Position = mvpMatrix * in_Position;
ex_Color = in_Color;
}
[/code]

[code]
#version 400

in vec4 ex_Color;
out vec4 out_Color;

void main(void)
{
out_Color = ex_Color;
}
[/code]

Share this post


Link to post
Share on other sites
why would u want to map vertices to single pixels?


just assume u would want to do some pixel art where textures have to align perfectly to pixels so u won't get flickering with gl_nearest.
In this case i would take care of this in the vertex shader. So you don't have to handle this View(Render) feature in your Controller(Game logic)

Share this post


Link to post
Share on other sites
[quote name='Danny02' timestamp='1306427167' post='4816095']
why would u want to map vertices to single pixels?


just assume u would want to do some pixel art where textures have to align perfectly to pixels so u won't get flickering with gl_nearest.
In this case i would take care of this in the vertex shader. So you don't have to handle this View(Render) feature in your Controller(Game logic)
[/quote]

I though I was doing just that :S

Share this post


Link to post
Share on other sites
You could just fill a vertexbuffer with one quad (or more) like so:


[code]
Vertex vertices[] =
{
{ Vector3f(), Vector2f(), }, //Top-left
{ Vector3f( (float)width, 0, 0 ), Vector2f( 1.0f, 0.0f ), }, //Top-right
{ Vector3f( 0.0f, (float)height, 0.0f ), Vector2f( 0.0f, 1.0f), }, //Bottom-left
{ Vector3f( (float)width, (float)height, 0.0f ), Vector2f( 1.0f, 1.0f), }, //Bottom-right
};
[/code]

where Vertex would be three floats for position and two for uv. Texture coordinates are flipped on the y-axis here (DirectX convention).
Then in your vertex shader you could place the quad like so:

[code]

uniform ivec2 ScreenSize;
uniform vec2 translation;
uniform vec2 scale = vec2( 1.0, 1.0 );
out vec2 texCoord;
void main()
{
vec4 vPos;
vPos.x = (gl_Vertex.x * scale.x + translation.x) / (ScreenSize.x/2.0f) - 1.0f;
vPos.y = 1.0f - (gl_Vertex.y * scale.y + translation.y) / (ScreenSize.y/2.0f);
vPos.z = 0.0f;
vPos.w = 1.0f;
gl_Position = vPos;
texCoord = vec2( gl_MultiTexCoord0.x, -gl_MultiTexCoord0.y ); //Flip back uv's y axis
}
[/code]

This code is for OpenGL 2.1 so you might want to update it a bit but it gives the basic idea.

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  

  • Forum Statistics

    • Total Topics
      628282
    • Total Posts
      2981805
  • 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