Sign in to follow this  
Rizky Aulia Rahman

OpenGL Build UI in OpenGL for my 3D game world?

Recommended Posts

i'm trying to create my own User Interface such as: Button, panel, window, radiobutton, checkbox, etc..

the word "create" here means:

-designing UI  with own style

-programming they all.

 

well, my problem is: what functions/codes that i must call to draw it all?

 

in this terms, maybe the points are:

-Drawing 2d texture on screen NOT in 3d world game.

so if we're doing translation camera in 3d world game, the UI texture won't  be move.

 

-determine xy coordinates based on screen NOT based in 3d world game.

of course before we set UI texture  first thing that we have to do is determine some textures.

 

to more cleary, take look at the picture

this is a sample User Interface that i've found in google. but this is XNA c#. 

Capture2_zps917ccb91.png

i've learned the source codes how they work. after i understood the concept (include how they draw many textures with structured coordinates)

 

ok so, the problem is: could you show me the point/codes that i should use in openGL graphic programming? include:

-Drawing 2d texture on screen NOT in 3d world game.

-determine xy coordinates in screen.

Edited by Rizkay

Share this post


Link to post
Share on other sites
What you're looking for is called an orthographic projection. This is a 3D projection that does not include any perspective "shrinking" as objects get further away. Older versions of GL included the now-deprecated glOrtho function to accomplish this, but you should be able to duplicate the effects easily enough using a matrix math library such as GLM.

Essentially, an orthographic projection maps the screen to some range of coordinates, X and Y, so that you can draw objects on the X/Y grid and have them appear in the correct location on-screen.

The typical drawing order is to draw the game view using the game camera and projection, then switch the projection to an orthographic matrix and draw the UI elements as a series of quads. These quads will technically be 3D, in that they are drawn using the same exact types of function calls as drawing the game objects (binding vertex buffers, shaders and textures, rendering triangles) but the geometry is configured so that the shapes are flat quads on the X/Y plane. The Z coordinate is typically set to 0; or, if desired, you can use the Z coordinate to determine the visible ordering of the objects as necessary.

Share this post


Link to post
Share on other sites

*with mouse driver: you can draw your interface using photo shop,

*add animated buttons, similair to a web page design (hover, click ; textures),

then interact with your GUI using Test POS XY relative to screen pos (if not full screen) and by checking if your mouse button is

down or up. Then you have to support those handles for your buttons;

what will they do when clicked, or hovered over?.

 

example is coded using c/C++ (oop/structured)

//FILE MouseClass.h //
//windows mouse driver
//using windows library
//handles are usually updated via win main Loop, and passed data to windows handle
 
#include <windows.h>
#include <winuser.h>
#include <windef.h>
//simple example for winmouse class
//for using the windows mouse
//POINT  members { long x,y }
class WinMouse
{
private:
POINT CP;  //cursor position
public:
HWND windH;
RECT RectA;
long x, y;
long cx,cy;
int button1, button2;
WinMouse();
~WinMouse();
long CalcWindowX();
long CalcWindowY();
void ResetPos(long, long);
void GetRectPos(RECT );
void GetPos();
void SetPos(long x,long y);
void SetCenter();
void GetCenter();
void UpdateWindowCenter();
long GetX();
long GetY();
PosTest(int x, int y, int tx, int ty);
//note needed for relative mouse pos
//rect->left - GetX() , rect->top - GetY()
//GetWindowRect(HWND,RECT IN PTR)
//then Call
//this->GetRectPos(RECT );
};

////////////////////function definitions/////////////////////

WinMouse::WinMouse()
{
button1 = 0;
button2 = 0;
x=0;
y=0;
cx = 0;
cy = 0;
}
WinMouse::~WinMouse()
{
}
void WinMouse::UpdateWindowCenter()
{
this->GetPos();
 this->x = GetX() - this->cx;
 this->y = GetY() - this->cy;
}
WinMouse::PosTest(int x, int y, int tx, int ty)
{
 if(x < (GetX() -RectA.left ) && x + tx > (GetX() -RectA.left ))
 {
  if( y < (GetY() - RectA.top) && y + ty > (GetY() - RectA.top) )
  return 1;
  else
  return 0;
 }
 else
 return 0;
}
void WinMouse::GetCenter()
{
 x = (RectA.right + RectA.left)/2;
 y = (RectA.top + RectA.bottom)/2;
 
 cx = x;
 cy = y;
}
void WinMouse::SetCenter()
{
 x = RectA.left + RectA.right;
 y = RectA.top + RectA.bottom;  
 
 cx = x/2;
 cy = y/2;
 SetCursorPos(x/2,y/2);
}
 
void WinMouse::GetRectPos(RECT RectW)
{
 
 RectA.left = RectW.left;
 RectA.right = RectW.right;
 RectA.top = RectW.top;
 RectA.bottom = RectW.bottom;
}
long WinMouse::CalcWindowX()
{
 return this->RectA.right + this->RectA.left;
}
long WinMouse::CalcWindowY()
{
 return this->RectA.top + this->RectA.bottom;
}
 
