id tech 3 game engine?
Author
well guys i am a kind of new to posting a qustion in a form and sorry if it is wrong section for this topic.my question is i have searched the id tech 3 engine hard but could not found it.?? and is it based of opengl api's for rendering? and can i gain experience if i used it as i have a basic knowledge of opengl and i can not do a great deal in opengl but i want to learn opengl because i love it.so...will id tech 3 game engine help me understand how a 3d game is made with the help of opengl?i have red book thats great but that teaches you opengl not game programming....
... 1) i have searched the id tech 3 engine hard but could not found it.??
... 2) is it based of opengl api's for rendering?
... 3) can i gain experience if i used it
... 4) i want to learn opengl because i love it.
... 5) so...will id tech 3 game engine help me understand how a 3d game is made with the help of opengl?
... 6) i have red book thats great but that teaches you opengl not game programming....
[font=arial, verdana, tahoma, sans-serif][size=2]1) You can easily find it.(<-- you want this, since it fixes a lot of the original's problems)
2) Yes, it's based on OpenGL[/font]
3) Yes, you could 'gain experience' but it would most likely be a painful one
4) Great! Then learn OpenGL in whatever language you are familiar with.
5) Probably not, since you neither know OpenGL, nor is idTech3 a good codebase to start from.
6) Yes. But you said you wanted to learn OpenGL, not game programming. Which is it?
Author
first of all...thank you..the way you clear all the things was just perfect..and yes i want to concentrate on opengl right now,,in the future yes but not now...and i am a hobbyist programmer of C/C++ for almost ten years but i came to know abt the graphics api's a year ago since then i am trying on opengl.and i understand the code examples of the red book easily..what will you suggest to me,,, reading the red book understanding it and compiling the code examples is good enough to learn opengl?????
I suggest to go through a few games and blackbox-analyze them first. Then have a look at modding. It is important to grasp the underlying problems before trying to solve them.
Reading books or compiling stuff does not make you understand anything. You have to understand the model first, the issues involved in driving a piece of real hardware, the performance pattern implications...
As a personal experience, I think that "starting from visualizing the output" is possibly an error. If I had to go back, I'd move away from graphics tests much sooner to focus on internal logic... because that's what's going to be needed.
Reading the spec... or the red book for what it counts, with no connection to the reality of problems being solved might eventually cause you to not see the bigger picture. Be careful.
Reading books or compiling stuff does not make you understand anything. You have to understand the model first, the issues involved in driving a piece of real hardware, the performance pattern implications...
As a personal experience, I think that "starting from visualizing the output" is possibly an error. If I had to go back, I'd move away from graphics tests much sooner to focus on internal logic... because that's what's going to be needed.
Reading the spec... or the red book for what it counts, with no connection to the reality of problems being solved might eventually cause you to not see the bigger picture. Be careful.
I suggest to go through a few games and blackbox-analyze them first. Then have a look at modding. It is important to grasp the underlying problems before trying to solve them.
Reading books or compiling stuff does not make you understand anything. You have to understand the model first, the issues involved in driving a piece of real hardware, the performance pattern implications...
As a personal experience, I think that "starting from visualizing the output" is possibly an error. If I had to go back, I'd move away from graphics tests much sooner to focus on internal logic... because that's what's going to be needed.
Reading the spec... or the red book for what it counts, with no connection to the reality of problems being solved might eventually cause you to not see the bigger picture. Be careful.
A good suggestion, as long as you stay away from actually trying to 'analyze' commercial game engine code - which is what the OP seemed to be suggesting he wanted to do in his first post. That... would be insanity.
Author
right now i am a little confused that what should i do either i should try out the commercial game code for learning, would it not be a little difficult for me or i should try out the opengl api's in any general problem for learning opengl and after that game programming...i think the suggestions of you both are contradicting..or it seems to me as if they are contradicting and they are not actually..what do you two experienced guys say about it..
A good suggestion, as long as you stay away from actually trying to 'analyze' commercial game engine code - which is what the OP seemed to be suggesting he wanted to do in his first post. That... would be insanity.Please suggest a better terminology. I actually meant "experimenting with content creation and see what happens". This is very important and standard. Although it is not a "true" black-box analysis in the "formal" sense of the term the amount of insight that can be gained is immense, especially in the terms of architectural design.
right now i am a little confused that what should i do either i should try out the commercial game code for learning, would it not be a little difficult for me or i should try out the opengl api's in any general problem for learning opengl and after that game programming[/quote]The two things are not comparable. Say for example you start playing with Unity or UDK. Or say you'll start creating content for ioQuake (since this thread is about id tech 3). Doing this already requires some skill and knowledge.
It's like a "spiral" path. You will approach more and more what you're trying to do. Maybe you're just really good and you will be able to go straight to the center, I don't know. Using an existing engine is nonetheless very recommended.
If you want to "[color="#1C2837"]understand how a 3d game is made", then OpenGL... or D3D for that matter, won't help you much as the rendering API is in fact minor implementation detail. Perhaps you'll become a really good graphics programmer, but for a whole game, that's only the beginning (or the last step). By the way, if you have been "[color="#1C2837"] [color="#1C2837"]a hobbyist programmer of C/C++ for almost ten years", odds are you are really code-centric, or maybe not. Feel free to elaborate!
What's the problem in what DarklyDreaming is writing? I don't see any problem.
Author
thanks for your experienced suggestions and i see no problem with what darkly dreaming is suggesting but i was a little confused now that confusion is out of the way as i am gaining more and more knowledge on this topic from you two and around the internet.i have started to learn modding and that is giving me a feel of how games are actually made but at the same time i haven't stop reading the red book and compiling its examples because i think its not bad if i learn both the API of my choice and game making...
Author
i have found a book named (focus on game mod programming in quake 3 arena written by Shawn Holmes).that is very helping book on the id tech 3 game engine and moding...so both of you guys suggestions were great and now i know what to do.thanks a lot
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
