Followers 0

# OpenGL opengl window and vbo vertexes

## 14 posts in this topic

hello,
I use this chunk of code for setup a windows for opengl 3.3:

HWND CreateAppWindow(const WNDCLASSEX &wcl, const char *pszTitle)
{
// Create a window that is centered on the desktop. It's exactly 1/4 the
// size of the desktop. Don't allow it to be resized.

DWORD wndExStyle = WS_EX_OVERLAPPEDWINDOW;
DWORD wndStyle = WS_OVERLAPPED | WS_CAPTION | WS_SYSMENU |
WS_MINIMIZEBOX | WS_CLIPCHILDREN | WS_CLIPSIBLINGS;

HWND hWnd = CreateWindowEx
(wndExStyle, wcl.lpszClassName, "title",
wndStyle, 0, 0, 0, 0, 0, 0, wcl.hInstance, 0);

if (hWnd)
{
int screenWidth = GetSystemMetrics(SM_CXSCREEN);
int screenHeight = GetSystemMetrics(SM_CYSCREEN);
int halfScreenWidth = screenWidth / 2;
int halfScreenHeight = screenHeight / 2;
int left = (screenWidth - halfScreenWidth) / 2;
int top = (screenHeight - halfScreenHeight) / 2;
RECT rc = {0};

SetRect(&rc, left, top, left + halfScreenWidth, top + halfScreenHeight);
AdjustWindowRectEx(&rc, wndStyle, FALSE, wndExStyle);
MoveWindow(hWnd, rc.left, rc.top, rc.right - rc.left, rc.bottom - rc.top, TRUE);

GetClientRect(hWnd, &rc);
m_windowWidth = rc.right - rc.left;
m_windowHeight = rc.bottom - rc.top;
}

return hWnd;
};


The problem is that i can't understand how the vbo vertexes are related to the window.
For example i use these points:
-1.0, -1.0, 0.5;
-1.0 , 1.0,  0.5;
1.0, 1.0, 0.5;

and i use this two shaders:
i set the uniform mat4 MVP to identity

#version 330
in vec3 VertexPosition;
uniform mat4 MVP;
void main()
{
gl_Position = MVP * vec4( VertexPosition, 1.0 );

}


