• Advertisement
Sign in to follow this  

OpenGL OpenGL via Win32

This topic is 3506 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

I'm hoping someone knows something about displaying OpenGL in Win32 as I am fairly new. Here's a summary of the problem: I have been working on a project for a class where I use OpenGL only to draw lines and points. Everything else is done through custom code. Basically I have implemented the model->world->view->NDC transformations so now I have coordinates in the range of [-1,1] in both x and y axis, as they should be. I basically need to do 2 things at this point. 1). Map my normalized device coordinates to pixels which is simple enough to do. (e.g. (0,0) would map to (512,384) at a resolution of (1024x768) 2). Display them in Win32 using glVertex3f(#,#,#); The problem (yes I finally got to it) is that it seems like if I call glVertex(#,#,#) with any values greater than the absolute value of 1 they are clipped. My guess is this is a Win32 related issue because if I set up the viewport and projection/modelview matrices normally I still can't pass glVertex3f() with any numbers abs() > 1. My interim solution is to convert the vertices to screen coordinates, perform Z-Buffering, and then convert them back to NDC [-1,1] but that seems like a horrible way to do it. Are there any Win32/Opengl experts out there? Thanks Hornsj2

Share this post


Link to post
Share on other sites
Advertisement
I'm not exactly sure I got what you're trying to do, but shouldn't just setting an orthographic projection with your window's width and height should be enough?

Share this post


Link to post
Share on other sites
I don't understand why you would want to do your model->view->NDC transformations in software if that can be done with OpenGL with a single matrix multiplication.

You also don't have to map your NDC coordinates to pixels. This is what OpenGL can do. With a standard orthographic projection you can directly pass your NDC coordinates to OpenGL provided that the viewport has been setup correctly.
If you insist in wanting to pass vertex values with abs() > 1 you simply have to setup the ortho projetion matrix accordingly.

Also, OpenGL does the z-buffering for you, why would you want to do it yourself? Doing it yourself defeats the purpose of using OpenGL. Then you could aswell write your own software rasterizer.

Share this post


Link to post
Share on other sites
Basically I created my own version of a software renderer that uses OpenGL to talk to the hardware. There is no practical reason for this, I am in a class.


Basically I have set up a projection matrix, model matrix, and view matrix. Then I load geometry from flat files and process them through that pipeline to get coordinates in screen space.

At the end if this pipeline I have geometry in normalized device coordinates (NDC), which are [-1,1] in both axis directions.

I can send these coordinates to OpenGL using glVertex3f(#,#,#); and they render to the screen just fine.

However, I now want to implement a z-buffer algorithm and I need integer values to represent scan lines. I am faced with converting my coordinates (floats) to another coordinate system (integers) in order to implement the algorithm and then transform them back to the NDC.

It is possible that I mixed up. I am new to win32/opengl.

Share this post


Link to post
Share on other sites
There is no reason to use OpenGL at all if you are writing a software renderer. You are just making things (much) more complicated that way. So either use OpenGL the way it was intended to be used (ie. as a hardware accelerated rasterizer), or drop it alltogether. Just use your software renderer to draw to a memory buffer and blit that into a window.

Share this post


Link to post
Share on other sites
Yes, of course you are right. Sorry for the confusion. Unfortunately this is the assignment, OpenGl is required, so I will just do a couple of transformations between coordinates and be sad about the inefficiency.

Thanks for the tips.

Hornsj2

Share this post


Link to post
Share on other sites
So you were told to draw an OpenGL point for each of your software rasterized pixels ?! No offense, but what kind of ridiculous assignment is that supposed to be ? If so, then I would seriously question the competence of whomever gave you this assignment.

If you really have to use OpenGL to write a software renderer, then at least have your software rasterizer render into a memory buffer, upload it as a texture to OpenGL, and render it as a screen aligned quad.

Share this post


Link to post
Share on other sites
Quote:
Original post by Yann L
No offense, but what kind of ridiculous assignment is that supposed to be ? If so, then I would seriously question the competence of whomever gave you this assignment.



LOL! My thoughts!

Share this post


Link to post
Share on other sites
Outstanding, so my instructor gave me a bad assignment. If anyone else has a LOL, PST because I find that kind of input extremely valuable.

Hornsj2

Share this post


Link to post
Share on other sites
I think what they're trying to teach is the transformation pipeline. I'd done this a while back when I was in school as well. When I did that assignment there's a drawpixel function that take care of putting the pixel on the screen for a given screen coordinate. IIRC the function doesn't use glVertex*, I have to look at the source later. If you still need it, I can look it up later today.

I found out what it was when I had the class. All they did was create a canvas (a buffer of screen width x screen height in size of pixel data (rgb) ), so when you plot a pixel it just set the correct color at the correct location, when it's time to render then you call glDrawPixels and pass in this canvas. Hope that helps.

[Edited by - nhatkthanh on July 15, 2008 12:11:51 AM]

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • 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