Put official GG developer's response [here
by Berserk · in Torque Game Engine · 06/06/2006 (9:03 am) · 22 replies
Hi everyone.
I made quite a progress with Torque learning from the last time, but I still can't get some aspects
about developing with it.
Well, I tryed in all manners to have a barebone project running with Torque as tutorial.base does, but without any editor and with only 1 gui and 1 mission, without any character and neither a single dif or dts around, but just the mission as-is (with its terrain and sky, I don't mind for a waterblock).
That kind of barebone demo would be written totally by hand and without any source modification but just TorqueScript.
So, all I need to know is: what are the minimum "code requirements" to achieve something similar?
I mean, every demo has its own "client" and "server", with a bunch of functions and some support files.
What do I need to write to get a barebone demo? What do I can't forget to write down in my code editor in order to not get console warnings/errors but still keep it simple and stupid?
My goals are:
- 1 (and only 1) GUI (the main gui)
- 1 (and only 1 - completely empty) mission, with the minimum required into (eg sun, terrain, sky, etc)
- 0 (and not more than *zero*) DTSes, character included
- 0 (and not more than *zero*) DIFs
- 1 camera (I think I can't do it without at least a camera) for looking around the empty mission
And all I ask to get these is: what do I need to declare/use?
(datablocks, classes, packages, let's think about this like one would think about if him has to write all by hand - all, mission and datafiles included).
I can't find documentation about this (and I'm complaining - ignored - for this from about two years).
Bye, Berserk.
.
I made quite a progress with Torque learning from the last time, but I still can't get some aspects
about developing with it.
Well, I tryed in all manners to have a barebone project running with Torque as tutorial.base does, but without any editor and with only 1 gui and 1 mission, without any character and neither a single dif or dts around, but just the mission as-is (with its terrain and sky, I don't mind for a waterblock).
That kind of barebone demo would be written totally by hand and without any source modification but just TorqueScript.
So, all I need to know is: what are the minimum "code requirements" to achieve something similar?
I mean, every demo has its own "client" and "server", with a bunch of functions and some support files.
What do I need to write to get a barebone demo? What do I can't forget to write down in my code editor in order to not get console warnings/errors but still keep it simple and stupid?
My goals are:
- 1 (and only 1) GUI (the main gui)
- 1 (and only 1 - completely empty) mission, with the minimum required into (eg sun, terrain, sky, etc)
- 0 (and not more than *zero*) DTSes, character included
- 0 (and not more than *zero*) DIFs
- 1 camera (I think I can't do it without at least a camera) for looking around the empty mission
And all I ask to get these is: what do I need to declare/use?
(datablocks, classes, packages, let's think about this like one would think about if him has to write all by hand - all, mission and datafiles included).
I can't find documentation about this (and I'm complaining - ignored - for this from about two years).
Bye, Berserk.
.
About the author
#22
I'm just looking for a mission and how to render it. By the way, I'm using simple_misison_demo as the base and I'm simplyfing it at the minimum barebone requirements.
Thanks anyway.
Bye, Berserk.
.
06/12/2006 (10:35 pm)
No, not exactly. I already got a GUI to display in the main screen, as well as a pointer and so.I'm just looking for a mission and how to render it. By the way, I'm using simple_misison_demo as the base and I'm simplyfing it at the minimum barebone requirements.
Thanks anyway.
Bye, Berserk.
.
Torque Owner John Ervin
http://www.garagegames.com/index.php?sec=mg&mod=resource&page=view&qid=5086
That is as empty as you can get and still run torque.
To be followed by this:
http://www.garagegames.com/index.php?sec=mg&mod=resource&page=view&qid=5091
Which takes you through the process of adding basic functionality. These resources were already mentioned in this thread, just follow up on looking at them.