# OpenGL The most efficient way of loading alot of bitmaps into memory?

## Recommended Posts

This is how i currently load my 2d textures. As i am rather new to the OpenGL api, this seems as a pretty straightforward approach, but it also seems terribly inefficient, as it takes several seconds to load all my bitmaps.
[source langg = "cpp"]
{
int status = FALSE;
AUX_RGBImageRec* TextureImage[textures];

for(int i = 0; i < textures; i++)
{
memset(TextureImage,0,sizeof(void *)*textures);
switch(i)
{
// load the appropriate image into the Tex. image array.
}
status = TRUE;
glGenTextures(1,&texture[i]);

glBindTexture(GL_TEXTURE_2D, texture[i]);

glTexParameteri(GL_TEXTURE_2D,GL_TEXTURE_MAG_FILTER,GL_LINEAR);
glTexParameteri(GL_TEXTURE_2D,GL_TEXTURE_MIN_FILTER,GL_LINEAR_MIPMAP_NEAREST);
gluBuild2DMipmaps(GL_TEXTURE_2D, 3, TextureImage[i]->sizeX, TextureImage[i]->sizeY, GL_RGB, GL_UNSIGNED_BYTE, TextureImage[i]->data);

if (TextureImage[i])									// If Texture Exists
{
if (TextureImage[i]->data)							// If Texture Image Exists
{
free(TextureImage[i]->data);					// Free The Texture Image Memory
}

free(TextureImage[i]);								// Free The Image Structure
}
}//for loop



##### Share on other sites
It would be useful to see how you are actually loading the bitmap data from the file, but the OpenGL code you are using is how it should be.

##### Share on other sites
I couldn't help but notice the following in your code.

AUX_RGBImageRec* TextureImage[textures];memset(TextureImage,0,sizeof(void *)*textures);

Given the usage, it seems quite obvious that your intent was to set all the pointers in the array to the null pointer value. Of course, this is not what your code does. Your code changes the binary representation of all the pointers in the array to the binary representation of the integer zero, which may or may not be the same as that of the null pointer value.

In short, you are setting the pointers in the TextureImage array to a certain value, and then hoping that the value which you used also happens to be the null pointer value:
// Set pointers to a value which I hope is "null"memset(TextureImage,0,sizeof(void*)*textures);

A shorter version, which also happens to do what you intended, is:
AUX_RGBImageRec* TextureImage[textures] = {};

##### Share on other sites
I assume you use the glaux library since there is a AUX_RGBImageRec in your code. I suggest to dump this library since it is deprecated. There are other image loading libraries with which you can load OpenGL textures. I for instance use SDL_image, convert the loaded bitmap to the appropriate OpenGL format and upload it. There is also DevIL and probably many others.

Using such image loading libraries may still not the most optimal way to load the images since you first have to convert them to the right type and bpp.

The most optimal way appart from not loading the images at all is to lay out the data in exactly the same way the API expects it and store this in a file. This means there will not be any parsing/conversion required on load. There might be endianness issues though.

And another good idea it to combine the above with compressed textures, as they are smaller and can thus be loaded faster. They are also faster when rendering.

##### Share on other sites
Quote:
 Original post by TrenkiAnd another good idea it to combine the above with compressed textures, as they are smaller and can thus be loaded faster. They are also faster when rendering.

I'm pretty sure that this is untrue. If anything, compressed textures will take longer to load, as the data will need to be uncompressed before they are loaded into memory. They also won't be rendered any faster, as the data is always stored the same way in memory, regardless of how they are stored on disk.

Unfortunately, there's not a whole lot you can do to vastly increase the speed of loading files. However, here are a few suggestions:

- Do you have lots of very small images? The cost of opening and closing each file, especially when there's very little to read, can quickly add up. Putting all of the image data into fewer files, and then only using what you need when you need it (say, by using glTexCoord) can reduce this cost.

- Do you really need all of your images immediately? Its unlikely, considering how long it takes so long to load them all. It would probably be better to just load them when they are needed. Unless you need to load in a *very* large image, or need to load in many images, taking the hit while the program is running through the main loop probably isn't going to hurt you much. It'll happen pretty rarely, so its usually not a problem.

##### Share on other sites
1) Textures can be compressed using hardware supported compression (ie DTX, etc). These don't need to be decompressed and are smaller/faster to load.

2) General compression (ie zlib) can help load times if file IO is a bottleneck. Profile your file loading times vs smaller file+decompression. Heavy compression will definitely take longer, but you can get a nice size reduction with relatively minimal compression which can be a win as file IO is all sorts of slow.

##### Share on other sites
Quote:
Original post by derickdong
Quote:
 Original post by TrenkiAnd another good idea it to combine the above with compressed textures, as they are smaller and can thus be loaded faster. They are also faster when rendering.

I'm pretty sure that this is untrue. If anything, compressed textures will take longer to load, as the data will need to be uncompressed before they are loaded into memory. They also won't be rendered any faster, as the data is always stored the same way in memory, regardless of how they are stored on disk.

You are wrong on this one. Compressed textures (with DXT or other compression formats) take up less space on disk and you can upload them with the glCompressedTexImage commands. They will NOT get expanded internally so they will use less texture memory as well. Compressed textures are a hardware feature and will be faster since less data has to be read from the texture memory to generate pixel colors.

I mean, when compressed textures would get expanded to normal textures internally then there would not be any point to have them in the first place.

## Create an account

Register a new account

• ## Partner Spotlight

• ### Forum Statistics

• Total Topics
627642
• Total Posts
2978354
• ### Similar Content

• 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?

• Hello all,

On my Windows 7 x64 machine I wrote the code below on VS 2017 and ran it.
#include <glad/glad.h>  #include <GLFW/glfw3.h> #include <std_lib_facilities_4.h> using namespace std; void framebuffer_size_callback(GLFWwindow* window , int width, int height) {     glViewport(0, 0, width, height); } //****************************** void processInput(GLFWwindow* window) {     if (glfwGetKey(window, GLFW_KEY_ESCAPE) == GLFW_PRESS)         glfwSetWindowShouldClose(window, true); } //********************************* int main() {     glfwInit();     glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 3);     glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 3);     glfwWindowHint(GLFW_OPENGL_PROFILE, GLFW_OPENGL_CORE_PROFILE);     //glfwWindowHint(GLFW_OPENGL_FORWARD_COMPAT, GL_TRUE);     GLFWwindow* window = glfwCreateWindow(800, 600, "LearnOpenGL", nullptr, nullptr);     if (window == nullptr)     {         cout << "Failed to create GLFW window" << endl;         glfwTerminate();         return -1;     }     glfwMakeContextCurrent(window);     if (!gladLoadGLLoader((GLADloadproc)glfwGetProcAddress))     {         cout << "Failed to initialize GLAD" << endl;         return -1;     }     glViewport(0, 0, 600, 480);     glfwSetFramebufferSizeCallback(window, framebuffer_size_callback);     glClearColor(0.2f, 0.3f, 0.3f, 1.0f);     glClear(GL_COLOR_BUFFER_BIT);     while (!glfwWindowShouldClose(window))     {         processInput(window);         glfwSwapBuffers(window);         glfwPollEvents();     }     glfwTerminate();     return 0; }
The result should be a fixed dark green-blueish color as the end of here. But the color of my window turns from black to green-blueish repeatedly in high speed! I thought it might be a problem with my Graphics card driver but I've updated it and it's: NVIDIA GeForce GTX 750 Ti.
What is the problem and how to solve it please?

• 10
• 12
• 22
• 13
• 33