Sign in to follow this  

OpenGL Simple multiple textures

Recommended Posts

I did D3D for a "long" time now and am somewhat new to OpenGL (still at the basics)


What i am trying to do is:

... Initialize

> Load texture1, Load texture2

... Render

> Bind texture1 to texture unit 0, render some geometry

> Bind texture2 to texture unit 0, render some geometry


In short it doenst work as expected. The result is, that both geometry is rendered with texture2 on it. So i looked up the docs and they were stating:

"glTexSubImage2D specifies a two-dimensional subtexture for the current texture unit, specified with glActiveTexture."


So I spent some time on trial and erroring around and finally I activated texture unit 1 before loading texture 2 which yields the correct result if I bind at rendering texture1 to tex unit 0 and texture2 to tex uint 1. Binding both textures to tex unit 0 will render the geometry only with texture1.

Actually this feels like the instand I call glTexImage* when having bound a texture to a certain tex uint (texture2 at 0) the the data I loaded before that (texture1 at 0) gets discarded?


I'm not quite sure what that would mean. Is it ture, that I need to spend a tex uint for each texture??? I cannot believe that, this would suggest that my graphics card has a 96 (GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS) textures max limit (no way). 


so here some snippets on how I (initially inteded to) do the loading and rendereing (both geometry gets rendered with texture2 on it):

glGenTextures (1, &tex);
glBindTexture (cfg.GetBindFlag (), tex);
glTexStorage2D(tex, cfg.GetMipLevel (), cfg.GetTextureFormat (), cfg.GetWidth (), cfg.GetHeight ());
glTexImage2D (cfg.GetBindFlag (), 
	cfg.GetMipLevel (), 
	cfg.GetTextureFormat (), 
	cfg.GetWidth (), cfg.GetHeight (), 0, 
	cfg.GetDataFormat (), 
	cfg.GetDataType (), initdata);
glActiveTexture (_TexUnit); // _TexUnit is asserted as GL_TEXTURE0 + _TexUnitIndex
glBindTexture (resource->GetBindFlag (), resource->GetGLID ()); // resource::_GLID is corresponds to names of texture1 and texture 2
glUniform1i (_Location, _TexUnitIndex); // _Location is the uniform sampler bindpoint in the shader, _TexUnitIndex is 0 in both rendering events
_Sampler->Bind (_TexUnitIndex);

I actually conclude that I have to have missed something, the question is what? Hopefully some of you can point me a diretion.

Share this post

Link to post
Share on other sites

Ok, so I publically denounced myself... it was a "variable not initialized error" which took me 1 and a half day to track down and of cource I posted here 2 hours befor i finally found the error....


But anyways, i would be glad of some explanation to the documentation. What does that "specifies a two-dimensional subtexture for the current texture unit" mean? Why is the texture unit relevant in the context of uploading texture data?

Share this post

Link to post
Share on other sites

But anyways, i would be glad of some explanation to the documentation. What does that "specifies a two-dimensional subtexture for the current texture unit" mean?

glTexSubImage, and equivalent for the other Sub-variants, modifies as sub-rectangle of an existing texture. Say you have a 128x128-pixel texture consisting of a 4x4 grid of 32x32-pixel tiles. You can use it to update/replace a single tile without having to upload an entirely new texture image.

Why is the texture unit relevant in the context of uploading texture data?

OpenGL has a bind-to-edit model which means you have to bind the texture object to make it the currently active object. Subsequent calls to glTexImage and such then operates on the currently bound texture. As you may have noticed, you never tell glTexImage which texture object to populate with texture data; that is given from the previous call to glBindTexture.


Since multitexturing allows for multiple textures to be bound at the same time, the texture bound to the currently active texture unit is the target of glTexImage.

Edited by Brother Bob

Share this post

Link to post
Share on other sites

I'm sorry to say that but you just pointed out the obvisous for me :P


you never tell glTexImage which texture object to populate with texture data


Yes of course. What I was actually wondering, is why the docs refer to the texture unit and especially glActiveTexture.

I thought glActiveTexture, should have nothing to do with what is stored in the texture but instead is a mechanism to access the texture via glsl.

Share this post

Link to post
Share on other sites

The glTexImage function doesn't have a parameter specifying which texture unit to store the data to, so the documentation tells you it will store the data to the current texture unit. The way to specify the current texture unit is glActiveTexture.


To get the texture in GLSL, you need to use a sampler and make it available to your shader program.


Edit: this is the same thing Brother Bob said, but hopefully if a few people tell you the same thing in different ways it will click.

Edited by richardurich

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
    • Total Posts
  • 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. 
      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!
    • 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.
  • Popular Now