Sign in to follow this  
ChugginWindex

OpenGL Any good Open source GL 3.x engines for reference?

Recommended Posts

ChugginWindex    187
I'm trying to put together a little framework based on a strictly OpenGL 3.x context and I'm having a bit of trouble structuring some of my information and would like to take a look at how others may have solved the problem. I've looked/learned a lot from Ogre, Horde3D and the HP1Engine that FrictionalGames released last year, but so far either A) the engines don't utilize the aspects of OpenGL 3.x that I need help with or B) they do things I can't fully understand or follow. So I'm wondering if there's any other good modern engines that I can take a look at that I've missed so far. I'm currently working on the structure of my Shader system and VBO/VAO management and have found VAO implementations in the above engines to be seemingly nonexistent. Also defining a flexible vertex format and shader uniforms standards are hard to find or confusing in some of them as well.

The name "PolyCode" seems to be all the buzz lately and I've looked at that as well, the library/engine looks great and I've learned quite a deal from that as well, but it seems to use a hybrid of deprecated and non-deprecated OpenGL throughout which is something I'd like to avoid. Also as with the engines and libraries I mentioned above PolyCode does not appear to have VAO support yet.

So how about it? Any blatant resources I've missed for learning this stuff? I've got a copy of the OpenGL Superbible 5 as well which has served me well and taught me the fundamentals of HOW this stuff works, I'd just like to see more how existing systems do certain things but haven't had a whole lot of luck finding those who have adopted the latest GL tech.

Share this post


Link to post
Share on other sites
supermaximo93    124
I don't really know of any popular OpenGL 3.x engines (well, I haven't tried looking for any), but if you want to have a look at my game library, here's a link: [url="https://github.com/supermaximo93/SuperMaximo_GameLibrary"]https://github.com/s...imo_GameLibrary[/url]. I'm not saying it's the best example of what to do though, it's just my take on OpenGL [img]http://public.gamedev.net/public/style_emoticons/default/smile.gif[/img] It doesn't use any deprecated functionality (I think [img]http://public.gamedev.net/public/style_emoticons/default/rolleyes.gif[/img]), and also uses VAOs. I haven't done any documentation for it though, although I will do soon. The OpenGL stuff is in the src > source/headers > Display.h/.cpp and the Font, Model, Sprite, Shader and Texture class files.

For some proof that the code actually does work [img]http://public.gamedev.net/public/style_emoticons/default/laugh.gif[/img] (although albeit an older version written in Pascal): [url="http://www.pascalgamedevelopment.com/showthread.php?9927-PGDmC-Mr-Snugglekins-and-the-Giant-Sack-of-Catnip"]http://www.pascalgamedevelopment.com/showthread.php?9927-PGDmC-Mr-Snugglekins-and-the-Giant-Sack-of-Catnip[/url]


I hope this helps [img]http://public.gamedev.net/public/style_emoticons/default/smile.gif[/img]

Share this post


Link to post
Share on other sites
Yours3!f    1532
a, BlendElf (If you can get the source of this out of SWIG then pls let me know.)<br />b, PixelLight<br />c, Psyche<br /><br />these are the first that came to my mind... they might not be pure OpenGL 3.x engines, or they may be 2.x but they're still a nice and modern example of what an engine should look like. To add you can learn a lot from them.

Sticking to OpenGL core context means not using deprecated functions. Besides FreeGLUT (and maybe GLFW) there are no libraries in which you can specify that you want pure OpenGL 3.x or 4.x functions, and the deprecated shouldn't event be present. In SFML though the author wrote on his forum that soon this feature will be available in SFML. It's really annoying when the source still compiles if you use deprecated stuff...

Share this post


