Sign in to follow this  
Followers 0

OpenGL Learning Resources

6 posts in this topic

So, entering into my last year of my degree program, I decided I'd like to finally get around to working on some game development (comp sci major). I'd done a lot with DirectX 7 a long time ago, but I never completed a project. I decide to start small with a 2d Tetris clone. I found some tutorials and got the game about half complete or so. I show my friend (who has completed several games) what I've got and he's happy for me. He then adds, "But you're using all the deprecated stuff." My immediate reaction was, "Huh?" He explained to me about OpenGL immediate mode and how new things were done in OpenGL 3.xx and 4.xx and they seemed more in line from what I remember about DirectX. I resolved that I would go and learn the new way to do things and.. I hit a brick wall.

First of all, how do you even know what's deprecated?

Second of all, I can't seem to find any tutorials that are usable for OpenGL 3 or 4. The few that I have found are so full of game framework stuff and extraneous code that it's difficult to wade through it all. Of course, I can wade through the documentation on, but I was really hoping to find something to get me going a little quicker than that. I have seen numerous recommendations that people start with 2.0 and then migrate to other versions, but I have seen just as many recommendations that condemn these suggestions and say that it will only teach bad habits.

Of course, I don't have to use the newest API for a 2D Tetris game, but my goal was to learn using this game and then move up to something more difficult. Can someone please offer some guidance in the way of suggesting a tutorial or book that is at least somewhat up to date? My frustrations have forced me into contemplating going back towards a DirectX route. At least there seems to be a plethora of DirectX 11 tutorials. Any help would be greatly appreciated.

Share this post

Link to post
Share on other sites
If you want to see what's deprecated, the reference card is a quick place to check:

Any functions that are in blue are deprecated.

There's really not that much you need to know to be up to date, basically all boils down to:

1) Don't use the fixed pipeline for anything
2) Handle your own matrices
3) Use generic vertex attributes/uniforms with shaders
4) Don't use built-in lighting commands

Just following those rules will get you 95% up to date with modern opengl. Picking out any one of those items I'm sure you can find tutorials, so it's not too difficult.

Share this post

Link to post
Share on other sites
People who write tutorials are people who do it in their spare time and have a website. I imagine there aren't many such people.
Personally, I contribute to the Wiki in my spare time.

[quote]First of all, how do you even know what's deprecated?[/quote]
karwosts answered that.

Also, you make a forward context (not backward compatible context).
See some tutorials here

It is possible to use GL 2.0 while and avoid deprecated stuff. If one day you decide to more to GL 3.3 or GL 4.0, it becomes much easier. You would just add VAO support and change the shader code a little.

Share this post

Link to post
Share on other sites
Thanks very much for the replies.
I didn't mean to sound ungrateful to those that write the tutorials, I was just a bit frustrated at the time. I'd also accept recommendations on books, but I forgot to mention that.

I will do some research in those specific topics and look at the list of deprecated methods. Thanks very much!

Share this post

Link to post
Share on other sites
I am having the same issue currently. However, I found this:

This is a really cool tutorial regarding OpenGL 3.X.
Worth a read. Although I did not manage yet to get my ortho matrices working.

Share this post

Link to post
Share on other sites
I am in the same position as you. Just started with OpenGL and want to learn GLSL. 2.0 is still great but immediate mode for rendering is no longer used and for cool graphic effects shader GLSL is a must. Mainting the martices on your own :confused: vertex array and VBO are used now. I am also looking for some great tutorial on these, books.

What about these books are they good with examples code explained ? Orange book GLSL in particular

[quote name='NicoG' timestamp='1296694539' post='4768807']
I am having the same issue currently. However, I found this:

This is a really cool tutorial regarding OpenGL 3.X.
Worth a read. Although I did not manage yet to get my ortho matrices working.

Thanks for the link :) I will have a go at it

Share this post

Link to post
Share on other sites
Everything works now for me.
Was a good read so far. I am not finished with that tutorial.
But if you like to see the difference between my Code with OGL 2.0 and now, see this link:

