|
|
|
i have been trying to learn opengl for the last year or so, but most of those times i gave up and i think i now know why. i was learning it from a book which does a pretty bad job of explaining them to a beginner. nitrix from #c suggested me a playlist which builds some opengl game in java and he suggested that i get a high level overview of how things work.
two videos in + some hours of discussions on #c-offtopic and i now have a decent idea of how models are loaded, how opengl stores those objects, how it draws them by switching between array objects, how the gpu is like a server and the cpu a client, how uv mapping works, defining variables for shaders...
it's not complete by any means, there are still gaps to be filled up but now when i look at the opengl code in that book, i understand what's going on. this is same as knowing the pseudocode of some algorithm and then reading it's implementations. i think this is a good approach to learning new things, directly jumping into the code in such cases is a bad idea.
and i am excited to learn more and put what i have learnt into code which matters a lot when learning new things. good mentors like nitrix are a blessing who, for hours, answer all your silly half-baked questions.