Link to post
Share on other sites
ChugginWindex    187
[quote name='SuperMaximo93' timestamp='1312971183' post='4847104']
I don't really know of any popular OpenGL 3.x engines (well, I haven't tried looking for any), but if you want to have a look at my game library, here's a link: [url="https://github.com/supermaximo93/SuperMaximo_GameLibrary"]https://github.com/s...imo_GameLibrary[/url]. I'm not saying it's the best example of what to do though, it's just my take on OpenGL [img]http://public.gamedev.net/public/style_emoticons/default/smile.gif[/img] It doesn't use any deprecated functionality (I think [img]http://public.gamedev.net/public/style_emoticons/default/rolleyes.gif[/img]), and also uses VAOs. I haven't done any documentation for it though, although I will do soon. The OpenGL stuff is in the src > source/headers > Display.h/.cpp and the Font, Model, Sprite, Shader and Texture class files.

For some proof that the code actually does work [img]http://public.gamedev.net/public/style_emoticons/default/laugh.gif[/img] (although albeit an older version written in Pascal): [url="http://www.pascalgamedevelopment.com/showthread.php?9927-PGDmC-Mr-Snugglekins-and-the-Giant-Sack-of-Catnip"]http://www.pascalgam...-Sack-of-Catnip[/url]


I hope this helps [img]http://public.gamedev.net/public/style_emoticons/default/smile.gif[/img]
[/quote]

It does! I'm more looking for examples on how to Object-Orient stuff like VAOs (or if I even should) since they seem to hold so little information outside of native OpenGL state. Your model class doesn't appear to deal with that and instead opts for just having the classes that need a VAO to hold them internally in their pure form. This is still an option and seeing someone else doing it that way helps sway my final decision in just the way I was hoping it would. Also your straight-forward handling of Vertex Attributes and Uniforms is more or less exactly what I needed to see in order to get my brain out of it's endless loop of trying to abstract everything away to the infinitely generic level that gets me nowhere ;).

I'm still open to suggestions on engines that I can learn from. Yourse3!f I'll be taking a look at the ones you mentioned. I've never heard of BlendElf or Psyche but I HAVE heard of PixelLight and completely forgot about it until this moment! So thank you for that. Perhaps I'll find what I've been searching for in one of those.

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  

  • Similar Content

    • By povilaslt2
      Hello. I'm Programmer who is in search of 2D game project who preferably uses OpenGL and C++. You can see my projects in GitHub. Project genre doesn't matter (except MMO's :D).
    • By ZeldaFan555
      Hello, My name is Matt. I am a programmer. I mostly use Java, but can use C++ and various other languages. I'm looking for someone to partner up with for random projects, preferably using OpenGL, though I'd be open to just about anything. If you're interested you can contact me on Skype or on here, thank you!
      Skype: Mangodoor408
    • By tyhender
      Hello, my name is Mark. I'm hobby programmer. 
      So recently,I thought that it's good idea to find people to create a full 3D engine. I'm looking for people experienced in scripting 3D shaders and implementing physics into engine(game)(we are going to use the React physics engine). 
      And,ye,no money =D I'm just looking for hobbyists that will be proud of their work. If engine(or game) will have financial succes,well,then maybe =D
      Sorry for late replies.
      I mostly give more information when people PM me,but this post is REALLY short,even for me =D
      So here's few more points:
      Engine will use openGL and SDL for graphics. It will use React3D physics library for physics simulation. Engine(most probably,atleast for the first part) won't have graphical fron-end,it will be a framework . I think final engine should be enough to set up an FPS in a couple of minutes. A bit about my self:
      I've been programming for 7 years total. I learned very slowly it as "secondary interesting thing" for like 3 years, but then began to script more seriously.  My primary language is C++,which we are going to use for the engine. Yes,I did 3D graphics with physics simulation before. No, my portfolio isn't very impressive. I'm working on that No,I wasn't employed officially. If anybody need to know more PM me. 
       
    • By Zaphyk
      I am developing my engine using the OpenGL 3.3 compatibility profile. It runs as expected on my NVIDIA card and on my Intel Card however when I tried it on an AMD setup it ran 3 times worse than on the other setups. Could this be a AMD driver thing or is this probably a problem with my OGL code? Could a different code standard create such bad performance?
    • By Kjell Andersson
      I'm trying to get some legacy OpenGL code to run with a shader pipeline,
      The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
      I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
      I've got a version 330 vertex shader to somewhat work:
      #version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
      What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
      Question:
      What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?
       
      Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.
  • Popular Now