However, the architecture of that code is still somewhat archaic and I will change the whole thing the next days to make it more batchfriendly.

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  
Followers 0

  • Similar Content

    • By Jon Alma
      Some time ago I implemented a particle system using billboarding techniques to ensure that the particles are always facing the viewer.  These billboards are always centered on one 3d coordinate.
      I would like to build on this and use billboarding as the basis for things like laser bolts and gunshots.  Here the difference is that instead of a single point particle I now have to draw a billboard between two points - the start and end of the laser bolt for example.  I appreciate that having two end points places limits on how much the billboard can be rotated to face the viewer, but I'm looking to code a best effort solution.  For the moment I am struggling to work out how to do this or find any tutorials / code examples that explain how to draw a billboard between two points ... can anyone help?
    • By Sagaceil
      It's always better to fight with a bro.
    • By recp
      I'm working on new asset importer ( based on COLLADA specs, the question is not about COLLADA directly
      also I'm working on a new renderer to render ( imported document.
      In the future I'll spend more time on this renderer of course, currently rendering imported (implemented parts) is enough for me
      assetkit imports COLLADA document (it will support glTF too),
      importing scene, geometries, effects/materials, 2d textures and rendering them seems working
      My actual confusion is about shaders. COLLADA has COMMON profile and GLSL... profiles,
      GLSL profile provides shaders for effects so I don't need to wory about them just compile, link, group them before render

      The problem occours in COMMON profile because I need to write shaders,
      Actually I wrote them for basic matrials and another version for 2d texture
      I would like to create multiple program but I am not sure how to split this this shader into smaller ones,

      Basic material version (only colors):
      Texture version:
      I used subroutines to bind materials, actually I liked it,
      In scene graph every node can have different program, and it switches between them if parentNode->program != node->program
      (I'll do scene graph optimizations e.g.  view frustum culling, grouping shaders... later)

      I'm going to implement transparency but I'm considering to create separate shaders,
      because default shader is going to be branching hell
      I can't generate shader for every node because I don't know how many node can be exist, there is no limit.
      I don't know how to write a good uber-shader for different cases:

      Here material struct:
      struct Material { ColorOrTexture emission; ColorOrTexture ambient; ColorOrTexture specular; ColorOrTexture reflective; ColorOrTexture transparent; ColorOrTexture diffuse; float shininess; float reflectivEyety; float transparency; float indexOfRefraction; }; ColorOrTexture could be color or 2d texture, if there would be single colorOrTex then I could split into two programs,
      Also I'm going to implement transparency, I am not sure how many program that I needed

      I'm considering to maintain a few default shaders for COMMON profile,
      1-no-texture, 2-one of colorOrTexture contains texture, 3-........

      Any advices in general or about how to optimize/split (if I need) these shaders which I provied as link?
      What do you think the shaders I wrote, I would like to write them without branching if posible,
      I hope I don't need to write 50+ or 100+ shaders, and 100+ default programs

      PS: These default shaders should render any document, they are not specific, they are general purpose...
             I'm compiling and linking default shaders when app launched

    • By CircleOfLight97
      Hi guys,
      I would like to contribute to a game project as a developer (open source possibly). I have some experiences in C/C++ in game development (perso projects). I don't know either unreal or unity but I have some knowledges in opengl, glsl and shading theory as I had some courses at university regarding to that. I have some knowledges in maths and basic in physics. I know a little how to use blender to do modelling, texturing and simple game assets (no characters, no animation no skinning/rigging). I have no game preferences but I like aventure game, dungeon crawler, platformers, randomly generated things. I know these kind of projects involve a lot of time and I'd be really to work on it but if there are no cleary defined specific design goals/stories/gameplay mechanics I would like to not be part of it x) and I would rather prefer a smaller but well defined project to work on that a huge and not 'finishable' one.
    • By gamesthatcouldbeworse
      Hi, I finally released KILL COMMANDO on gamejolt for free. It is a retro-funsplatter-shooter with C64 style. Give it a try.
  • Popular Now