Sign in to follow this  
Tolito

OpenGL Sprite Sheet

Recommended Posts

I have decided to go with OpenGL rendering for a project of mine that was originally using SDL. It is still using SDL, but it is going to be depending on OpenGL for some graphical operations. One of my sprite sheets happens to have the dimensions, 1892x66. Here are my questions:

  1. Are the dimensions all wrong for an OpenGL texture, considering the power-of-two rule? If so, what is the best thing I can do?
  2. Does storing a sprite sheet as a surface in SDL use less memory than storing it as an OpenGL texture?
  3. Am I better off using separate graphics in the sheet for left and right and using a surface in SDL than using OpenGL, given the dimensions? I wrote a function to copy a sprite from a sheet to a separate surface and mirrored the surface, but this was slow when called multiple times in one frame.
  4. Will someone please link me to a document or post some code that provides an example of this?

Thank you! smile.png

Share this post


Link to post
Share on other sites
  1. Non-power-of-two textures have been supported pretty much everywhere for ages. It might be a concern if you're running on > 10-year-old hardware, or some mobile platforms. That said, a power-of-two (or at least more square) texture might work better for mip-mapping, and for various hardware caches.
  2. All things (dimensions, bit-depth, etc) being equal, it should be no larger in a texture. Perhaps smaller if you use a compressed texture.
  3. In general you want to keep the number of separate draw calls to a minimum, and one of the ways to help do that is to keep related things in a single texture. But it sounds to me more like the problem you're experiencing is due to copying and mirroring multiple times--if you're probably going to use the mirrored image again, do it once and keep it in memory.

Share this post


Link to post
Share on other sites

Thank you for your response! You have earned yourself some more reputation!

 

Are dimensions ever too big, or should it work in OpenGL if SDL can load it as a surface?

 

Yes, the slowdown was due to how many times I was calling those functions. I was asking if the power-of-two rule and other problems that may arise relating to the use of OpenGL would be so much trouble that I would be better off sticking with SDL and including mirrored versions of sprites in the sprite sheets. I was including that little detail to serve as an explanation as to why I wanted to switch to OpenGL and how such a function was slow. Sorry for the confusion.

 

Do you happen to have any examples for what I want to accomplish? Thank you again!

Share this post


Link to post
Share on other sites

Don't have any examples, sorry.

 

The width ought to be fine, aside from my other comments. I think a minimum of 2048x2048 has been the standard since around GeForce 2, or around 15 years ago. Again, you might find some mobile platforms that don't support textures that large, I'm not terribly familiar with feature support on mobile platforms.

Share this post


Link to post
Share on other sites

IIRC there was also a requirement for texture sizes to be divisible by 4 (so width needs to be divisible by 4)

 

I couldnt find much information by googling, it might only apply to compressed textures.

Share this post


Link to post
Share on other sites

IIRC there was also a requirement for texture sizes to be divisible by 4 (so width needs to be divisible by 4)

 

I couldnt find much information by googling, it might only apply to compressed textures.

That is incorrect. The size can be any value, even compressed textures.

 

Compressed textures are commonly compressed in blocks of 4x4 pixels. If a block is not fully used, the data has to be padded to form a valid 4x4 data block, but the actual texture does not have to fill this block entirely.

 

You may be thinking of the byte alignment, which required the byte-width of the image to be a multiple of 4 bytes. But that was just a parameter you could set anyway and effectively disable by setting a 1-byte alignment,

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
      628377
    • Total Posts
      2982324
  • 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