and this fragment shader(the uniform vec4 color is set corrected by my project:

#version 330

out vec4 outputColor;
uniform vec4 color;
void main()
{
outputColor = color;
}


the problem is that the triangle is not correct, it must be the half of the screen but it isn't, is more smaller.

i try to use the left/bottom 0 to -1 and the right/top to -1 , but don't work.
How i can create a triangle that is half of the entire screen ? and how are related  the vbo vertexes to the width and height of the screen?
my goal is be able to set the entire coordinate for example 800 if the width of the screen is 800 ecc....
is possible?
my viewport recreated always in the render loop is
glViewport(0.0, 0.0, 800, 600);

0

##### Share on other sites

You can think of glViewport as defining the drawable area in the window. If your window is larger than 800x600, then your fixed viewport will not cover the whole window. On the other hand, if your window is actually smaller than 800x600, the drawable region extends outside the window.

The coordinates you then draw will be mapped to the viewport such that the post-transformed coordinates (-1, -1) corresponds to the bottom-left corner of the viewport, and (1, 1) corresponds to the upper-left corner of the viewport. Since you have the MVP matrix set to the identity matrix, the coordinates you pass and the post-transformed coordinates are the same.

Let's say you have a window that is 1600x1200 pixels, and you define the viewport as in your code. The viewport then covers the bottom left-half of the window. If you then draw a triangle with coordinates (-1,-1) [the bottom-left corner of the viewport], (-1, 1) [the top-right corner of the viewport] and (1, -1) [the bottom-left corner of the viewport], the triangle will cover the bottom-left half of the viewport. However, the viewport only covers the bottom-left quadrant of the window, ans to the triangle cover, on the screen, the bottom-left half of the bottom-left quadrant; that is, one eight of the total area of the window.

You probably want to set the viewport to cover the whole window. From there, you control the coordinate range using the MVP matrix. For example, if you set the MPV matrix to an orthographic matrix with the coordinate range [0, 800] along the X-axis and [0, 600] along the Y-axis, you will have a fullscreen viewport, and a visible coordinate range from (0,0) in one corner and (800, 600) in the diagonally opposite corner.

0

##### Share on other sites

thanks,but these ortho matrix ( i use glm with : m_MP = glm::ortho<GLfloat>( 0, 800, 0, 600, 1.0, -1.0 );)

i try

[code]ptrVerteBufferManager ptrMakeVBa(new CVertexBufferManager());

ptrMakeVBa->Position.m_pPosition->AddData(glm::vec3(0.0 , 600.0,  0.5));

ptrMakeVBa->Position.SetDynamics(GL_STATIC_DRAW);
ptrMakeVBa->Position.SetSemantics("VertexPosition");
ptrMakeVBa->Position.SetType(GL_FLOAT);
[/code]
but what i must insert in a vbo for draw an half of the entire screen with a triangle?
thanks.

0

##### Share on other sites

With that projection matrix, the visible coordinate range is from 0 to 800 along the X-axis, and from 0 to 600 along the Y-axis. The coordinates you have there are the correct ones.

0

##### Share on other sites

I can not understand, this is the matrix that comes to Shader, the MVP generated from this ortho function of glm:.

m_MP = glm::ortho<GLfloat>(0.0, 800.0, 0.0, 600.01 );

[code]{0.0024999999, 0, 0, 0}
{0, 0.0033332778, 0, 0}
{0, 0, -1, 0}
{-1, -1, 0, 1}[/code]

and i use a 800(width)* 600(height) coords, this is the vbo that comes to the gpu(i use gdebugger)

[code]0, 0, 0.5,
0, 600, 0.5,
800, 600, 0.5,
[/code]

if i use a -1 1 -1 1 all works fine .

where is my mistake?

0

##### Share on other sites

Perhaps you forgot to upload the projection matrix to the MVP uniform.

0

##### Share on other sites

no, i see with gdebugger that the mvp matrix is that that i post, in the gpu there is that matrix.
but i trying to multiply the 800 for the matrix and i see that the results go from 0 to 2 is correct?
They don't must  go from -1 to 1?
thanks.

0

##### Share on other sites

The matrix is correct; the vector (0, 0, z, 1) transforms to (-1, -1, -z, 1) and the vector (800, 600, z, 1) transforms to (1, 1, -z, 1). Thus, the coordinate range (0,0) to (800, 600) maps correctly to the range (-1,-1) to (1, 1).

0

##### Share on other sites

may be that the error is in 0.5 the z component?

i set 0.5 because i work in 2d and not in 3d:

[code]

1. 0, 0, 0.5,
2. 0, 600, 0.5,
3. 800, 600, 0.5,
[/code]

but with the matrix that i post ....

0

##### Share on other sites

Nothing wrong with the Z-component with regards to that matrix. But what is the problem now, really? I assume you have fixed what I have said above, so the error must be something else now. Show the current code so I know what you have fixed and how you have fixed it.

0

##### Share on other sites

I see a problem:

if i use a glViewport(0, 0, 1920, 1080); that is my full resolution screen all works fine, but if i use a 800 x 600 glViewport(0, 0, 800, 600); the triangle is an half of the correct rectangle that must occupy the half of the screen.
Then the error may be in the creation of the window?
this is my window's creation code:
[code]
HWND CreateAppWindow(const WNDCLASSEX &wcl, const char *pszTitle)
{
// Create a window that is centered on the desktop. It's exactly 1/4 the
// size of the desktop. Don't allow it to be resized.
int n = 0;
DWORD wndExStyle = WS_EX_OVERLAPPEDWINDOW;
DWORD wndStyle = WS_OVERLAPPED | WS_CAPTION | WS_SYSMENU |
WS_MINIMIZEBOX | WS_CLIPCHILDREN | WS_CLIPSIBLINGS;

HWND hWnd = CreateWindowEx
(wndExStyle, wcl.lpszClassName, "title",
wndStyle, 0, 0, 1920, 1080, 0, 0, wcl.hInstance, 0);

if (hWnd)
{
int screenWidth = GetSystemMetrics(SM_CXSCREEN);
int screenHeight = GetSystemMetrics(SM_CYSCREEN);
int halfScreenWidth = screenWidth / 2;
int halfScreenHeight = screenHeight / 2;
int left = (screenWidth - halfScreenWidth) / 2;
int top = (screenHeight - halfScreenHeight) / 2;
RECT rc = {0};

SetRect(&rc, left, top, left + halfScreenWidth, top + halfScreenHeight);
AdjustWindowRectEx(&rc, wndStyle, FALSE, wndExStyle);
MoveWindow(hWnd, rc.left, rc.top, rc.right - rc.left, rc.bottom - rc.top, TRUE);

GetClientRect(hWnd, &rc);
m_windowWidth = rc.right - rc.left;
m_windowHeight = rc.bottom - rc.top;
}

return hWnd;
};
[/code]

0

##### Share on other sites

also if i set this

HWND hWnd = CreateWindowEx
(wndExStyle, wcl.lpszClassName, "title",
wndStyle, 0, 0, 1920, 1080, 0, 0, wcl.hInstance, 0);

to

HWND hWnd = CreateWindowEx
(wndExStyle, wcl.lpszClassName, "title",
wndStyle, 0, 0, 800, 600, 0, 0, wcl.hInstance, 0);

if i set the viewport to 1920w 1080h all work fine.

what can be'

0

##### Share on other sites

As I said in my first post, your triangle is drawn in the viewport, not in the window. If you have a 1920x1080 window and set the viewport to the bottom-left 800x600 region, then the triangle will be drawn to that bottom-left 800x600 region of the whole 1920x1080 window. If you want the viewport to cover the whole window, then the viewport shall have the same size as the window.

0

##### Share on other sites

then the vbo points are related to the viewport, is correct?

If so

1)i can create a window of 400 x 400

