Lights:
Pretty straightforward, you can set a lot of options here, i wont go much into detail here, I assume u know what RGB colors, diffuse, specular and ambient values are
Code:
{
entity_name="Light_1",
type=LIGHT,
template_name="",
lt_grp=0,
srt_grp=0,
usr_flg=0,
spatialprops={
pos={
0,
0,
0
},
orient={
{
0.560152,
0,
-0.82839
},
{
0,
1,
0
},
{
0.82839,
0,
0.560152
}
}
},
lightprops={
on=Y,
color={
255,
255,
255
},
diffuse={
0.909804,
0.909804,
1
},
specular={
0,
0,
0
},
ambient={
0,
0,
0
},
direction={
0,
0,
1
},
range=2000,
cutoff=98.999985,
type=L_DIRECT,
theta=90,
atten={
1,
0,
4e-006
}
}
},



Camera and monitor
you need both to see something - u can define cameras and i think u can even swithc between them during the animation. The monitor is what u actually see on the screen.

Code:

{
entity_name="Camera_1",
type=CAMERA,
template_name="",
lt_grp=0,
srt_grp=0,
usr_flg=0,
spatialprops={
pos={
0.0,
-1028.601685,
7368.024414
},
orient={
{
1,
0,
0
},
{
0,
1,
0
},
{
0,
0,
1
}
}
},
cameraprops={
fovh=30,
hvaspect=1.333333,
nearplane=1,
farplane=1000000
}
},


I havent experimented with the cameraprops yet, but i guess u can change FOV there how about a 360° cam?

Monitor:
Code:

{
entity_name="Monitor_2",
type=MONITOR,
template_name="",
lt_grp=0,
srt_grp=0,
usr_flg=0
},



Background
Use any starsphere from the inis.
Code:
{
entity_name="starsphere_Li04_4",
type=COMPOUND,
template_name="starsphere_Li04",
lt_grp=0,
srt_grp=-100,
usr_flg=1,
flags=LIT_DYNAMIC,
spatialprops={
pos={
0,
0,
0
},
orient={
{
-0.943394,
0,
-0.331673
},
{
0,
1,
0
},
{
0.331673,
0,
-0.943394
}
}
},
userprops={
category="Prop"
}
},



Pathes:
The way to get things moving, maybe the most compicated part of this:
Code:

{
entity_name="Path_1",
type=MOTION_PATH,
template_name="",
lt_grp=0,
srt_grp=0,
usr_flg=0,
spatialprops={
pos={
0,
0,
0
},
orient={
{
1,
0,
0
},
{
0,
1,
0
},
{
0,
0,
1
}
}
},
pathprops={
path_type="CV_CROrientationSplinePath",
path_data="OPEN, {0.000000,-1000.000000,6800.000000}, {1.000000,0.000000,0.000000,0.000000}, {0.000000,-1000.000000,2000.000000}, {1.000000,0.000000,0.000000,0.000000}, "
}
},


position doesnt matter here, the important entry is this:
path_data="OPEN, ...
there is always one coordinate "{x, z, y}" followed by "{1.000000,0.000000,0.000000,0.000000}".
I dont know what the 2nd entries in the set do, but the 1st ones define the waypoints of the path.
(I need to verify if these are absolute or relative coordinates.)

You can add additional waypoints.

The ships / moving objects will be attached to the path in the "effects" section.
You can attach a camera to a path, too.


The last entry in "entities" doesnt have a "," after the closing bracket }.

------------------------------------------------------------------------------
events:

the number before each entry is the delay in seconds before it is initiated.

Starting effects:
This is used for all kinds of effects. They must have been defined in the sections above.
Code:

{
0,
START_PSYS,
{
"Ship_01_Engine_1"
},
{
duration=2400
}
},


duration is in seconds.

Rotating objects
Code:

{
0,
START_SPATIAL_PROP_ANIM,
{
"planet_watblucld_1500_4"
},
{
duration=360.1,
target_type=ROOT,
spatialprops={
axisrot={
360,
NEG_Y_AXIS
}
}
},


Used usually with planets, but it should work with any object - maybe even the camera.

Attaching objects to each other
This is used to attach an engine to a ship, rings to planets, explosions to their objects,...
a few examples:
an engine:
Code:

{
0,
ATTACH_ENTITY,
{
"Ship_01_Engine_1",
"Ship_01"
},
{
duration=360,
offset={
0,
0,
0
},
up=Y_AXIS,
front=NEG_Z_AXIS,
target_part="hpengine01",
target_type=HARDPOINT,
flags=POSITION + ORIENTATION
}
},


target_part is the hardpoint of the ship - mabe its possible to place guns on ships, too.

Pathes / Movement
moving a ship:
Code:

{
0,
START_PATH_ANIMATION,
{
"Ship_01",
"Path_1"
},
{
duration=50,
start_percent=0,
stop_percent=1,
offset={
0,
0,
0
},
up=Y_AXIS,
front=NEG_Z_AXIS,
flags=POSITION + ORIENTATION + LOOK_AT
}
},


duration is in seconds. This and the distance defined by the Path (waypoints) will be responsible for the speed of the object.

The offset entries are used to move the relative position of the attached object to the parent object.
You can give several objects the same path with different offsets to create fleets and their formations.

Set up Monitor
Code:

{
0,
SET_CAMERA,
{
"Monitor_2",
"Camera_1"
}
},
{
0,
START_PATH_ANIMATION,
{
"Camera_1",
"Path_Cam"
},
{
duration=35,
start_percent=0,
stop_percent=1,
offset={
0,
0,
0
},
up=Y_AXIS,
front=NEG_Z_AXIS,
flags=POSITION + ORIENTATION + LOOK_AT
}
},



First the Monitor is attached to the camera object, then the camera is set on a defined path -> moving camera.

---------------------------------------------------------------------------

Most of the work you'll be doing is pure trial and error so don't be afraid to experiment and don't worry about CTD's as thier par for the coarse. If you have any problems post away and I'll try and help, I'm not brilliant at them but I do know enough not to get to many CTDs

@ Bejaymac

I can't express how much I appreciate your feedback on this. This is like the "Holy Grail" to me as IT IS what makes the difference between the usual and unique.
It's like a "teaser" to wet the appetite and anticipation of the player for the "Shape of Things to come" .

Edited by - Rankor on 11/26/2006 9:25:21 AM

There are a couple of tutorials here on TLR

This is bobthedog's tutorial, it's similar to the one I posted.
This is buckaroobanzai's new room tutorial.

Between these and dozens of experiments of my own I've got a basic understanding of THN's, and I do mean basic.