Sign in to follow this  
hayden

OpenGL How to check in my graphics card...?

Recommended Posts

Hi, i'm programming an application in GLSL/OpenGL and i need to check if my graphics supports any resolution or if only supports width/height values as power of 2. How can i check this? I google searched it but i didn't found the answer... Sorry for the basic question :)

Share this post


Link to post
Share on other sites
Texture resolution or screen resolution?

If you mean screen resolution, this is done through your operating system, or if you mean textures, you can get it with this:


int gl_max_texture_size;
glGetIntegerv( GL_MAX_TEXTURE_SIZE, &gl_max_texture_size );

Share this post


Link to post
Share on other sites
I'm pretty sure most modern graphics cards only support textures with power of 2 sizes mainly because it means they can do a lot of optimisations.

Screen resolution is usually 16:9, 16:10 or 4:3 ratios, there is nothing to stop you creating a window of any width/height though.

Share this post


Link to post
Share on other sites
Quote:
Original post by Malal
I'm pretty sure most modern graphics cards only support textures with power of 2 sizes mainly because it means they can do a lot of optimisations.

Screen resolution is usually 16:9, 16:10 or 4:3 ratios, there is nothing to stop you creating a window of any width/height though.

If ARB_texture_non_power_of_two is supported, you can use textures of any dimensions (as long as they're below the max size samster581 posted) and they'll work just fine.

IIRC "proper" video cards have supported this for several years (back to nVidia's FX6xxx, and ATi's equivilent), not sure about those crappy intel chips though.

[Edited by - OrangyTang on November 19, 2008 11:49:06 AM]

Share this post


Link to post
Share on other sites
Quote:
Original post by samster581
Texture resolution or screen resolution?

If you mean screen resolution, this is done through your operating system, or if you mean textures, you can get it with this:


int gl_max_texture_size;
glGetIntegerv( GL_MAX_TEXTURE_SIZE, &gl_max_texture_size );


I forgot to specify that.. sorry :S

I was referring texture resolutions the graphics card supports.

I did what you suggest and it gave me the value of 1244396. This means i can use any texture resolution?

Share this post


Link to post
Share on other sites
ARB_texture_non_power_of_two has promoted to core since opengl 2.0.
From the OpenGL 2.0 Specification:
Quote:

I.3 Non-Power-Of-Two Textures


The restriction of textures to power-of-two dimensions has been relaxed for all texture targets, so that non-power-of-two textures may be specified without generating errors. Non-power-of-two textures was promoted from the ARB_texture_non_power_of_two extension.


Thus you can use non-power-of-two textures in opengl 2.0 or higher (check glGetString(GL_VERSION) ) or if ARB_texture_non_power_of_two is supported (GL_ARB_texture_non_power_of_two is included in the string returned glGetString(GL_EXTENSIONS) ).


Quote:
Original post by hayden
I did what you suggest and it gave me the value of 1244396. This means i can use any texture resolution?


1) You should call glGetIntegerv after creating a valid opengl context, 1244396 is strange value, the max texture size is more likely something like 2048, 4096 or 8192.

2) No, Max texture size just tells you that the texture can not be larger than the maximum size in each dimension.

Share this post


Link to post
Share on other sites
Quote:
Original post by OrangyTang
IIRC "proper" video cards have supported this for several years (back to nVidia's FX5200, and ATi's equivilent), not sure about those crappy intel chips though.
My Intel X3100 works fine with non-power-of-2, even with the ghastly Apple drivers.

Share this post


Link to post
Share on other sites
Quote:
Original post by OrangyTang
IIRC "proper" video cards have supported this for several years (back to nVidia's FX5200, and ATi's equivilent), not sure about those crappy intel chips though.


Actually it started at the GeForce 6, on ATI i'm not pretty sure it started before the HD series.

Share this post


Link to post
Share on other sites
Quote:
Original post by hayden
I did what you suggest and it gave me the value of 1244396. This means i can use any texture resolution?


No, that can't be correct. You either got garbage back or you're not printing out the text correctly. You pass the address of an integer variable to that function.
You should get back a nice number like 1024, 2048 or 4096.

Share this post


Link to post
Share on other sites
Quote:
Original post by HuntsMan
Quote:
Original post by OrangyTang
IIRC "proper" video cards have supported this for several years (back to nVidia's FX5200, and ATi's equivilent), not sure about those crappy intel chips though.


Actually it started at the GeForce 6, on ATI i'm not pretty sure it started before the HD series.

Oops, you're right thanks. Fixed.

Side note: Delphi3d.net used to be great for checking these things but it's vanished sometime in the last year, does anyone know of a good replacement?

Share this post


Link to post
Share on other sites
Thanks for all of your replies :)
The 1244396 value was garbage, my bad... Now i'm having a max texture size of 8192.

Quote:
Original post by Kambiz
ARB_texture_non_power_of_two has promoted to core since opengl 2.0.
From the OpenGL 2.0 Specification:
Quote:

I.3 Non-Power-Of-Two Textures


The restriction of textures to power-of-two dimensions has been relaxed for all texture targets, so that non-power-of-two textures may be specified without generating errors. Non-power-of-two textures was promoted from the ARB_texture_non_power_of_two extension.