2)set this vbo  :

-1, -1, 0,
-1, 1, 0,
1,1, 0,


3)set the ortho matrix with glm(m_MP = glm::ortho<GLfloat>(-1, 1, -1, 1); to

{1, 0, 0, 0}
{0, 1, 0, 0}
{0, 0, -1, 0}
{-0, -0, 0, 1}


4)all works fine.

but if:

1)ok,

2)set this vbo

0, 0, 0,
0,400,0
400,400,0


3)the ortho matrix sended to the shader as a mvp(now i change the name) is :

{0.0049999999, 0, 0, 0}
{0, 0.0049999999, 0, 0}
{0, 0, -1, 0}
{-1, -1, 0, 1}


but,i see nothing

this is all that i change , from the first to the second i change only the ortho projection and the vbo points from -1 1 to 0 400 ecc....

thanks again for your help, and sorry if i 'm a newbe

and the mview matrix is to use? i suppose that is identity .

by.

0

##### Share on other sites

Start with the case that works and slowly change the numbers towards the case that doesn't work. You will hopefully see where the triangle goes and why it doesn't show up.

0

## 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

Followers 0

• ### Similar Content

• Hello, I have been working on SH Irradiance map rendering, and I have been using a GLSL pixel shader to render SH irradiance to 2D irradiance maps for my static objects. I already have it working with 9 3D textures so far for the first 9 SH functions.
In my GLSL shader, I have to send in 9 SH Coefficient 3D Texures that use RGBA8 as a pixel format. RGB being used for the coefficients for red, green, and blue, and the A for checking if the voxel is in use (for the 3D texture solidification shader to prevent bleeding).
My problem is, I want to knock this number of textures down to something like 4 or 5. Getting even lower would be a godsend. This is because I eventually plan on adding more SH Coefficient 3D Textures for other parts of the game map (such as inside rooms, as opposed to the outside), to circumvent irradiance probe bleeding between rooms separated by walls. I don't want to reach the 32 texture limit too soon. Also, I figure that it would be a LOT faster.
Is there a way I could, say, store 2 sets of SH Coefficients for 2 SH functions inside a texture with RGBA16 pixels? If so, how would I extract them from inside GLSL? Let me know if you have any suggestions ^^.
• By DaniDesu
#include "MyEngine.h" int main() { MyEngine myEngine; myEngine.run(); return 0; } MyEngine.h
#pragma once #include "MyWindow.h" #include "MyShaders.h" #include "MyShapes.h" class MyEngine { private: GLFWwindow * myWindowHandle; MyWindow * myWindow; public: MyEngine(); ~MyEngine(); void run(); }; MyEngine.cpp
#pragma once #include <glad\glad.h> #include <GLFW\glfw3.h> class MyWindow { private: GLFWwindow * windowHandle; int windowWidth; int windowHeight; const char * windowTitle; public: MyWindow(int windowWidth, int windowHeight, const char * windowTitle); ~MyWindow(); GLFWwindow * getWindowHandle(); void createWindow(); void MyWindow::destroyWindow(); }; MyWindow.cpp
#include "MyWindow.h" MyWindow::MyWindow(int windowWidth, int windowHeight, const char * windowTitle) { this->windowHandle = NULL; this->windowWidth = windowWidth; this->windowWidth = windowWidth; this->windowHeight = windowHeight; this->windowTitle = windowTitle; glfwInit(); } MyWindow::~MyWindow() { } GLFWwindow * MyWindow::getWindowHandle() { return this->windowHandle; } void MyWindow::createWindow() { // Use OpenGL 3.3 and GLSL 3.3 glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 3); glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 3); // Limit backwards compatibility glfwWindowHint(GLFW_OPENGL_PROFILE, GLFW_OPENGL_CORE_PROFILE); glfwWindowHint(GLFW_OPENGL_FORWARD_COMPAT, GL_TRUE); // Prevent resizing window glfwWindowHint(GLFW_RESIZABLE, GL_FALSE); // Create window this->windowHandle = glfwCreateWindow(this->windowWidth, this->windowHeight, this->windowTitle, NULL, NULL); glfwMakeContextCurrent(this->windowHandle); } void MyWindow::destroyWindow() { glfwTerminate(); } MyShapes.h
#pragma once #include <glad\glad.h> #include <GLFW\glfw3.h> class MyShapes { public: MyShapes(); ~MyShapes(); GLuint & drawTriangle(float coordinates[]); }; MyShapes.cpp
#include "MyShapes.h" MyShapes::MyShapes() { } MyShapes::~MyShapes() { } GLuint & MyShapes::drawTriangle(float coordinates[]) { GLuint vertexBufferObject{}; GLuint vertexArrayObject{}; // Create a VAO glGenVertexArrays(1, &vertexArrayObject); glBindVertexArray(vertexArrayObject); // Send vertices to the GPU glGenBuffers(1, &vertexBufferObject); glBindBuffer(GL_ARRAY_BUFFER, vertexBufferObject); glBufferData(GL_ARRAY_BUFFER, sizeof(coordinates), coordinates, GL_STATIC_DRAW); // Dertermine the interpretation of the array buffer glVertexAttribPointer(0, 3, GL_FLOAT, GL_FALSE, 3*sizeof(float), (void *)0); glEnableVertexAttribArray(0); // Unbind the buffers glBindBuffer(GL_ARRAY_BUFFER, 0); glBindVertexArray(0); return vertexArrayObject; } MyFileHandler.h
#pragma once #include <cstdio> #include <cstdlib> class MyFileHandler { private: const char * fileName; unsigned long fileSize; void setFileSize(); public: MyFileHandler(const char * fileName); ~MyFileHandler(); unsigned long getFileSize(); const char * readFile(); }; MyFileHandler.cpp
#include "MyFileHandler.h" MyFileHandler::MyFileHandler(const char * fileName) { this->fileName = fileName; this->setFileSize(); } MyFileHandler::~MyFileHandler() { } void MyFileHandler::setFileSize() { FILE * fileHandle = NULL; fopen_s(&fileHandle, this->fileName, "rb"); fseek(fileHandle, 0L, SEEK_END); this->fileSize = ftell(fileHandle); rewind(fileHandle); fclose(fileHandle); return; } unsigned long MyFileHandler::getFileSize() { return (this->fileSize); } const char * MyFileHandler::readFile() { char * buffer = (char *)malloc((this->fileSize)+1); FILE * fileHandle = NULL; fopen_s(&fileHandle, this->fileName, "rb"); fread(buffer, this->fileSize, sizeof(char), fileHandle); fclose(fileHandle); buffer[this->fileSize] = '\0'; return buffer; } VertexShader.glsl
#version 330 core layout (location = 0) vec3 VertexPositions; void main() { gl_Position = vec4(VertexPositions, 1.0f); } FragmentShader.glsl
#version 330 core out vec4 FragmentColor; void main() { FragmentColor = vec4(1.0f, 0.0f, 0.0f, 1.0f); } I am attempting to create a simple engine/graphics utility using some object-oriented paradigms. My first goal is to get some output from my engine, namely, a simple red triangle.
For this goal, the MyShapes class will be responsible for defining shapes such as triangles, polygons etc. Currently, there is only a drawTriangle() method implemented, because I first wanted to see whether it works or not before attempting to code other shape drawing methods.
The constructor of the MyEngine class creates a GLFW window (GLAD is also initialized here to load all OpenGL functionality), and the myEngine.run() method in Main.cpp is responsible for firing up the engine. In this run() method, the shaders get loaded from files via the help of my FileHandler class. The vertices for the triangle are processed by the myShapes.drawTriangle() method where a vertex array object, a vertex buffer object and vertrex attributes are set for this purpose.
The while loop in the run() method should be outputting me the desired red triangle, but all I get is a grey window area. Why?
Note: The shaders are compiling and linking without any errors.
(Note: I am aware that this code is not using any good software engineering practices (e.g. exceptions, error handling). I am planning to implement them later, once I get the hang of OpenGL.)

