Sign in to follow this  
Ender1618

OpenGL Eigen with modern OpenGL

Recommended Posts

So I'm getting back into OpenGL after a many years of work with D3D (the project I'm working on needs to be cross platform). Wanted to avoid fixed function (and the rest of the deprecated functionality) and stick with modern OpenGL (3.0,4.0).

So then comes the immediate question as to what vector/linear algebra library to use. The code base I am working with is already using Eigen for linear algebra. So i though i should use Eigen for my OpenGL work as well (since many people are saying they are doing this), and it would be a bit of a head ache to use multiple math libraries that were suppose to be doing many of the same things. Then I hit the alignment issue in Eigen, where all fixed sized types are 16 byte aligned.

The typical way i define a vertex in D3D is with a structure e.g.
[CODE]
struct MyVertex
{
Vec3 position;
Vec3 nornal;
Vec2 texcoord;
};
[/CODE]

I know I can do something like this in OGL with interleaved VBOs, or i could split the vertices up in to component arrays. The issue is that if I replace Vec3 with Eigen::Vector3f (or the 2 float variants), Vector3f is 16 byte aligned. In the Eigen documentation, it states that it is recommended when declaring a struct containing Eigen fixed size types (such as Vector3f) that you should use the macro EIGEN_MAKE_ALIGNED_OPERATOR_NEW which redefines new to deal with alignment issues: [url="http://eigen.tuxfamily.org/api/TopicStructHavingEigenMembers.html"]http://eigen.tuxfami...genMembers.html[/url]

Would this not wreak havoc with an array of MyVertex, and specifying component offsets (or even component arrays)? Should I not be using Eigen types in my vertex structures or component arrays? Anyone have any experience with using OGL with Eigen as their math library and has dealt with these issues?

