Sign in to follow this  
Followers 0
Acharis

OpenGL
How to test if OpenGL support textures of non power of 2?

11 posts in this topic

I need a code (that works under OpenGL 1.5+) that checks if textures of non power of 2 are supported (via some extension maybe?)

Or maybe I should just check if OpenGL 2.0 is present and older versions would never be able to support it anyway?
0

Share this post


Link to post
Share on other sites
Check the extension string for ARB_texture_non_power_of_two. For OpenGL 2.0 and later you don't have to check anything since its in the core already.
1

Share this post


Link to post
Share on other sites
Do I need to test for extension AND for OpenGL version 2.0+

OR

OpenGL 2.0+ has ARB_texture_non_power_of_two extension always present? So the check for extension presence alone is enough?
0

Share this post


Link to post
Share on other sites
OpenGL 2.0 or later alone is enough, you don't need to check the extension if the version is OK. If the version is pre-2.0, then you need to check the extension. But note that 2.0 does not mean that the extension will be listed so you cannot rely on the extension alone. You have to check both if you want to cover for earlier versions, but passing one of the tests is enough.
1

Share this post


Link to post
Share on other sites
Beware that OpenGL makes no promise to hardware-accelerate non-power-of-two textures. And you can't check for that.

In general if your GL_VERSION is 3.0 or better you're absolutely guaranteed to have them, and to have them be hardware accelerated. In the rare event that you encounter a really really really old card with a lower version, you may or may not have them be accelerated (GeForce FX was an offender here, despite claiming 2.0). You might be aware to get away with GL_ARB_texture_rectangle instead, if your usage meets it's restrictions: http://www.opengl.org/registry/specs/ARB/texture_rectangle.txt
1

Share this post


Link to post
Share on other sites
For simplicity's sake:

[source lang="cpp"]#include <GL/glew.h>

glewInit();

if (GLEW_VERSION_2_0 || GLEW_ARB_texture_non_power_of_two)
{
/* I can haz teh supportz? */
}[/source]
2

Share this post


Link to post
Share on other sites
OK, maybe I will explain in details.

I use glDrawPixels for 2D stuff, that are my requirements. Because it's slow I rewrote it to standard textured quads (ortho perspective, etc). But since power of two textures are sometimes not supported I need to fallback to glDrawPixels in some cases (that's why I need the detection part). I can do it any other way of course, as long as compatibility and performance is OK since this is my goal. Again, I don't need anything fancy here, it's just a replacement for glDrawPixels.

Is the GL_ARB_texture_rectangle extension significantly more supported? Or other extensions/tricks?

How to do it best? How you would do it?
0

Share this post


Link to post
Share on other sites
Just because you're using textures doesn't mean you have to draw the whole texture. Another option is to use a texture the size of the next larger power of two and then stick your image in a part of the larger texture. You can even pack multiple images in in the same texture if you want.
1

Share this post


Link to post
Share on other sites
[quote name='Acharis' timestamp='1351063621' post='4993347']OK, maybe I will explain in details.

I use glDrawPixels for 2D stuff, that are my requirements. Because it's slow I rewrote it to standard textured quads (ortho perspective, etc). But since power of two textures are sometimes not supported I need to fallback to glDrawPixels in some cases (that's why I need the detection part). I can do it any other way of course, as long as compatibility and performance is OK since this is my goal. Again, I don't need anything fancy here, it's just a replacement for glDrawPixels.[/quote]

glDrawPixels can be fast if you use the right params. Since you've observed slowness I'm guessing that you're using dear old GL_RGB/GL_UNSIGNED_BYTE, which is a slow path nearly everywhere; you need these parameters to match the native format of your backbuffer otherwise GL is going to send the data through intermediate conversion steps, so try it with GL_BGRA/GL_UNSIGNED_INT_8_8_8_8_REV for starters and you should see a [i]very[/i] noticeable performance increase (at the cost of an extra byte per pixel - fair tradeoff) - that just requires GL1.2 support. Also be sure, if you're using glDrawPixels, to switch off texturing and lighting, as OpenGL will texture and light individual pixels otherwise.

[quote name='Acharis' timestamp='1351063621' post='4993347']Is the GL_ARB_texture_rectangle extension significantly more supported? Or other extensions/tricks?[/quote]

The definition of "significant" nowadays is that you can rely on full general non-power-of-two support being available absolutely everywhere, aside from some 6-year-old laptops or business-class PCs with integrated Intels. But since you're aiming for an [i]extremely [/i]downlevel minimum GL_VERSION it's fair to say that GL_ARB_texture_rectangle is more likely to be supported on that class of lower paleolithic hardware. Edited by mhagain
1

Share this post


Link to post
Share on other sites
[quote name='mhagain' timestamp='1351076224' post='4993388']
glDrawPixels can be fast if you use the right params. Since you've observed slowness I'm guessing that you're using dear old GL_RGB/GL_UNSIGNED_BYTE, which is a slow path nearly everywhere; you need these parameters to match the native format of your backbuffer otherwise GL is going to send the data through intermediate conversion steps, so try it with GL_BGRA/GL_UNSIGNED_INT_8_8_8_8_REV for starters and you should see a [i]very[/i] noticeable performance increase (at the cost of an extra byte per pixel - fair tradeoff) - that just requires GL1.2 support. [/quote]Can I use GL_RGBA,GL_UNSIGNED_INT_8_8_8_8_REV instead? Or it must be BGRA?
0