• By KarimIO
EDIT: I thought this was restricted to Attribute-Created GL contexts, but it isn't, so I rewrote the post.
Hey guys, whenever I call SwapBuffers(hDC), I get a crash, and I get a "Too many posts were made to a semaphore." from Windows as I call SwapBuffers. What could be the cause of this?
Update: No crash occurs if I don't draw, just clear and swap.
static PIXELFORMATDESCRIPTOR pfd = // pfd Tells Windows How We Want Things To Be { sizeof(PIXELFORMATDESCRIPTOR), // Size Of This Pixel Format Descriptor 1, // Version Number PFD_DRAW_TO_WINDOW | // Format Must Support Window PFD_SUPPORT_OPENGL | // Format Must Support OpenGL PFD_DOUBLEBUFFER, // Must Support Double Buffering PFD_TYPE_RGBA, // Request An RGBA Format 32, // Select Our Color Depth 0, 0, 0, 0, 0, 0, // Color Bits Ignored 0, // No Alpha Buffer 0, // Shift Bit Ignored 0, // No Accumulation Buffer 0, 0, 0, 0, // Accumulation Bits Ignored 24, // 24Bit Z-Buffer (Depth Buffer) 0, // No Stencil Buffer 0, // No Auxiliary Buffer PFD_MAIN_PLANE, // Main Drawing Layer 0, // Reserved 0, 0, 0 // Layer Masks Ignored }; if (!(hDC = GetDC(windowHandle))) return false; unsigned int PixelFormat; if (!(PixelFormat = ChoosePixelFormat(hDC, &pfd))) return false; if (!SetPixelFormat(hDC, PixelFormat, &pfd)) return false; hRC = wglCreateContext(hDC); if (!hRC) { std::cout << "wglCreateContext Failed!\n"; return false; } if (wglMakeCurrent(hDC, hRC) == NULL) { std::cout << "Make Context Current Second Failed!\n"; return false; } ... // OGL Buffer Initialization glClear(GL_DEPTH_BUFFER_BIT | GL_COLOR_BUFFER_BIT); glBindVertexArray(vao); glUseProgram(myprogram); glDrawElements(GL_TRIANGLES, indexCount, GL_UNSIGNED_SHORT, (void *)indexStart); SwapBuffers(GetDC(window_handle));
• By Tchom
Hey devs!