There isnt much documentation on the caveats of using OGL with Eigen (or maybe I'm just looking in the wrong place), the support module provided by Eigen seems to focus more on fixed function calls: [url="http://eigen.tuxfamily.org/dox/unsupported/group__OpenGLSUpport__Module.html"]http://eigen.tuxfami...rt__Module.html[/url]

Any insight would be greatly appreciated.

Share this post


Link to post
Share on other sites
Never heard of Eigen before, so can not be of any help there, sadly. Although you are not searching for a new math library i think it would not hurt to drop an alternative lib name anyway. [url=http://glm.g-truc.net/]GLM[/url] - it is quite convenient, mostly because it mimics glsl and gl conventions in general [including extendability + many extensions. ex: quaternions, simplex noise, etc] (it is also a header-only library - which is also quite convenient). Only complaint i have is that its half-float conversion is terribly inefficient (unless the latest release fixed it).

Share this post


Link to post
Share on other sites
[quote name='Ender1618' timestamp='1335371305' post='4934803']Would this not wreak havoc with an array of MyVertex? Should I not be using Eigen types in my vertex structures or component arrays?[/quote]Yes, you probably shouldn't be using eigen types inside your vertex structs.
Your GL vertex structs are usually packed to be optimal for consumption by the GPU ([i]which usually means: as small as possible[/i]), whereas your eigen structs are going to be padded/aligned to be optimal for SIMD processing by a CPU ([i]which usually means allocated on 16-byte aligned boundaries[/i]). These two goals are ([i]usually[/i]) contradictory, so you should use different types for each goal ([i]CPU-optimised types for CPU-processing, GPU-optimised types for GPU-processing[/i]).

Share this post


Link to post
Share on other sites
Only vectorizable fixed vector and matrix types require 16bytes alignment. In other word, this concerns only types which sizes are a multiple of 16 bytes. So Eigen's types will never introduce any padding in your structs.

Share this post


Link to post
Share on other sites
I had no end of problems when I tried to use a SIMD aware math library in my project (slmath). First I had to allocate on a boundary and second there's a problem with containers in VC++ such that putting such aligned objects into them resulted in seg faults and all kinds of issues (I'm a heavy user of std::). In the end I decided it was too much trouble for the potential gain in speed, so I switched to glm::, which so far has been a joy to use (and program that doesn't seg fault runs much faster than one that does!). I wouldn't rule out using SIMD for very tight, focused algorithms though, and I'm waiting with anticipation for a future where compilers intelligently make use of SIMD themselves, so I don't have to.

Share this post


Link to post
Share on other sites
[quote name='RobinsonUK' timestamp='1335462042' post='4935139']
I had no end of problems when I tried to use a SIMD aware math library in my project (slmath). First I had to allocate on a boundary ...
[/quote]

There is a function in VC++ that allocates on a boundary. I imagine you are using new/delete and searching for a memory location that starts on a boundary by yourself.

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  

  • Forum Statistics

    • Total Topics
      627757
    • Total Posts
      2978950
  • Similar Content

    • By DelicateTreeFrog
      Hello! As an exercise for delving into modern OpenGL, I'm creating a simple .obj renderer. I want to support things like varying degrees of specularity, geometry opacity, things like that, on a per-material basis. Different materials can also have different textures. Basic .obj necessities. I've done this in old school OpenGL, but modern OpenGL has its own thing going on, and I'd like to conform as closely to the standards as possible so as to keep the program running correctly, and I'm hoping to avoid picking up bad habits this early on.
      Reading around on the OpenGL Wiki, one tip in particular really stands out to me on this page:
      For something like a renderer for .obj files, this sort of thing seems almost ideal, but according to the wiki, it's a bad idea. Interesting to note!
      So, here's what the plan is so far as far as loading goes:
      Set up a type for materials so that materials can be created and destroyed. They will contain things like diffuse color, diffuse texture, geometry opacity, and so on, for each material in the .mtl file. Since .obj files are conveniently split up by material, I can load different groups of vertices/normals/UVs and triangles into different blocks of data for different models. When it comes to the rendering, I get a bit lost. I can either:
      Between drawing triangle groups, call glUseProgram to use a different shader for that particular geometry (so a unique shader just for the material that is shared by this triangle group). or
      Between drawing triangle groups, call glUniform a few times to adjust different parameters within the "master shader", such as specularity, diffuse color, and geometry opacity. In both cases, I still have to call glBindTexture between drawing triangle groups in order to bind the diffuse texture used by the material, so there doesn't seem to be a way around having the CPU do *something* during the rendering process instead of letting the GPU do everything all at once.
      The second option here seems less cluttered, however. There are less shaders to keep up with while one "master shader" handles it all. I don't have to duplicate any code or compile multiple shaders. Arguably, I could always have the shader program for each material be embedded in the material itself, and be auto-generated upon loading the material from the .mtl file. But this still leads to constantly calling glUseProgram, much more than is probably necessary in order to properly render the .obj. There seem to be a number of differing opinions on if it's okay to use hundreds of shaders or if it's best to just use tens of shaders.
      So, ultimately, what is the "right" way to do this? Does using a "master shader" (or a few variants of one) bog down the system compared to using hundreds of shader programs each dedicated to their own corresponding materials? Keeping in mind that the "master shaders" would have to track these additional uniforms and potentially have numerous branches of ifs, it may be possible that the ifs will lead to additional and unnecessary processing. But would that more expensive than constantly calling glUseProgram to switch shaders, or storing the shaders to begin with?
      With all these angles to consider, it's difficult to come to a conclusion. Both possible methods work, and both seem rather convenient for their own reasons, but which is the most performant? Please help this beginner/dummy understand. Thank you!
    • By JJCDeveloper
      I want to make professional java 3d game with server program and database,packet handling for multiplayer and client-server communicating,maps rendering,models,and stuffs Which aspect of java can I learn and where can I learn java Lwjgl OpenGL rendering Like minecraft and world of tanks
    • By AyeRonTarpas
      A friend of mine and I are making a 2D game engine as a learning experience and to hopefully build upon the experience in the long run.

      -What I'm using:
          C++;. Since im learning this language while in college and its one of the popular language to make games with why not.     Visual Studios; Im using a windows so yea.     SDL or GLFW; was thinking about SDL since i do some research on it where it is catching my interest but i hear SDL is a huge package compared to GLFW, so i may do GLFW to start with as learning since i may get overwhelmed with SDL.  
      -Questions
      Knowing what we want in the engine what should our main focus be in terms of learning. File managements, with headers, functions ect. How can i properly manage files with out confusing myself and my friend when sharing code. Alternative to Visual studios: My friend has a mac and cant properly use Vis studios, is there another alternative to it?  
    • By ferreiradaselva
      Both functions are available since 3.0, and I'm currently using `glMapBuffer()`, which works fine.
      But, I was wondering if anyone has experienced advantage in using `glMapBufferRange()`, which allows to specify the range of the mapped buffer. Could this be only a safety measure or does it improve performance?
      Note: I'm not asking about glBufferSubData()/glBufferData. Those two are irrelevant in this case.
    • By xhcao
      Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness. 
  • Popular Now