Game Development Community

C++ reference

by Patrick · in Torque Game Engine · 11/08/2003 (9:06 am) · 5 replies

I would just like to know if there are any tutorials or *small* example games that I can look at to begin messing with more than just the scripts for the demo apps.

I would just like to see the minimum amount of coding for a game, and get an idea on how to go about actually coding, none of that "C like scripting language" I've been messing with so far.

I am using linux (Suse 8.2) with, I believe the 1.4.20 kernel. If it actually makes a difference I can look it up but I generally don't feel like checking it right now (gonna try to upgrade when the non-beta 2.6.* comes out for suse, or I may just use my other partition with a new distro).

I downloaded the entire development folder under suse (I like dsl + plenty of space, I also downloaded the whole games folder). I was able to compile the engine and demo's, so I think I have all I need. I also have kDevelop (need to find that tutorial laying around here to set it up).

I've already worked my way through my c++ books, so I have a general idea on what I'm doing, I just would like a small push in the right direction. I found it strange that I am having a hard time just finding a getting started with c and torque tutorial, but I do really stink at finding things.

I think I type too much. Thanks in advance.

About the author

Recent Threads


#1
11/08/2003 (12:34 pm)
There are a lot of simple example games out there... but you can't really trim Torque down and have it still be Torque. The starter FPS you get is pretty basic. If you're not familiar with game engine design techniques, you might want to look at some examples or articles.
#2
11/09/2003 (11:57 am)
How about one of those "cheat sheet" sort of things. I hate reading the doxygen whatever's.

Where is the source to the simple fps anyway, I know I compiled it somehow (using that automated script), but don't know where the actual source is located.

thanks for your reply
#3
11/09/2003 (12:39 pm)
The source code is in the engine subdirectory. The scripts and assets are in the example subdirectory.

The Doxygen stuff is a pretty decent cheat sheet, as all the commentary that's in it is also in the source... What would you want on this cheat sheet?
#4
11/09/2003 (9:25 pm)
You are going to need way more patience . . . to really "get" the entire engine is 12 - 18 months, if you can't read the docs, then you aren't going to get far because no-one is going to type up what is already available somewhere else.
#5
11/13/2003 (2:37 am)
Thanks, I'll get into it. That doxygen stuff is good, but it does seem a bit... automated. I'm getting used to it (everybody uses it). I was just thinking of something more printable, but whatever.

Thanks, now I just need a decent amount of time off from school to mess with this thing.