I've been working on a OpenGL ES 2.0 android engine and I have begun implementing some simple (point) lighting. I had something fairly simple working, so I tried to get fancy and added color-tinting light. And it works great... with only one or two lights. Any more than that, the application drops about 15 frames per light added (my ideal is at least 4 or 5). I know implementing lighting is expensive, I just didn't think it was that expensive. I'm fairly new to the world of OpenGL and GLSL, so there is a good chance I've written some crappy shader code. If anyone had any feedback or tips on how I can optimize this code, please let me know.

uniform mat4 u_MVPMatrix; uniform mat4 u_MVMatrix; attribute vec4 a_Position; attribute vec3 a_Normal; attribute vec2 a_TexCoordinate; varying vec3 v_Position; varying vec3 v_Normal; varying vec2 v_TexCoordinate; void main() { v_Position = vec3(u_MVMatrix * a_Position); v_TexCoordinate = a_TexCoordinate; v_Normal = vec3(u_MVMatrix * vec4(a_Normal, 0.0)); gl_Position = u_MVPMatrix * a_Position; } Fragment Shader
precision mediump float; uniform vec4 u_LightPos["+numLights+"]; uniform vec4 u_LightColours["+numLights+"]; uniform float u_LightPower["+numLights+"]; uniform sampler2D u_Texture; varying vec3 v_Position; varying vec3 v_Normal; varying vec2 v_TexCoordinate; void main() { gl_FragColor = (texture2D(u_Texture, v_TexCoordinate)); float diffuse = 0.0; vec4 colourSum = vec4(1.0); for (int i = 0; i < "+numLights+"; i++) { vec3 toPointLight = vec3(u_LightPos[i]); float distance = length(toPointLight - v_Position); vec3 lightVector = normalize(toPointLight - v_Position); float diffuseDiff = 0.0; // The diffuse difference contributed from current light diffuseDiff = max(dot(v_Normal, lightVector), 0.0); diffuseDiff = diffuseDiff * (1.0 / (1.0 + ((1.0-u_LightPower[i])* distance * distance))); //Determine attenuatio diffuse += diffuseDiff; gl_FragColor.rgb *= vec3(1.0) / ((vec3(1.0) + ((vec3(1.0) - vec3(u_LightColours[i]))*diffuseDiff))); //The expensive part } diffuse += 0.1; //Add ambient light gl_FragColor.rgb *= diffuse; } Am I making any rookie mistakes? Or am I just being unrealistic about what I can do? Thanks in advance
• By yahiko00
Hi,
Not sure to post at the right place, if not, please forgive me...
For a game project I am working on, I would like to implement a 2D starfield as a background.
I do not want to deal with static tiles, since I plan to slowly animate the starfield. So, I am trying to figure out how to generate a random starfield for the entire map.
I feel that using a uniform distribution for the stars will not do the trick. Instead I would like something similar to the screenshot below, taken from the game Star Wars: Empire At War (all credits to Lucasfilm, Disney, and so on...).

Is there someone who could have an idea of a distribution which could result in such a starfield?
Any insight would be appreciated

• 28
• 13
• 11
• 31
• 20