• 11
• 9
• 10
• 9
• 11
• ### Similar Content

• By tj8146
I am using immediate mode for OpenGL and I am creating a 2D top down car game. I am trying to configure my game loop in order to get my car-like physics working on a square shape. I have working code but it is not doing as I want it to. I am not sure as to whether it is my game loop that is incorrect or my code for the square is incorrect, or maybe both! Could someone help because I have been trying to work this out for over a day now
I have attached my .cpp file if you wish to run it for yourself..
WinMain code:
/******************* WIN32 FUNCTIONS ***************************/ int WINAPI WinMain( HINSTANCE hInstance, // Instance HINSTANCE hPrevInstance, // Previous Instance LPSTR lpCmdLine, // Command Line Parameters int nCmdShow) // Window Show State { MSG msg; // Windows Message Structure bool done=false; // Bool Variable To Exit Loop Car car; car.x = 220; car.y = 140; car.dx = 0; car.dy = 0; car.ang = 0; AllocConsole(); FILE *stream; freopen_s(&stream, "CONOUT$", "w", stdout); // Create Our OpenGL Window if (!CreateGLWindow("OpenGL Win32 Example",screenWidth,screenHeight)) { return 0; // Quit If Window Was Not Created } while(!done) // Loop That Runs While done=FALSE { if (PeekMessage(&msg,NULL,0,0,PM_REMOVE)) // Is There A Message Waiting? { if (msg.message==WM_QUIT) // Have We Received A Quit Message? { done=true; // If So done=TRUE break; } else // If Not, Deal With Window Messages { TranslateMessage(&msg); // Translate The Message DispatchMessage(&msg); // Dispatch The Message } } else // If There Are No Messages { if(keys[VK_ESCAPE]) done = true; void processKeys(Car& car); //process keyboard while (game_is_running) { loops = 0; while (GetTickCount() > next_game_tick && loops < MAX_FRAMESKIP) { update(car); // update variables next_game_tick += SKIP_TICKS; loops++; } display(car); // Draw The Scene SwapBuffers(hDC); // Swap Buffers (Double Buffering) } } } // Shutdown KillGLWindow(); // Kill The Window return (int)(msg.wParam); // Exit The Program } //WIN32 Processes function - useful for responding to user inputs or other events. LRESULT CALLBACK WndProc( HWND hWnd, // Handle For This Window UINT uMsg, // Message For This Window WPARAM wParam, // Additional Message Information LPARAM lParam) // Additional Message Information { switch (uMsg) // Check For Windows Messages { case WM_CLOSE: // Did We Receive A Close Message? { PostQuitMessage(0); // Send A Quit Message return 0; // Jump Back } break; case WM_SIZE: // Resize The OpenGL Window { reshape(LOWORD(lParam),HIWORD(lParam)); // LoWord=Width, HiWord=Height return 0; // Jump Back } break; case WM_LBUTTONDOWN: { mouse_x = LOWORD(lParam); mouse_y = screenHeight - HIWORD(lParam); LeftPressed = true; } break; case WM_LBUTTONUP: { LeftPressed = false; } break; case WM_MOUSEMOVE: { mouse_x = LOWORD(lParam); mouse_y = screenHeight - HIWORD(lParam); } break; case WM_KEYDOWN: // Is A Key Being Held Down? { keys[wParam] = true; // If So, Mark It As TRUE return 0; // Jump Back } break; case WM_KEYUP: // Has A Key Been Released? { keys[wParam] = false; // If So, Mark It As FALSE return 0; // Jump Back } break; } // Pass All Unhandled Messages To DefWindowProc return DefWindowProc(hWnd,uMsg,wParam,lParam); } C++ and OpenGL code: int mouse_x=0, mouse_y=0; bool LeftPressed = false; int screenWidth=1080, screenHeight=960; bool keys[256]; float radiansFromDegrees(float deg) { return deg * (M_PI / 180.0f); } float degreesFromRadians(float rad) { return rad / (M_PI / 180.0f); } bool game_is_running = true; const int TICKS_PER_SECOND = 50; const int SKIP_TICKS = 1000 / TICKS_PER_SECOND; const int MAX_FRAMESKIP = 10; DWORD next_game_tick = GetTickCount(); int loops; typedef struct { float x, y; float dx, dy; float ang; }Car; //OPENGL FUNCTION PROTOTYPES void display(const Car& car); //called in winmain to draw everything to the screen void reshape(int width, int height); //called when the window is resized void init(); //called in winmain when the program starts. void processKeys(Car& car); //called in winmain to process keyboard input void update(Car& car); //called in winmain to update variables /************* START OF OPENGL FUNCTIONS ****************/ void display(const Car& car) { const float w = 50.0f; const float h = 50.0f; glClear(GL_COLOR_BUFFER_BIT); glLoadIdentity(); glTranslatef(100, 100, 0); glBegin(GL_POLYGON); glVertex2f(car.x, car.y); glVertex2f(car.x + w, car.y); glVertex2f(car.x + w, car.y + h); glVertex2f(car.x, car.y + h); glEnd(); glFlush(); } void reshape(int width, int height) // Resize the OpenGL window { screenWidth = width; screenHeight = height; // to ensure the mouse coordinates match // we will use these values to set the coordinate system glViewport(0, 0, width, height); // Reset the current viewport glMatrixMode(GL_PROJECTION); // select the projection matrix stack glLoadIdentity(); // reset the top of the projection matrix to an identity matrix gluOrtho2D(0, screenWidth, 0, screenHeight); // set the coordinate system for the window glMatrixMode(GL_MODELVIEW); // Select the modelview matrix stack glLoadIdentity(); // Reset the top of the modelview matrix to an identity matrix } void init() { glClearColor(1.0, 1.0, 0.0, 0.0); //sets the clear colour to yellow //glClear(GL_COLOR_BUFFER_BIT) in the display function //will clear the buffer to this colour. } void processKeys(Car& car) { if (keys[VK_UP]) { float cdx = sinf(radiansFromDegrees(car.ang)); float cdy = -cosf(radiansFromDegrees(car.ang)); car.dx += cdx; car.dy += cdy; } if (keys[VK_DOWN]) { float cdx = sinf(radiansFromDegrees(car.ang)); float cdy = -cosf(radiansFromDegrees(car.ang)); car.dx += -cdx; car.dy += -cdy; } if (keys[VK_LEFT]) { car.ang -= 2; } if (keys[VK_RIGHT]) { car.ang += 2; } } void update(Car& car) { car.x += car.dx*next_game_tick; } game.cpp • By tj8146 I am using immediate mode for OpenGL and I am creating a 2D top down car game. I am trying to configure my game loop in order to get my car-like physics working on a square shape. I have working code but it is not doing as I want it to. I am not sure as to whether it is my game loop that is incorrect or my code for the square is incorrect, or maybe both! Could someone help because I have been trying to work this out for over a day now I have attached my .cpp file if you wish to run it for yourself.. This is my C++ and OpenGL code: int mouse_x=0, mouse_y=0; bool LeftPressed = false; int screenWidth=1080, screenHeight=960; bool keys[256]; float radiansFromDegrees(float deg) { return deg * (M_PI / 180.0f); } float degreesFromRadians(float rad) { return rad / (M_PI / 180.0f); } bool game_is_running = true; const int TICKS_PER_SECOND = 50; const int SKIP_TICKS = 1000 / TICKS_PER_SECOND; const int MAX_FRAMESKIP = 10; DWORD next_game_tick = GetTickCount(); int loops; typedef struct { float x, y; float dx, dy; float ang; }Car; //OPENGL FUNCTION PROTOTYPES void display(const Car& car); //called in winmain to draw everything to the screen void reshape(int width, int height); //called when the window is resized void init(); //called in winmain when the program starts. void processKeys(Car& car); //called in winmain to process keyboard input void update(Car& car); //called in winmain to update variables /************* START OF OPENGL FUNCTIONS ****************/ void display(const Car& car) { const float w = 50.0f; const float h = 50.0f; glClear(GL_COLOR_BUFFER_BIT); glLoadIdentity(); glTranslatef(100, 100, 0); glBegin(GL_POLYGON); glVertex2f(car.x, car.y); glVertex2f(car.x + w, car.y); glVertex2f(car.x + w, car.y + h); glVertex2f(car.x, car.y + h); glEnd(); glFlush(); } void reshape(int width, int height) // Resize the OpenGL window { screenWidth = width; screenHeight = height; // to ensure the mouse coordinates match // we will use these values to set the coordinate system glViewport(0, 0, width, height); // Reset the current viewport glMatrixMode(GL_PROJECTION); // select the projection matrix stack glLoadIdentity(); // reset the top of the projection matrix to an identity matrix gluOrtho2D(0, screenWidth, 0, screenHeight); // set the coordinate system for the window glMatrixMode(GL_MODELVIEW); // Select the modelview matrix stack glLoadIdentity(); // Reset the top of the modelview matrix to an identity matrix } void init() { glClearColor(1.0, 1.0, 0.0, 0.0); //sets the clear colour to yellow //glClear(GL_COLOR_BUFFER_BIT) in the display function //will clear the buffer to this colour. } void processKeys(Car& car) { if (keys[VK_UP]) { float cdx = sinf(radiansFromDegrees(car.ang)); float cdy = -cosf(radiansFromDegrees(car.ang)); car.dx += cdx; car.dy += cdy; } if (keys[VK_DOWN]) { float cdx = sinf(radiansFromDegrees(car.ang)); float cdy = -cosf(radiansFromDegrees(car.ang)); car.dx += -cdx; car.dy += -cdy; } if (keys[VK_LEFT]) { car.ang -= 2; } if (keys[VK_RIGHT]) { car.ang += 2; } } void update(Car& car) { car.x += car.dx*next_game_tick; } My WinMain code: /******************* WIN32 FUNCTIONS ***************************/ int WINAPI WinMain( HINSTANCE hInstance, // Instance HINSTANCE hPrevInstance, // Previous Instance LPSTR lpCmdLine, // Command Line Parameters int nCmdShow) // Window Show State { MSG msg; // Windows Message Structure bool done=false; // Bool Variable To Exit Loop Car car; car.x = 220; car.y = 140; car.dx = 0; car.dy = 0; car.ang = 0; AllocConsole(); FILE *stream; freopen_s(&stream, "CONOUT$", "w", stdout); // Create Our OpenGL Window if (!CreateGLWindow("OpenGL Win32 Example",screenWidth,screenHeight)) { return 0; // Quit If Window Was Not Created } while(!done) // Loop That Runs While done=FALSE { if (PeekMessage(&msg,NULL,0,0,PM_REMOVE)) // Is There A Message Waiting? { if (msg.message==WM_QUIT) // Have We Received A Quit Message? { done=true; // If So done=TRUE break; } else // If Not, Deal With Window Messages { TranslateMessage(&msg); // Translate The Message DispatchMessage(&msg); // Dispatch The Message } } else // If There Are No Messages { if(keys[VK_ESCAPE]) done = true; void processKeys(Car& car); //process keyboard while (game_is_running) { loops = 0; while (GetTickCount() > next_game_tick && loops < MAX_FRAMESKIP) { update(car); // update variables next_game_tick += SKIP_TICKS; loops++; } display(car); // Draw The Scene SwapBuffers(hDC); // Swap Buffers (Double Buffering) } } } // Shutdown KillGLWindow(); // Kill The Window return (int)(msg.wParam); // Exit The Program } //WIN32 Processes function - useful for responding to user inputs or other events. LRESULT CALLBACK WndProc( HWND hWnd, // Handle For This Window UINT uMsg, // Message For This Window WPARAM wParam, // Additional Message Information LPARAM lParam) // Additional Message Information { switch (uMsg) // Check For Windows Messages { case WM_CLOSE: // Did We Receive A Close Message? { PostQuitMessage(0); // Send A Quit Message return 0; // Jump Back } break; case WM_SIZE: // Resize The OpenGL Window { reshape(LOWORD(lParam),HIWORD(lParam)); // LoWord=Width, HiWord=Height return 0; // Jump Back } break; case WM_LBUTTONDOWN: { mouse_x = LOWORD(lParam); mouse_y = screenHeight - HIWORD(lParam); LeftPressed = true; } break; case WM_LBUTTONUP: { LeftPressed = false; } break; case WM_MOUSEMOVE: { mouse_x = LOWORD(lParam); mouse_y = screenHeight - HIWORD(lParam); } break; case WM_KEYDOWN: // Is A Key Being Held Down? { keys[wParam] = true; // If So, Mark It As TRUE return 0; // Jump Back } break; case WM_KEYUP: // Has A Key Been Released? { keys[wParam] = false; // If So, Mark It As FALSE return 0; // Jump Back } break; } // Pass All Unhandled Messages To DefWindowProc return DefWindowProc(hWnd,uMsg,wParam,lParam); }
game.cpp
• By lxjk
Hi guys,
There are many ways to do light culling in tile-based shading. I've been playing with this idea for a while, and just want to throw it out there.
Because tile frustums are general small compared to light radius, I tried using cone test to reduce false positives introduced by commonly used sphere-frustum test.
On top of that, I use distance to camera rather than depth for near/far test (aka. sliced by spheres).
This method can be naturally extended to clustered light culling as well.
The following image shows the general ideas

Performance-wise I get around 15% improvement over sphere-frustum test. You can also see how a single light performs as the following: from left to right (1) standard rendering of a point light; then tiles passed the test of (2) sphere-frustum test; (3) cone test; (4) spherical-sliced cone test

I put the details in my blog post (https://lxjk.github.io/2018/03/25/Improve-Tile-based-Light-Culling-with-Spherical-sliced-Cone.html), GLSL source code included!

Eric

• Good evening everyone!

I was wondering if there is something equivalent of  GL_NV_blend_equation_advanced for AMD?
Basically I'm trying to find more compatible version of it.

Thank you!

• Hello guys,

How do I know? Why does wavefront not show for me?
I already checked I have non errors yet.

And my download (mega.nz) should it is original but I tried no success...
- Add blend source and png file here I have tried tried,.....

PS: Why is our community not active? I wait very longer. Stop to lie me!
Thanks !

# OpenGL Matrices and the pipeline

This topic is 4714 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

## Recommended Posts

Hi, Well I'm after making some decent progress since I first took up learning OpenGL a few months ago. I can now use vertex arrays, vertex buffer objects, indexed geometry, texture mapping, fog, mipmapping, vertex/pixel shaders etc. etc.. However I feel as if I've skipped some of the basics, which I should really know inside out at this stage... My first question relates to the two matrices: the 'modelview' matrix and 'projection matrix'. In my 3D engine I only use the projection matrix to translate and rotate the map and all the game objects. This works fine, however I am unsure as why there is a second matrix (modelview) and what its purpose is. I have looked for some good explanations on the differences between the two matrices, but couldn't find anything decent to help explain them. So why do we need two transformation matrices ? What typical scenarios would you use each of the two matrices? Is the modelview matrix a transformation matrix used for transformations local to each object in a game (eg: monster / map item) and the projection matrix used for transforming the world (entire map geometry) ? Or is the modelview matrix simply an additional matrix which can recalled and used if needed ? Why use it? The second question regards the pipeline and viewing transforms. When I render each frame I first setup the projection matrix / rotations etc and then draw the map. I then push this matrix to save its status. The matrix is then transformed again by whatever position/rotation that each monster has, and the monster is then drawn. After drawing each monster I then pop the matrix to reload the previously saved state. Now.. If i remove the pop matrix line the entire world gets translated by whatever I translate the monster by. This brings me to some alarming conclusions.. When I am translating the monster, am I really translating everything else too? I thought once something was sent down the pipeline it stays in whatever position it was when it was first sent? Does this mean everytime I move a monster a whole bunch of unnecessary calculations are being peformed on the rest of the map? If so, how can I avoid such calculations? Thanks in advance for your help. I know this post is a bit of a pain [smile] but these are things I really need to get clear in my head before I go any further.

##### Share on other sites
Hi,

Whether you know it or not, you are using the modelview matrix. Search through your code - somewhere I'm sure you'll find the line glMatrixMode(GL_MODELVIEW).

Ok, so on to what the two matrices do. The modelview matrix performs an affine transformation; more practically, it sets the position and orientation of your camera and of objects in the scene in 3d space, and applies other linear transformations such as scale, reflection, and shear.

The projection matrix performs a different function: it converts the 3d world into 2d information that can be displayed on the screen. Variables include field of view, aspect ratio, and near and far clipping planes.

I'm not exactly sure how OpenGL implements this internally, but in any case you don't have to worry about doing 'too much transformation'. That's why matrix concatenation is useful; no matter how many transformations you combine, it still comes down to a single matrix-vector multiplication per vertex.

##### Share on other sites
projection matirx for the frustum and ortho things.
modelview matrix for translating/rotatting/scaling for the objects
texture matrix same as modelview matrix but for the textures GL_TEXTURE_1D/2D/3D
for more details read the red book

##### Share on other sites
mmm i am not sure about your second question but every push you should pop it or you'll face problem, because the matrix stack has a limit and every loop in your main function you'll push till it gets full .
bye

##### Share on other sites
Ah yes- now it makes more sense.. I can see the relationship between the two more clearly now. Good reply..

Quote:
 Original post by jykWhether you know it or not, you are using the modelview matrix. Search through your code - somewhere I'm sure you'll find the line glMatrixMode(GL_MODELVIEW).

Nope. All throughout my code the matrix used is GL_PROJECTION - even in my vertex shaders. I can see how it can be used to achieve the same effect though, since ultimately it controls how points are projected from world space onto the screen.

Ok, so that's one issue cleared up I think. Any more ideas on the other question?

##### Share on other sites
The answer to the second question is that, for rigid meshes, every vertex is transformed exactly once, with whatever matrix was loaded at the time the draw function is called. Basically, when you call glBegin() the driver makes a copy of the matrix at the top of the stack and sends that along with the vertices you specify, and whatever happens afterwards it preserves the illusion that the vertices are completely transformed & rendered with the current GL state before you go and muck with it.

So, the transformations are just numerical manipulations on the matrix only, and don't actually *move* anything until you draw something. It looks like a little crash-course in linear algebra would help you out a lot in understanding these concepts.

Tom

##### Share on other sites
Also, it is perfectly plausible to use the projection matrix only, as the two matrices are always concatenated prior to transformation. They are only separate because it can be handy to manipulate one and not the other. For instance:

You have a Projection matrix with the following transforms:
1. Frustum transform
2. Viewing (camera) transform

And a Model matrix with the following transforms:
3. World transform
4. Model transform
5. Sub-model transform (objects moving relative to parent objects, etc)

This is more or less the same as one Projection matrix with transforms 1-5, but say you wanted to draw mountains twice, once regularly and once reflected in water. To do the reflection, you want to flip the camera.

If you're using one matrix, you need to pop 5, 4, 3, and 2, specify a new camera transform, and then specify 3-5 again.

If you're using two matrices, you just pop 2 off the Projection and specify your new camera, and the Model matrix stays the same.

Tom

##### Share on other sites
Quote:
 Original post by ParadigmShiftThe answer to the second question is that, for rigid meshes, every vertex is transformed exactly once, with whatever matrix was loaded at the time the draw function is called. Basically, when you call glBegin() the driver makes a copy of the matrix at the top of the stack and sends that along with the vertices you specify, and whatever happens afterwards it preserves the illusion that the vertices are completely transformed & rendered with the current GL state before you go and muck with it.

Excellent. That was just what I needed to know.. At least I can be sure now that everything is being transformed once, and once only.

Quote:
 Original post by ParadigmShiftSo, the transformations are just numerical manipulations on the matrix only, and don't actually *move* anything until you draw something. It looks like a little crash-course in linear algebra would help you out a lot in understanding these concepts.Tom

I do a lot of stuff on algebra and matrices in college- just had my final year maths exam today in fact! [smile] Its not that I don't understand the maths involved in the rotations, I'm just unsure exactly what the hell OpenGL / display drivers are doing underneath the API to my geometry. However, you're post has helped clear that up so I am thankful for that.

Well thats great guys, I feel much more enlightened now! [wink] You have been most helpful so I think extra ratings are in order.

Cheers
-Darragh

##### Share on other sites
Hm, guess I was wrong about having to use the modelview matrix :-| However, see here (section 8.030) and here for discussion of the way OpenGL intends for the matrices to be used and the reasons for following these guidelines.

##### Share on other sites
Thanks for that. Those two articles are very informative- i'll keep them for future reference.

You've also managed to solve another long outstanding problem i had...

In the article about 'GL_PROJECTION' abuse (of which I am guilty [smile]), it also mentions the problems of using the projection matrix with fog. Now cast you're eye back to the thread which I started on that very subject.. I was unable to solve the problem (until now) and subsequently had to resort to learning GLSL and using pixel shaders in order to do my fogging. If only I had known about this back then!... [smile]