void WinMouse::ResetPos(long Width, long Height)
{
 this->x = (long)(Width * (float).5);
 this->y = (long)(Height * (float).5);
SetCursorPos( this->x , this->y );
}
void WinMouse::SetPos(long x, long y)
{
SetCursorPos(x, y);
}
void WinMouse::GetPos()
{
GetCursorPos(&this->CP);
}
long WinMouse::GetX()
{
 return this->CP.x;
 
}
long WinMouse::GetY()
{
 return this->CP.y;
 
}
 
//EOF

Share this post


Link to post
Share on other sites

ok i got it.

here i got the things that must be understood before. there are some points to build User Interface in openGL.

  • firstly,  glOrtho help us to command "Orthographic Projection". although we're drawing 3d vertex no matter how far they are (in z coordinate). it will looks like 2D Image. but if we'd like to set our vertex Stay in front we should set z coordinate to 0.

          ok, lets try my code that i've made.

 void DrawImage(void) 
{
	int width = window.width;  //your window width
	int height = window.height;//your window height
glMatrixMode(GL_PROJECTION);
glPushMatrix();
glLoadIdentity();
glOrtho(0, width, height, 0, -1.0, 1.0);
glMatrixMode(GL_MODELVIEW);
glPushMatrix();
glLoadIdentity();
// here you will set xy coordinate of vertex on our screen
glBegin(GL_QUADS);
//there are reason why z must be set to 0
glVertex3f(0, 0, 0.0);
glVertex3f(0, 0.5f, 0.0);
glVertex3f(-1.0f, 0.5f, 0.0);
glVertex3f(-1.0f, 0, 0.0);
glEnd();
glPopMatrix();
glMatrixMode(GL_PROJECTION);
glPopMatrix();
glMatrixMode(GL_MODELVIEW);
}
  • second, set up our input/output for Keyboard and Mouse. that's why  it be called Graphic User Interface
Edited by Rizkay

Share this post


Link to post
Share on other sites

Note that if you are using an orthographic projection that is windowwidth by windowheight in size, then drawing a quad as small as you are drawing will pretty much just draw a single pixel or two, since the viewport is now windowwidth units wide and windowheight units tall, and you are drawing a quad 1 unit wide and 1/2 unit tall. You need to draw your objects larger in order to see anything useful.

Edited by JTippetts

Share this post


Link to post
Share on other sites

Note that if you are using an orthographic projection that is windowwidth by windowheight in size, then drawing a quad as small as you are drawing will pretty much just draw a single pixel or two, since the viewport is now windowwidth units wide and windowheight units tall, and you are drawing a quad 1 unit wide and 1/2 unit tall. You need to draw your objects larger in order to see anything useful.

of course,, you've remind me.

when we build User Interface i think the best way to set the parameters of glOrtho like:

  • left : 0.0f
  • right: in accordance with our window width
  • top: 0.0f
  • bottom: in accordance with our window height
  • Znear Zfar: 0,1  -> i don't know why is this so match with UI graphic (these values make the plane always on foreground of the vieweport)

there is a reason why do i set the right and the bottom in accordance with our window size. whenever we resize the window Coordinate of glOrtho won't be screwed.

do you remember in desktop application programming we're like drawing on Quadrant 4 (270 - 360 degree) but y coordinate it's just positive value NOT negative. therefore i set it up in accordance with desktop programming, it wold be easy!

 

well, for drawing vertex actually we have to adjust the coordinate also where  the max x/y coordinate is in accordance with our window size. so if we would follow this way you must set your vertex like we're doing graphic programming on deskop programming. lets look at my vertex code:

::glTranslatef(0,0,0); //the position of the element
glBegin(GL_QUADS
//look actully we've created left sidebar
glVertex3f(200, 0, 0); 
glVertex3f(200, height, 0);
glVertex3f(0.0f, height, 0);
glVertex3f(0, 0, 0);
glEnd();

yeahh we've created a sidebar at viewport.

 

you see? x/y coordinate is set to large value (Something unusual). but in this term i've set before, with this command: glOrtho(0, window.width, window.height, 0, 0, 1);

the viewport will be fit to our window. even you resize your window size i think we're just build simple algorithm (something like anchor?) cz the viewport and the window are same!

Edited by Rizkay

Share this post


Link to post
Share on other sites

Just so you understand that

Mouse coord' system only uses 2 deminsions X,Y

the coord starts from the Top zero and the left zero (going top to  (<, greater) down, and left to  (<, greater) right)

You dont need to use Ortho graphic projection to use a 2d (or 3D) GUI.

 

the default OpenGL matrix is 4 x 4 units,

if you do that math and a little guessing or debugging, it is simple enough to

match your mouse Position checks with your Cursor and buttons.

 

when the screen position or size is changed

 

code:

//inside MainWindowProc  (these are your handles for your window and GUI)

//(windows messege SIZE)

//(windows messege MOVE)

 

// dispatch messages
 switch (uMsg)

{

//...

 

case WM_SIZE:
  height = HIWORD(lParam);  // retrieve width and height
  width = LOWORD(lParam);
// ~(update mouse coords' center "relative")~ //

 

case WM_MOVE:

//~(update new mouse postions relative to new RECT screen position)~//
// Mouse_.GetRectPos(windowRect); //

 

Example thumb PIC (JPEG)

[attachment=19265:ex1.JPG]

Edited by Mathimetric

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
      628285
    • Total Posts
      2981837
  • 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