Sign in to follow this  

OpenGL Size in pixel of object in screen

Recommended Posts

Hi I want to make a GUI in OpenGL and so I want my widgets to have a specific size in pixels, but I want to have a few effects or models in it that glOrtho wouldn't look good (other than that it works fine) ... so any ideas how I get that to work? cu & thx ernii

Share this post

Link to post
Share on other sites
You could just switch between orthographic and perspective projection every
time you want to draw a different object. i.e. call glOrtho() when you want to render the GUI graphics, and gluPerspective() when you want to render the other stuff.

Share this post

Link to post
Share on other sites
If W and H are the viewport width and height, respectively, then you can measure pixels in your window with glOrtho: glOrtho2D(0,W,0,H, -1 , 1);

If you need to mix 3D with it, then size depends on the view angle. Assuming that you are using a 'regular' projection matrix (such as the type generated by gluPerspective) then what you need are:
W: viewport width in pixels
H: viewport height in pixels
Aspect: Aspect ratio of width/height.
FOV: Vertical field of view. (top to bottom of screen)

If your field of view is 90 degrees, top to bottom, then from the center of the screen to the top of the screen is 45 degrees. A point in space at X=0, Z=-1 unit (1 unit into the screen), will be just at the top of your viewport when Y = sin(45 degrees). This will give you a conversion factor:

At Z=-1 : sin(45) vertical world units = half a screen height. = H/2
This inversely proportional to Z depth units; an object twice as far away will be half the size.

Height in pixels = height of object * sin(45) * height of screen /2 /Z

If your projection matrix scales X and Y by the same amount (which is normally the case) , then the same formula should work for width.

Note, all of this is from memory, so there might be some bugs in my math. I can check it against my implementation when I get home, since I have done this same thing before.

[Edited by - DracoLacertae on September 27, 2006 5:15:28 PM]

Share this post

Link to post
Share on other sites

Its more like that I want to do like little animations with the Widgets so I need the pixel size of them anyway. But other than that I think it would very good :)

Okay, sorry, I just don't get it ;)
I use gluPerspective with an angle of 90 deg and I get the part that now the half screen height should have the size sin(45 deg) in world units.

Since half of the screen should have the size H/2 in world units (since it has the same amount of pixels), so the factor should be 1/(H / 2 / sin(45)).

I tried to scale everything with that, but it didn't work ... so I tried with only H/2 and it seemed to work, I also tried to move everything H/2 away and that worked to .... but sometimes it is wrong by like a pixel.

So I'm a little bit confused right now ;) ... what didn't I get right?

cu & thx

Share this post

Link to post
Share on other sites
Are you using GLU? I just found out about gluProject:

Just gluProject the corners of your object, and you'll get exactly where it is on the screen.

The method I gave may be off by a few pixels, because this method is not the method GL uses; instead it is a rather crude geometric construction. (When I find the code I last used it in, I'll post it.) To get the true pixel coordinates for a point in space, you need to transform using the projection and modelview matrices; much like how gluProject does.

Share this post

Link to post
Share on other sites
I want to transform the widget in 3D and that looks kind of odd with orthogonal projection, like a rotation in depth. ANd yes this is nearly only for eyecandy .. but it is still cool :)

Wow, that looks like the "solve problem" function for me :)
I will try it out. Thank you for the tip

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  

  • Partner Spotlight

  • Forum Statistics

    • Total Topics
    • Total Posts
  • Similar Content

    • By xhcao
      Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness. 
    • By cebugdev
      hi guys, 
      are there any books, link online or any other resources that discusses on how to build special effects such as magic, lightning, etc. in OpenGL? i mean, yeah most of them are using particles but im looking for resources specifically on how to manipulate the particles to look like an effect that can be use for games,. i did fire particle before, and I want to learn how to do the other 'magic' as well.
      Like are there one book or link(cant find in google) that atleast featured how to make different particle effects in OpenGL (or DirectX)? If there is no one stop shop for it, maybe ill just look for some tips on how to make a particle engine that is flexible enough to enable me to design different effects/magic 
      let me know if you guys have recommendations.
      Thank you in advance!
    • By dud3
      How do we rotate the camera around x axis 360 degrees, without having the strange effect as in my video below? 
      Mine behaves exactly the same way spherical coordinates would, I'm using euler angles.
      Tried googling, but couldn't find a proper answer, guessing I don't know what exactly to google for, googled 'rotate 360 around x axis', got no proper answers.
      The video shows the difference between blender and my rotation:
    • By Defend
      I've had a Google around for this but haven't yet found some solid advice. There is a lot of "it depends", but I'm not sure on what.
      My question is what's a good rule of thumb to follow when it comes to creating/using VBOs & VAOs? As in, when should I use multiple or when should I not? My understanding so far is that if I need a new VBO, then I need a new VAO. So when it comes to rendering multiple objects I can either:
      * make lots of VAO/VBO pairs and flip through them to render different objects, or
      * make one big VBO and jump around its memory to render different objects. 
      I also understand that if I need to render objects with different vertex attributes, then a new VAO is necessary in this case.
      If that "it depends" really is quite variable, what's best for a beginner with OpenGL, assuming that better approaches can be learnt later with better understanding?
    • By test opty
      Hello all,
      On my Windows 7 x64 machine I wrote the code below on VS 2017 and ran it.
      #include <glad/glad.h>  #include <GLFW/glfw3.h> #include <std_lib_facilities_4.h> using namespace std; void framebuffer_size_callback(GLFWwindow* window , int width, int height) {     glViewport(0, 0, width, height); } //****************************** void processInput(GLFWwindow* window) {     if (glfwGetKey(window, GLFW_KEY_ESCAPE) == GLFW_PRESS)         glfwSetWindowShouldClose(window, true); } //********************************* int main() {     glfwInit();     glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 3);     glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 3);     glfwWindowHint(GLFW_OPENGL_PROFILE, GLFW_OPENGL_CORE_PROFILE);     //glfwWindowHint(GLFW_OPENGL_FORWARD_COMPAT, GL_TRUE);     GLFWwindow* window = glfwCreateWindow(800, 600, "LearnOpenGL", nullptr, nullptr);     if (window == nullptr)     {         cout << "Failed to create GLFW window" << endl;         glfwTerminate();         return -1;     }     glfwMakeContextCurrent(window);     if (!gladLoadGLLoader((GLADloadproc)glfwGetProcAddress))     {         cout << "Failed to initialize GLAD" << endl;         return -1;     }     glViewport(0, 0, 600, 480);     glfwSetFramebufferSizeCallback(window, framebuffer_size_callback);     glClearColor(0.2f, 0.3f, 0.3f, 1.0f);     glClear(GL_COLOR_BUFFER_BIT);     while (!glfwWindowShouldClose(window))     {         processInput(window);         glfwSwapBuffers(window);         glfwPollEvents();     }     glfwTerminate();     return 0; }  
      The result should be a fixed dark green-blueish color as the end of here. But the color of my window turns from black to green-blueish repeatedly in high speed! I thought it might be a problem with my Graphics card driver but I've updated it and it's: NVIDIA GeForce GTX 750 Ti.
      What is the problem and how to solve it please?
  • Popular Now