Share this post


Link to post
Share on other sites
[quote name='Acharis' timestamp='1352719918' post='5000195']
[quote name='mhagain' timestamp='1351076224' post='4993388']
glDrawPixels can be fast if you use the right params. Since you've observed slowness I'm guessing that you're using dear old GL_RGB/GL_UNSIGNED_BYTE, which is a slow path nearly everywhere; you need these parameters to match the native format of your backbuffer otherwise GL is going to send the data through intermediate conversion steps, so try it with GL_BGRA/GL_UNSIGNED_INT_8_8_8_8_REV for starters and you should see a [i]very[/i] noticeable performance increase (at the cost of an extra byte per pixel - fair tradeoff) - that just requires GL1.2 support. [/quote]Can I use GL_RGBA,GL_UNSIGNED_INT_8_8_8_8_REV instead? Or it must be BGRA?
[/quote]

It depends on the layout of your underlying framebuffer, and that's going to be decided by your hardware. If your hardware likes data in BGRA order, then BGRA order is what you must use to get the fast path.
1

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 Jon Alma
      Some time ago I implemented a particle system using billboarding techniques to ensure that the particles are always facing the viewer.  These billboards are always centered on one 3d coordinate.
      I would like to build on this and use billboarding as the basis for things like laser bolts and gunshots.  Here the difference is that instead of a single point particle I now have to draw a billboard between two points - the start and end of the laser bolt for example.  I appreciate that having two end points places limits on how much the billboard can be rotated to face the viewer, but I'm looking to code a best effort solution.  For the moment I am struggling to work out how to do this or find any tutorials / code examples that explain how to draw a billboard between two points ... can anyone help?
      Thanks.
    • By Sagaceil
      It's always better to fight with a bro.
    • By recp
      Hi,
      I'm working on new asset importer (https://github.com/recp/assetkit) based on COLLADA specs, the question is not about COLLADA directly
      also I'm working on a new renderer to render (https://github.com/recp/libgk) imported document.
      In the future I'll spend more time on this renderer of course, currently rendering imported (implemented parts) is enough for me
      assetkit imports COLLADA document (it will support glTF too),
      importing scene, geometries, effects/materials, 2d textures and rendering them seems working
      My actual confusion is about shaders. COLLADA has COMMON profile and GLSL... profiles,
      GLSL profile provides shaders for effects so I don't need to wory about them just compile, link, group them before render

      The problem occours in COMMON profile because I need to write shaders,
      Actually I wrote them for basic matrials and another version for 2d texture
      I would like to create multiple program but I am not sure how to split this this shader into smaller ones,

      Basic material version (only colors):
      https://github.com/recp/libgk/blob/master/src/default/shader/gk_default.frag
      Texture version:
      https://gist.github.com/recp/b0368c74c35d9d6912f524624bfbf5a3
      I used subroutines to bind materials, actually I liked it,
      In scene graph every node can have different program, and it switches between them if parentNode->program != node->program
      (I'll do scene graph optimizations e.g.  view frustum culling, grouping shaders... later)

      I'm going to implement transparency but I'm considering to create separate shaders,
      because default shader is going to be branching hell
      I can't generate shader for every node because I don't know how many node can be exist, there is no limit.
      I don't know how to write a good uber-shader for different cases:

      Here material struct:
      struct Material { ColorOrTexture emission; ColorOrTexture ambient; ColorOrTexture specular; ColorOrTexture reflective; ColorOrTexture transparent; ColorOrTexture diffuse; float shininess; float reflectivEyety; float transparency; float indexOfRefraction; }; ColorOrTexture could be color or 2d texture, if there would be single colorOrTex then I could split into two programs,
      Also I'm going to implement transparency, I am not sure how many program that I needed

      I'm considering to maintain a few default shaders for COMMON profile,
      1-no-texture, 2-one of colorOrTexture contains texture, 3-........

      Any advices in general or about how to optimize/split (if I need) these shaders which I provied as link?
      What do you think the shaders I wrote, I would like to write them without branching if posible,
      I hope I don't need to write 50+ or 100+ shaders, and 100+ default programs

      PS: These default shaders should render any document, they are not specific, they are general purpose...
             I'm compiling and linking default shaders when app launched

      Thanks
    • By CircleOfLight97
      Hi guys,
      I would like to contribute to a game project as a developer (open source possibly). I have some experiences in C/C++ in game development (perso projects). I don't know either unreal or unity but I have some knowledges in opengl, glsl and shading theory as I had some courses at university regarding to that. I have some knowledges in maths and basic in physics. I know a little how to use blender to do modelling, texturing and simple game assets (no characters, no animation no skinning/rigging). I have no game preferences but I like aventure game, dungeon crawler, platformers, randomly generated things. I know these kind of projects involve a lot of time and I'd be really to work on it but if there are no cleary defined specific design goals/stories/gameplay mechanics I would like to not be part of it x) and I would rather prefer a smaller but well defined project to work on that a huge and not 'finishable' one.
      CircleOfLight97
    • By gamesthatcouldbeworse
      Hi, I finally released KILL COMMANDO on gamejolt for free. It is a retro-funsplatter-shooter with C64 style. Give it a try.
  • Popular Now