Sign in to follow this  
mv348

OpenGL To glut or not to glut...

Recommended Posts

mv348    263
I'm going to be modifying the source code from [url="http://ogldev.atspace.co.uk/"]these tutorials [/url] (Now available as Visual Studio 2010 Project files. YAY!) and use it as a code base for my graphics engine. These tutorials use glut to handle windowing and callbacks. I always used the Windows API for my OpenGL applications because my understanding was that it was the 'grown up way', it offered more flexibility and customization, and also glut seemed to be fading into obscurity, at least on Windows. But I'm trying to determine if its worth the effort to remove GLUT and replace it with direct Windows API calls. In the future I hope to make use of some type of Game-pad and I don't think glut offers a whole lot of options for that. More specifically, I don't believe it supports force-feedback and I'd have to use a more advanced input API. I'm not sure if glut would play nice with that, given its current input and callback mechanisms.

Can I hear some opinions? Is it unprofessional to use GLUT in a modern application? Will it hold me back in any way? Edited by mv348

Share this post


Link to post
Share on other sites
larspensjo    1561
I suppose you mean freeglut, and not glut. Glut is indeed very old and not supported.

Personally, I prefer glfw instead of *glut. But glfw doesn't support fore-feedback either (though it is considered for 3.0). I feel glfw as a more mature library than *glut.

The tutorials you link to seem to be "almost" up-to-date, but not completely. They are not using Vertex Array Objects, which is mandatory from OpenGL 3.

For a very good, minimal example, see [url="https://github.com/progschj/OpenGL-Examples"]https://github.com/progschj/OpenGL-Examples[/url]. Starting from the basic, to advanced. They are minimal in the sense that every example is only one file, and does only just what is needed and nothing more.

Share this post


Link to post
Share on other sites
SimonForsman    7642
glut was originally made to support the OpenGL redbook examples (without having to deal with platform specific code), it is not a complete API and shouldn't be used in serious applications and yes it will hold you back. (main problem imo is that it takes over the game loop)

Personally i wouldn't use the Windows API with OpenGL either since it is a pain in the ass to write platform specific code (and AFAIK Win32 doesn't include force feedback support either, you probably have to use DirectInput on Windows for that), something like SFML + OIS might be a good combination though.

Share this post


Link to post
Share on other sites
mv348    263
Thanks for your responses!

[quote]The tutorials you link to seem to be "almost" up-to-date, but not completely. They are not using Vertex Array Objects, which is mandatory from OpenGL 3.[/quote]

I did not know it was mandatory (Is it really? In the sense that it won't even work?) But they introduced VAO's back in [url="http://ogldev.atspace.co.uk/www/tutorial32/tutorial32.html"]Tutorial 32[/url] and have used them from there on.

So yes, let us clarify, turns out it is in fact FreeGlut that the tutorials use for Windows.

[quote]
Personally i wouldn't use the Windows API with OpenGL either since it is a pain in the ass to write platform specific code
[/quote]

Really? I thought it would be harder to make my code cross-platform compatible than to just go with a single platform.

So I'd need DirectInput for force feedback? Hmm.. that's annoying...

Share this post


Link to post
Share on other sites
larspensjo    1561
[quote name='mv348' timestamp='1352498215' post='4999442']
[quote]The tutorials you link to seem to be "almost" up-to-date, but not completely. They are not using Vertex Array Objects, which is mandatory from OpenGL 3.[/quote]

I did not know it was mandatory (Is it really? In the sense that it won't even work?) But they introduced VAO's back in [url="http://ogldev.atspace.co.uk/www/tutorial32/tutorial32.html"]Tutorial 32[/url] and have used them from there on.[/quote]
It is possible to use OpenGL in compatibility mode, where legacy API is available. This support is probably not going to go away for a long time yet, so it isn't much of a problem. As you already understand the VAO, it looks to me like a good tutorial. As long as it isn't based on [url="http://www.opengl.org/wiki/Legacy_OpenGL"]immediate mode[/url], I think you are fine.

[quote][quote]
Personally i wouldn't use the Windows API with OpenGL either since it is a pain in the ass to write platform specific code
[/quote]

Really? I thought it would be harder to make my code cross-platform compatible than to just go with a single platform.
[/quote]

If you are used to Windows API, it may well be easier. I don't know the Windows API very well, and find glfw (or glut) is easier to use. And then you get portability at the same time.

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