• Advertisement

Archived

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

OpenGL simple 2D graphics API in OpenGL or DirectX?

This topic is 5490 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi everyone, I''m taking a graphics class and I have to write a basic wireframe render which does backface culling. As part of the project, we are allowed to use OpenGL or DirectX, but only for dumping out our calculations to the screen. This means I can only use simple calls like "set pixel at x,y" or "draw line from pixel x,y to a,b". The rest of the rendering, such as going through the viewing pipeline, backface culling, etc. I have to do myself, I just need a simple API in a C++ window that can draw to the screen, so once I have done all the rendering, I can make the simple calls to the grpahics api to draw my stuff to the window. Do you have any suggestions as to what API i could use? The professor suggested that C++ and OpenGL was a good combination. Thanks, Riz

Share this post


Link to post
Share on other sites
Advertisement
I''ve done pretty much the same sorts of things in my graphics classes. I always used C++ and GLUT, and I never had any problems.

Share this post


Link to post
Share on other sites
Hi mmelson,

Thanks for replying. I''ve never used GLUT before, but I looked at the API, and it doesn''t seem to have any functions to draw basic primitives, such as lines and points. Could you tell me what kind of setup you had for your graphics programs? I''d really appreciate any help,

thanks,
riz

Share this post


Link to post
Share on other sites
im am currently doing something similar, and am using GLUT, i currently using

glColor3f for my colour
glVertex2i for my put pixel,

but if any 1 actually knows how i can get direct access to the video memory like in direct draw in opengl i would be very happy :D as im sure glVertex2i is pretty slow

Share this post


Link to post
Share on other sites
GLUT is a small convenience toolkit for OpenGL, it handles things like the windowing system, and rudimentary input. All drawing is done through OpenGL.

riz, I think OpenGL is pretty well suited for what you have in mind. You should also consider GLUT to get a fast working OpenGL framework running, if you don''t need any fancy features.

supagu: drawing individual pixels by glVertex is pretty much the slowest way there is OpenGL is primarily a vector API. Either you use the texture method (create a texture of the size of the screen, directly write your pixels to it, and finally render it to the screen with a single quad), or drop OpenGL and use something like DirectDraw or, better, SDL.

Share this post


Link to post
Share on other sites
Ok I must be getting this all wrong but:

My assignment is to make a basic renderer from scratch. Once all my points have been transformed to their pixel positions, I have use some API to "dump" out the graphics to the screen, using simple functions like "draw line" in OpenGL or some graphics package. Basically, I can''t use OpenGL''s 3D capability at all.

Since OpenGL is primarily an API for 3D Graphics, I''m having trouble figuring out what settings to put for setting the GL camera and perpective matrix to ensure that I get only 2D output.

if anyone has any other graphics package, or a code example in GDI (native windows graphics calls) I would really appreciate it.

thanks,
riz

Share this post


Link to post
Share on other sites
OpenGL doesn''t require you to use the 3D features in any way. Every 3D API can be used as a 2D API, if you ignore the 3rd dimension.

You simply setup a 2D orthographic camera, by using glOrtho():

glOrtho(0, 1024, 0, 768, -1, 1);

That would be for a 1024x768 screen, as an example. You can now address the screen coordinates in the (0..1023/0..767) range. To plot a point, or draw a line, you use the glVertex2() function family. This works very well, if you want to process 2D vector graphics.

If you want direct raw access to each pixel, however, then this method is not optimal. This is the case, if you want to write your own rasterizer, and line drawing functions.

Share this post


Link to post
Share on other sites
aahhh I see

Thanks Yann L, I was just confused about how to set up an orthogonal camera, but one simple function call is very nice, hehe.

Thanks for everyone''s help, I''m going to go and try it out!

riz

Share this post


