What's the best way to learn it?
by Ben Greenholtz · in Torque 3D Beginner · 11/30/2011 (6:33 am) · 4 replies
I was wondering what you guys think the best way to learn to program using T3D is. I know for "languages" most people say learn to make tetris, then mario, then blah blah blah, but since this is 3D, should I start elsewhere?
And if possible I would like the entire experience to be digital, no paper books.
And if possible I would like the entire experience to be digital, no paper books.
About the author
#2
11/30/2011 (10:35 pm)
I have done most of the FPS Tutorial, but it seemed like it was learning how to insert and understand code, not really write it yourself. I'll have to check out the official documentation. Thanks
#3
For me, when I started, it was experimentation and modding experience with it's ancestor that led me to utilizing Torque. When I wanted to implement some specific task or feature, a search through the forums (for information) and expecially the Resources (for examples) were and still are a great way to understand how things fit together. Having some knowledge of C++ and other programming languages is a plus when it comes to understanding the example code and writing your own.
12/01/2011 (10:55 am)
Quote:Exactly the issue I thought the "from the ground up" Tutorial was supposed to defeat...
I have done most of the FPS Tutorial, but it seemed like it was learning how to insert and understand code, not really write it yourself.
For me, when I started, it was experimentation and modding experience with it's ancestor that led me to utilizing Torque. When I wanted to implement some specific task or feature, a search through the forums (for information) and expecially the Resources (for examples) were and still are a great way to understand how things fit together. Having some knowledge of C++ and other programming languages is a plus when it comes to understanding the example code and writing your own.
#4
12/10/2011 (1:54 pm)
What I have learned from the tutorial is definitely nothing, but it's mostly, to me at least, just understanding code that has already been written. I can't always figure out how they came to x conclusion of how to "code" that line
Employee Michael Perry
ZombieShortbus