• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
giugio

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:
vshader:
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 this post


Link to post
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 this post


Link to post
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, 0.0, 0.5));
    ptrMakeVBa->Position.m_pPosition->AddData(glm::vec3(0.0 , 600.0,  0.5));
    ptrMakeVBa->Position.m_pPosition->AddData(glm::vec3(800.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 this post


Link to post
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 this post


Link to post
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 this post


Link to post
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 this post


Link to post
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 this post


Link to post
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 this post


Link to post
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 this post


Link to post
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 this post


Link to post
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 this post


Link to post
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 this post


Link to post
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 this post


Link to post
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

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  
Followers 0

  • Similar Content

    • By fllwr0491
      I googled around but are unable to find source code or details of implementation.
      What keywords should I search for this topic?
      Things I would like to know:
      A. How to ensure that partially covered pixels are rasterized?
         Apparently by expanding each triangle by 1 pixel or so, rasterization problem is almost solved.
         But it will result in an unindexable triangle list without tons of overlaps. Will it incur a large performance penalty?
      B. A-buffer like bitmask needs a read-modiry-write operation.
         How to ensure proper synchronizations in GLSL?
         GLSL seems to only allow int32 atomics on image.
      C. Is there some simple ways to estimate coverage on-the-fly?
         In case I am to draw 2D shapes onto an exisitng target:
         1. A multi-pass whatever-buffer seems overkill.
         2. Multisampling could cost a lot memory though all I need is better coverage.
            Besides, I have to blit twice, if draw target is not multisampled.
       
    • By mapra99
      Hello

      I am working on a recent project and I have been learning how to code in C# using OpenGL libraries for some graphics. I have achieved some quite interesting things using TAO Framework writing in Console Applications, creating a GLUT Window. But my problem now is that I need to incorporate the Graphics in a Windows Form so I can relate the objects that I render with some .NET Controls.

      To deal with this problem, I have seen in some forums that it's better to use OpenTK instead of TAO Framework, so I can use the glControl that OpenTK libraries offer. However, I haven't found complete articles, tutorials or source codes that help using the glControl or that may insert me into de OpenTK functions. Would somebody please share in this forum some links or files where I can find good documentation about this topic? Or may I use another library different of OpenTK?

      Thanks!
    • By Solid_Spy
      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 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.
       
      Vertex Shader
      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
  • Popular Now