GPGT OSX Appendix E
by Christopher Tall · in Torque Game Engine · 12/10/2010 (9:05 pm) · 3 replies
Dear Torque community,
I (as everyone who uses the Guide to Torque for Programmers on the OSX) have experienced a multitude of problems with the instructions. Before accusing me otherwise, I have done some searching. I found that there exists an "Appendix E" for Mac users that fixes all the errata from the original book. However, any link directed to the download of this file brings me to "hallofworlds.com" which apparently doesn't exist anymore. In short, I can't find Appendix E anywhere on the internet! I hope that someone might direct me to the file's new location, if it has one. Thanks. :)
I (as everyone who uses the Guide to Torque for Programmers on the OSX) have experienced a multitude of problems with the instructions. Before accusing me otherwise, I have done some searching. I found that there exists an "Appendix E" for Mac users that fixes all the errata from the original book. However, any link directed to the download of this file brings me to "hallofworlds.com" which apparently doesn't exist anymore. In short, I can't find Appendix E anywhere on the internet! I hope that someone might direct me to the file's new location, if it has one. Thanks. :)
#2
12/19/2010 (12:45 am)
Well, the instructions in the book just do not work on the Mac. Also, half the torquescript examples don't work (//bt00() for instance). When I load most of the code I just get a very quick, yellow message that says it cannot find it. However, when I check the actual script, all the code is there in the correct file, in the correct folder! I've read that I will come into many more problems along the way, but the Appendix E written for the Mac will guide me through them. I just can't find it anywhere.
#3
12/19/2010 (2:40 am)
I remember there is a button in the principal (window) menu to have a console with all this examples. You can try run your scripts in this part.
Torque 3D Owner ERICK MIRANDA M
help you. And about Hall here is the link to explain what happened. You could find some documentation in this site.