Thus you can use non-power-of-two textures in opengl 2.0 or higher (check glGetString(GL_VERSION) ) or if ARB_texture_non_power_of_two is supported (GL_ARB_texture_non_power_of_two is included in the string returned glGetString(GL_EXTENSIONS) ).


Quote:
Original post by hayden
I did what you suggest and it gave me the value of 1244396. This means i can use any texture resolution?


1) You should call glGetIntegerv after creating a valid opengl context, 1244396 is strange value, the max texture size is more likely something like 2048, 4096 or 8192.

2) No, Max texture size just tells you that the texture can not be larger than the maximum size in each dimension.

Now i get it, with the info you pointed here :) thanks again!

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  

  • Announcements

  • Forum Statistics

    • Total Topics
      628356
    • Total Posts
      2982251
  • Similar Content

    • By test opty
      Hi all,
       
      I'm starting OpenGL using a tut on the Web. But at this point I would like to know the primitives needed for creating a window using OpenGL. So on Windows and using MS VS 2017, what is the simplest code required to render a window with the title of "First Rectangle", please?
       
       
    • By DejayHextrix
      Hi, New here. 
      I need some help. My fiance and I like to play this mobile game online that goes by real time. Her and I are always working but when we have free time we like to play this game. We don't always got time throughout the day to Queue Buildings, troops, Upgrades....etc.... 
      I was told to look into DLL Injection and OpenGL/DirectX Hooking. Is this true? Is this what I need to learn? 
      How do I read the Android files, or modify the files, or get the in-game tags/variables for the game I want? 
      Any assistance on this would be most appreciated. I been everywhere and seems no one knows or is to lazy to help me out. It would be nice to have assistance for once. I don't know what I need to learn. 
      So links of topics I need to learn within the comment section would be SOOOOO.....Helpful. Anything to just get me started. 
      Thanks, 
      Dejay Hextrix 
    • By mellinoe
      Hi all,
      First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
      Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
      The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
      Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.
    • By aejt
      I recently started getting into graphics programming (2nd try, first try was many years ago) and I'm working on a 3d rendering engine which I hope to be able to make a 3D game with sooner or later. I have plenty of C++ experience, but not a lot when it comes to graphics, and while it's definitely going much better this time, I'm having trouble figuring out how assets are usually handled by engines.
      I'm not having trouble with handling the GPU resources, but more so with how the resources should be defined and used in the system (materials, models, etc).
      This is my plan now, I've implemented most of it except for the XML parts and factories and those are the ones I'm not sure of at all:
      I have these classes:
      For GPU resources:
      Geometry: holds and manages everything needed to render a geometry: VAO, VBO, EBO. Texture: holds and manages a texture which is loaded into the GPU. Shader: holds and manages a shader which is loaded into the GPU. For assets relying on GPU resources:
      Material: holds a shader resource, multiple texture resources, as well as uniform settings. Mesh: holds a geometry and a material. Model: holds multiple meshes, possibly in a tree structure to more easily support skinning later on? For handling GPU resources:
      ResourceCache<T>: T can be any resource loaded into the GPU. It owns these resources and only hands out handles to them on request (currently string identifiers are used when requesting handles, but all resources are stored in a vector and each handle only contains resource's index in that vector) Resource<T>: The handles given out from ResourceCache. The handles are reference counted and to get the underlying resource you simply deference like with pointers (*handle).  
      And my plan is to define everything into these XML documents to abstract away files:
      Resources.xml for ref-counted GPU resources (geometry, shaders, textures) Resources are assigned names/ids and resource files, and possibly some attributes (what vertex attributes does this geometry have? what vertex attributes does this shader expect? what uniforms does this shader use? and so on) Are reference counted using ResourceCache<T> Assets.xml for assets using the GPU resources (materials, meshes, models) Assets are not reference counted, but they hold handles to ref-counted resources. References the resources defined in Resources.xml by names/ids. The XMLs are loaded into some structure in memory which is then used for loading the resources/assets using factory classes:
      Factory classes for resources:
      For example, a texture factory could contain the texture definitions from the XML containing data about textures in the game, as well as a cache containing all loaded textures. This means it has mappings from each name/id to a file and when asked to load a texture with a name/id, it can look up its path and use a "BinaryLoader" to either load the file and create the resource directly, or asynchronously load the file's data into a queue which then can be read from later to create the resources synchronously in the GL context. These factories only return handles.
      Factory classes for assets:
      Much like for resources, these classes contain the definitions for the assets they can load. For example, with the definition the MaterialFactory will know which shader, textures and possibly uniform a certain material has, and with the help of TextureFactory and ShaderFactory, it can retrieve handles to the resources it needs (Shader + Textures), setup itself from XML data (uniform values), and return a created instance of requested material. These factories return actual instances, not handles (but the instances contain handles).
       
       
      Is this a good or commonly used approach? Is this going to bite me in the ass later on? Are there other more preferable approaches? Is this outside of the scope of a 3d renderer and should be on the engine side? I'd love to receive and kind of advice or suggestions!
      Thanks!
    • By nedondev
      I 'm learning how to create game by using opengl with c/c++ coding, so here is my fist game. In video description also have game contain in Dropbox. May be I will make it better in future.
      Thanks.
  • Popular Now