How "outdated" really?
by Akkuma · in Torque Game Engine · 10/03/2007 (11:21 am) · 3 replies
Hello,
First off I'd like to say that I've been researching on this forum for about 2 months now. I've read through both forums on both this book and the 3d game programming all in one. It seems both books (and the advanced gpaio) are fairly out dated.
I would like to know if this book is still fairly relevent though. Mostly interested in the torque script language and how to use it.
I come from a very limited programming background (pascal), however I'm a very strong artist and modeler. I'm currently on 2 different "teams". Both useing torque. Anyhow, I've decided to dive into torque and try to help my programmer (he's also learning torque script but is strong in c++).
Now then, is this book good for learning the current generation of torque script? Has torque script evolved enough to where alot of what is shown in the book isn't practical, or is it the other way where most of the book is fine with few changes in torque script.
The reason I'm leaning more twords this book first is because I'm already good with modeling and texturing and I don't need another book on it.
Thanks in advanced.
Nate
First off I'd like to say that I've been researching on this forum for about 2 months now. I've read through both forums on both this book and the 3d game programming all in one. It seems both books (and the advanced gpaio) are fairly out dated.
I would like to know if this book is still fairly relevent though. Mostly interested in the torque script language and how to use it.
I come from a very limited programming background (pascal), however I'm a very strong artist and modeler. I'm currently on 2 different "teams". Both useing torque. Anyhow, I've decided to dive into torque and try to help my programmer (he's also learning torque script but is strong in c++).
Now then, is this book good for learning the current generation of torque script? Has torque script evolved enough to where alot of what is shown in the book isn't practical, or is it the other way where most of the book is fine with few changes in torque script.
The reason I'm leaning more twords this book first is because I'm already good with modeling and texturing and I don't need another book on it.
Thanks in advanced.
Nate
#2
You know, one thing I like about TGE is that 'evolution' is never a issue.
10/03/2007 (2:59 pm)
Quote:Has torque script evolved enough to where alot of what is shown in the book isn't practical, or is it the other way where most of the book is fine with few changes in torque script.
You know, one thing I like about TGE is that 'evolution' is never a issue.
#3
Unfortunatly for me, I have a bad habbit of writing noodle code using boolean, hopefully torque script will help me learn more and break my bad habbit.
10/04/2007 (7:21 am)
Thats really good to hear. For me personally I don't really care if the tuturials need older versions of torque. What I'm interested in is a good resorce that lets say, I'm having problems with how to get something in the GUI to work correctly and all I need to do is find a referance to the function I need. So that I can look at how and more importantly why a certain script was used.Unfortunatly for me, I have a bad habbit of writing noodle code using boolean, hopefully torque script will help me learn more and break my bad habbit.
Torque 3D Owner Matthew Jessick
There are some sections clearly marked with methods required of older versions, but the more modern version is also given. e.g.: obsolete "first responder" considerations for user interfaces.
I use the book as a one-stop-shop with tables, charts, examples, all together, and organized in sections with a table of contents and an OK index. This makes it fast to get a basic reminder when I have a question that isn't too detailed, or I want to page through a chapter looking for a good "tool" to use.
For other things, I use the GG website search functions and page through the links looking for gems. The Website is much broader coverage (e.g.: 15 projects bearing in some way on what I'm looking for.) This is both good and bad. If I find exactly what I need, it is good. If I find 25% of what I need after a lot of digging, it is bad. Having the book available can shorten the research for small obvious projects.
The book also attempts to teach the "Torque way of doing things and philosophy". This is important because sometimes having a good feeling for this can keep you from wasting time trying to do something that doesn't fit the usual usage philosophy when the normal Torque way is adequate for your problem.