View Full Version : frame drop when binding & rendering large texture
10-05-2011, 11:38 PM
I am experiencing a frame drop when binding and rendering textures for the first frame. I can remedy this by rendering the texture once at start-up but it is not an ideal situation to have to pre-render all the textures just to get rid of the sudden frame drop. It is like the texture becomes cached when it has been rendered and don't cause any future slowdowns once this has been done.
Can this issue be fixed without pre-rendering the texture somehow? The texture is 2048x2048 and I'm using an ATI4850 graphics card, I know it should be able to handle it.
No shaders involved, just fixed function and two textures.
10-06-2011, 01:44 AM
I've made a small test program. If anyone is willing to try it out I would be grateful.
It's a big quad going back and forth over the screen. When space is pressed the quad changes texture. The first time this is done there is a brief frame drop, It might be needed to run the test several times to notice the frame drop.
I have noticed this bug on:
ATI Radeon 4850
intel mobile graphic card. (don't know exact model)
The drop didn't occur on:
GeForce GTX 285
GeForce 8400 M G
10-06-2011, 06:38 AM
Simple question: Do you bind the tex object and upload data to video memory at init time or right before doing some rendering?
10-06-2011, 11:09 AM
Thanks for the reply! Both textures are loaded right after window creation. The program main loop only binds the requested texture and renders it.
10-06-2011, 11:14 AM
This use to be a common problem in all games because the driver stores the texture in RAM but it never sends it to the video card until it is used.
It is possible that AMD and nVidia have different texture policies. It isn't something that can be control via GL calls.
10-06-2011, 12:16 PM
Can this issue be fixed without pre-rendering the texture somehow?This use to be a common problem in all games because the driver stores the texture in RAM but it never sends it to the video card until it is used.
Right. O-san, I think the solution you propose is exactly what you need. AFAIK, there isn't a glUploadTextureToTheGPUNow( tex_handle ). You need to invoke an action that requires the texture to be GPU-resident, and the upload is done implicitly...
...of course, it may be "undone" too, if you have insufficient room on your GPU for your full working set of textures. Texture residency is virtualized. There is glPrioritizeTextures, but I don't know which vendors honor that, if any.
10-06-2011, 01:10 PM
Ah thank you for the insight. I'll just try to prerender my most needed textures then and see if that helps. I also thought of splitting up my large texture to smaller ones. It seemed to help somewhat to shrink the texture. But now that I've read your posts I am having second thoughts about it.
Powered by vBulletin® Version 4.2.3 Copyright © 2017 vBulletin Solutions, Inc. All rights reserved.