## Recommended Posts

Hi, I'd like to know which of the following methods is faster in OpenGL when it comes to loading/resetting the modelview and projection matrices: - to load the matrix by using glLoadMatrixf - to rely on a set of glPushMatrix/glPopMatrix calls At the moment I am using a combination of the two, but I tend to self-convince myself that glLoadMatrixf should be faster. Which is the fastest method in your personal experience?

##### Share on other sites
i would think that push/pop is faster

since loadmatrix would result in sending the matrix to the gpu, while push/pop tells the gpu with a command what to do..

i dont know if this is true, but it should be correct

##### Share on other sites
If the GPU supports a matrix stack on board, then glPush and pop will be faster but I doubt that any of them do.

Also, don't worry about it. Don't optimize too early.
If you have the matrix ready, just use glLoadMatrix. It's only 16 floats that will be sent.

##### Share on other sites
GPUs don't have hardware matrix stacks. The current matrices are pushed down to the card when you make a draw call, along with other relevant state.

LoadMatrix is essentially a memory copy. PushMatrix is essentially a pointer increment and a memory copy. (I don't know if drivers implement some kind of adaptive growth strategy, but even if they do, the costs will get amortized quickly.) Either way, it doesn't matter at all. Don't concern yourself with such trivial nonsense.

##### Share on other sites
I was thinking that maybe OpenGL does some sort of 'state init' processing whenever a modelview or projection matrix is loaded and that maybe pushing/popping simply pushed/popped that 'state' making it the fastest method of the two.

But I'm glad I was overcomplicating this issue and that there are no performance issues involved!

Thanks to all for the invaluable input given.

## Create an account

Register a new account

• ## Partner Spotlight

• ### Forum Statistics

• Total Topics
627681
• Total Posts
2978611
• ### Similar Content

• Both functions are available since 3.0, and I'm currently using glMapBuffer(), which works fine.
But, I was wondering if anyone has experienced advantage in using glMapBufferRange(), which allows to specify the range of the mapped buffer. Could this be only a safety measure or does it improve performance?
Note: I'm not asking about glBufferSubData()/glBufferData. Those two are irrelevant in this case.
• 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.
• 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.

References:
Code: https://pastebin.com/Hcshj3FQ
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?

• 13
• 12
• 10
• 12
• 22