Link to post
Share on other sites

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By LifeArtist
      Good Evening,
      I want to make a 2D game which involves displaying some debug information. Especially for collision, enemy sights and so on ...
      First of I was thinking about all those shapes which I need will need for debugging purposes: circles, rectangles, lines, polygons.
      I am really stucked right now because of the fundamental question:
      Where do I store my vertices positions for each line (object)? Currently I am not using a model matrix because I am using orthographic projection and set the final position within the VBO. That means that if I add a new line I would have to expand the "points" array and re-upload (recall glBufferData) it every time. The other method would be to use a model matrix and a fixed vbo for a line but it would be also messy to exactly create a line from (0,0) to (100,20) calculating the rotation and scale to make it fit.
      If I proceed with option 1 "updating the array each frame" I was thinking of having 4 draw calls every frame for the lines vao, polygons vao and so on. 
      In addition to that I am planning to use some sort of ECS based architecture. So the other question would be:
      Should I treat those debug objects as entities/components?
      For me it would make sense to treat them as entities but that's creates a new issue with the previous array approach because it would have for example a transform and render component. A special render component for debug objects (no texture etc) ... For me the transform component is also just a matrix but how would I then define a line?
      Treating them as components would'nt be a good idea in my eyes because then I would always need an entity. Well entity is just an id !? So maybe its a component?
      Regards,
      LifeArtist
    • By QQemka
      Hello. I am coding a small thingy in my spare time. All i want to achieve is to load a heightmap (as the lowest possible walking terrain), some static meshes (elements of the environment) and a dynamic character (meaning i can move, collide with heightmap/static meshes and hold a varying item in a hand ). Got a bunch of questions, or rather problems i can't find solution to myself. Nearly all are deal with graphics/gpu, not the coding part. My c++ is on high enough level.
      Let's go:
      Heightmap - i obviously want it to be textured, size is hardcoded to 256x256 squares. I can't have one huge texture stretched over entire terrain cause every pixel would be enormous. Thats why i decided to use 2 specified textures. First will be a tileset consisting of 16 square tiles (u v range from 0 to 0.25 for first tile and so on) and second a 256x256 buffer with 0-15 value representing index of the tile from tileset for every heigtmap square. Problem is, how do i blend the edges nicely and make some computationally cheap changes so its not obvious there are only 16 tiles? Is it possible to generate such terrain with some existing program?
      Collisions - i want to use bounding sphere and aabb. But should i store them for a model or entity instance? Meaning i have 20 same trees spawned using the same tree model, but every entity got its own transformation (position, scale etc). Storing collision component per instance grats faster access + is precalculated and transformed (takes additional memory, but who cares?), so i stick with this, right? What should i do if object is dynamically rotated? The aabb is no longer aligned and calculating per vertex min/max everytime object rotates/scales is pretty expensive, right?
      Drawing aabb - problem similar to above (storing aabb data per instance or model). This time in my opinion per model is enough since every instance also does not have own vertex buffer but uses the shared one (so 20 trees share reference to one tree model). So rendering aabb is about taking the model's aabb, transforming with instance matrix and voila. What about aabb vertex buffer (this is more of a cosmetic question, just curious, bumped onto it in time of writing this). Is it better to make it as 8 points and index buffer (12 lines), or only 2 vertices with min/max x/y/z and having the shaders dynamically generate 6 other vertices and draw the box? Or maybe there should be just ONE 1x1x1 cube box template moved/scaled per entity?
      What if one model got a diffuse texture and a normal map, and other has only diffuse? Should i pass some bool flag to shader with that info, or just assume that my game supports only diffuse maps without fancy stuff?
      There were several more but i forgot/solved them at time of writing
      Thanks in advance
    • By RenanRR
      Hi All,
      I'm reading the tutorials from learnOpengl site (nice site) and I'm having a question on the camera (https://learnopengl.com/Getting-started/Camera).
      I always saw the camera being manipulated with the lookat, but in tutorial I saw the camera being changed through the MVP arrays, which do not seem to be camera, but rather the scene that changes:
      Vertex Shader:
      #version 330 core layout (location = 0) in vec3 aPos; layout (location = 1) in vec2 aTexCoord; out vec2 TexCoord; uniform mat4 model; uniform mat4 view; uniform mat4 projection; void main() { gl_Position = projection * view * model * vec4(aPos, 1.0f); TexCoord = vec2(aTexCoord.x, aTexCoord.y); } then, the matrix manipulated:
      ..... glm::mat4 projection = glm::perspective(glm::radians(fov), (float)SCR_WIDTH / (float)SCR_HEIGHT, 0.1f, 100.0f); ourShader.setMat4("projection", projection); .... glm::mat4 view = glm::lookAt(cameraPos, cameraPos + cameraFront, cameraUp); ourShader.setMat4("view", view); .... model = glm::rotate(model, glm::radians(angle), glm::vec3(1.0f, 0.3f, 0.5f)); ourShader.setMat4("model", model);  
      So, some doubts:
      - Why use it like that?
      - Is it okay to manipulate the camera that way?
      -in this way, are not the vertex's positions that changes instead of the camera?
      - I need to pass MVP to all shaders of object in my scenes ?
       
      What it seems, is that the camera stands still and the scenery that changes...
      it's right?
       
       
      Thank you
       
    • By dpadam450
      Sampling a floating point texture where the alpha channel holds 4-bytes of packed data into the float. I don't know how to cast the raw memory to treat it as an integer so I can perform bit-shifting operations.

      int rgbValue = int(textureSample.w);//4 bytes of data packed as color
      // algorithm might not be correct and endianness might need switching.
      vec3 extractedData = vec3(  rgbValue & 0xFF000000,  (rgbValue << 8) & 0xFF000000, (rgbValue << 16) & 0xFF000000);
      extractedData /= 255.0f;
    • By Devashish Khandelwal
      While writing a simple renderer using OpenGL, I faced an issue with the glGetUniformLocation function. For some reason, the location is coming to be -1.
      Anyone has any idea .. what should I do?
  • Advertisement