Sign in to follow this  

OpenGL Generating texture coordinates

Recommended Posts

Ok, developing and developing, it's time for texturing... I read something about texture coordinates all over the net, but many questions are still without an answer... 1. glTexGen* should be used to generate texture coodinates, but how I could use this 'offline', to save texture coordinates for a mesh? I mean, I thought I had to pass to a function a texture size (width, height), vertex coordinates (x,y,z) and a mode (for cube/sphere/etc mapping) to retrieve correct (u,v)... but it seems glTexGen* doesn't work as I expected... I suppose glTexGen* are used to specify what kind of coordinates I have to generate, while glTexGen*v should return values... but if it's the case... how should I specify what's the vertex to map in texture space? :( 2. Is it possible to use glTexGen* with VertexArrays? I suppose so, but I can't figure how... 3. Is there a tutorial/example about glTexGen*? 4. Rendering animated meshes, I should compute 'offline' texture coordinates for each key frame, or it's better to let OpenGL generate them at runtime (if I didn't misunderstood glTexGen* usage... and it could be so...)? I find texturing not so easy as I thought, indeed... :P

Share this post

Link to post
Share on other sites
Ok, I finally decided to consult my RedBook, founding some useful information... without clearing all my dubts... this is my first problem... RedBook says:

--------------------------- RED BOOK -----------------------------------
void glTexGen{ifd}(GLenum coord, GLenum pname, TYPEparam);
void glTexGen{ifd}v(GLenum coord, GLenum pname, TYPE *param);

Specifies the functions for automatically generating texture coordinates.

The first parameter <...>

If it's GL_TEXTURE_GEN_MODE, param is an integer (or, in the vector version
of the command, points to an integer) that's either GL_OBJECT_LINEAR,
GL_EYE_LINEAR, or GL_SPHERE_MAP. These symbolic constants determine which
function is used to generate the texture coordinate.

With either of the other possible values for pname, param is a pointer to an array of values (for the vector version) specifying parameters for the
texture-generation function.
So, it says that I can call glTexGen* or glTexGen*v, depending on my needs:
I can use the first with GL_TEXTURE_GEN_MODE, specifying next what kind of mapping I intend to do, and setting up texture plane by the second function (the one accepting vectors).
Now, reading I assumed that I could use glTexGen*(GL_S,GL_OBJECT_PLANE,...) [the not-vector form] but MSDN says definitely NOT:

--------------------------- MSDN ------------------------------------
void glTexGen*( GLenum coord, GLenum pname, GLdouble param);

pname The symbolic name of the texture coordinategeneration function. Must be GL_TEXTURE_GEN_MODE.

If my understanding are correct, MSDN is right, I can't call the not-vector-based function with a parameter different from GL_TEXTURE_GEN_MODE, since there is no int parameter associated to GL_OBJECT_PLANE or GL_EYE_PLANE...
am I correct about this?
So, the not-vector-based form, is only used to specify the texture coordinates generation function, the vector-based one is needed to define clip planes...

And here lies my other dubt... how should I define this planes? To generate correct texture coordinates for a complex mesh (like a human body), what kind of planes I should define and, above all, why? I'd like to understand a bit more about it...

Moreover, rendering dynamic scenes, is it too expansive to call glTexGen* every frame? Is it better to precompute texture coordinates (it can be easily done for object coordinates, but doing it for view coordinates is not so good, since every time modelview matrix changes I should recompute coordinates... --') or let OpenGL do this work for me? How professional programs handle this, if anybody knows (Since this is my first attempt to create a 3D engine, I don't want to create a professional product, but I'd like to know a bit more about this scenario)?

Thnx in advance :D

Share this post

Link to post
Share on other sites
If your making a 3d engine that uses polygonal models I dont see why would you need glTexGen, as all the uv's are stored in the model format and you can just store them in your vertex class or structure (or in some other manner).

Share this post

Link to post
Share on other sites
Yes, but what if I would deal with dynamic meshes? In such a case texture coordinates should be calculated every time the mesh changes it's shape... Am I wrong? Moreover, what if the model I loaded has no texture coordinates? I would like to be able to generate them... that's why I'm asking informations about glTexGen, to go deeper and learn how to calculate them... that's why I'm asking now, how to define (what equation) texture planes... I know I can "copy" the function provided in the docs to calculate texture coordinates *offline* now, but I'd like to understand well what are that planes for, understanding the underlying math... :P

Share this post

Link to post
Share on other sites
TexGen is not magic, it can't map textures intelligently to any random animated mesh and have it work with whatever texture you provide. With models you'll want to load in texture coordinates that have been manually setup for use with a specific texture. Texture coordinates are usually static for animated meshes, unless you're specifically scrolling or warping the texture as well (like for water flow).

TexGen is useful when you want to do on-the-fly placement of textures on existing geometry (like projecting flashlight textures or shadows) or when you want to add an environment map which constantly changes depending on the orientation of the model.

Share this post

Link to post
Share on other sites
orangytang is correct there is no magic solution getting texturecoordinats for a model is a timeconsuming + boring task
your best bet for info is a modelling site eg try

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