What's wrong with the NeHe tutorials?
category: general [glöplog]
Not a joke post, just me wondering.
Ok, I haven't read them much, only when I did the CloseGL demo and only 10 first chapters. Now I am doing things on my own. I don't remember them. But most people for some reason say that they suck. Why is that? Specifically?
Ok, I haven't read them much, only when I did the CloseGL demo and only 10 first chapters. Now I am doing things on my own. I don't remember them. But most people for some reason say that they suck. Why is that? Specifically?
I have to admit to that I didn't look into them since around 2003. Back then, the main problem with them was that the guy who wrote them knew less about OpenGL than I did after 3 days of learning. And the code sucked ass anyway.
What the fuck is that shit? What do you imply with that???
I hate it when the big images have me scroll horizontally to read the rest of the text that might or might not be posted here in the near future.
I hate it when the big images have me scroll horizontally to read the rest of the text that might or might not be posted here in the near future.
Optimus, the solution is easy: [image disabled]
I'm still considering making the Argon-Selenium opengl tutorials, as "competition" to the Neon-Helium ones.. =)
It probably means havoc doesn't give a shit about whether they suck or not, and that the thread is useless in his opinion and pollutes the pouet BBS.
...just a random guess...
...just a random guess...
There is nothing wrong with Nehe imo when you want to get started the easy way with OpenGL or have a glimpse. It has basic examples on all platforms that are really easy to understand.
A few lines to show newcomers how to make simple things using OpenGL, that's what it's all about. Those tutorials never claimed to be anything more.
Once that step done, you can indeed get a serious book or read the specs.
Some people hate having specs and boring serious stuff thrown at them at the begining of a learning process. I prefer this kind of "teaching" : experiment first, then learn the rules and the boring theories afterwards, once you managed to find it not too appaling. It's a good way to make sure people don't get disgusted at first contact.
On a sidenote, I know a lot of very well known groups (using OpenGL) that started with Nehe's code for their first prod(s) but they are probably too shy to admit it ;)
(I did)
A few lines to show newcomers how to make simple things using OpenGL, that's what it's all about. Those tutorials never claimed to be anything more.
Once that step done, you can indeed get a serious book or read the specs.
Some people hate having specs and boring serious stuff thrown at them at the begining of a learning process. I prefer this kind of "teaching" : experiment first, then learn the rules and the boring theories afterwards, once you managed to find it not too appaling. It's a good way to make sure people don't get disgusted at first contact.
On a sidenote, I know a lot of very well known groups (using OpenGL) that started with Nehe's code for their first prod(s) but they are probably too shy to admit it ;)
(I did)
Quote:
I'm still considering making the Argon-Selenium opengl tutorials, as "competition" to the Neon-Helium ones.. =)
Ar-Se tutorials! Do it! :D
About the subject, there is nothing wrong with tutorials. And If you want to learn the specs you can always go to the proper books.
What keops said. Nothing wrong with NeHe per se.
But that's beginner stuff, and when you try to do real shit (tm) with OpenGL, then you have to un-learn everything you read in the tutorials and find a proper way (tm) to do it. That's one of the problems with OpenGL - there's always a bazillion ways of doing the same thing, and 99% of them are crap (in performance, in stability etc.). The remaining 1% is, of course, different on each platform and graphics card that you want to support.
But that's beginner stuff, and when you try to do real shit (tm) with OpenGL, then you have to un-learn everything you read in the tutorials and find a proper way (tm) to do it. That's one of the problems with OpenGL - there's always a bazillion ways of doing the same thing, and 99% of them are crap (in performance, in stability etc.). The remaining 1% is, of course, different on each platform and graphics card that you want to support.
what havoc said *sprays natural fertilizer from multiple pipes simultaneously*
ah, ok then...
Better ask: what's right with NeHe's tutorials.
Let me start:
-they have samples in lots of languages.
Ok, I guess that ends the list.
Let me start:
-they have samples in lots of languages.
Ok, I guess that ends the list.
I still don't get what is wrong. I never got the feeling the guy knew less about OpenGL than me after 3 days of coding. Any examples? Did I learned something wrong that I have to unlearn now?
Quote:
That's one of the problems with OpenGL - there's always a bazillion ways of doing the same thing, and 99% of them are crap (in performance, in stability etc.)
So you're using ATI ?
(sorry, couldn't resist)
Its wrong because it aint direct3d
Quote:
Its wrong because it aint direct3d
lol yes
Bill Gates says Direct3D is best, so it's gotta be!
I started reading the Nehe tutorials back in... hm maybe mid 2001, by then I already knew opengl. I got the code for setting up a window (lesson2) and since then all the demo executables of all demos we actually did are actually an offspring of lesson2 (the exe name is lesson2.exe, changed to whatever the name of the demo is by ren).
Quote:
Bill Gates says Direct3D is best, so it's gotta be!
Quote:
Nothing wrong with NeHe per se. [...] then you have to un-learn everything you read in the tutorials
ah, ok, it's much clearer now :)
Navis: CODE RIPPER!1!"" ;) (i thought Life Force looked familiar)
thx to whoever fixed the image resolution shit, now I can read the thread. Also, wtf are people thinking when they send a 3200x2400 px image? I mean, why? Seriously, I cannot believe there is sceners without a clear understanding of what a pixel is, so, please tell me, why do you do it? Why?
On topic, I would use Nehe as a starting point for having an opengl project up and running with some textures. But, imho, once you are at lesson 08 stop and do not go ahead with nehe. Instead, search on the net for a way to 1. use FBOs, 2. use VBOs, 3. Use GLSL shaders. The resto of the gl api is useless, and most of the tutorials/way_of_doing_the_effects in nehe not relevant, from my point of view.
learning from nehe certainly doesnt help when it comes to learning system design :/
