I'm looking for someone who is good with editing THNs.
Someone who can teach me how to write planetscape, menu, and scene scripts, or someone who can do some of those for me.
I don't really need much, just a few scripts. Would be better if someone could teach me.
Well, thats it for now. Thanks ahead!
1st decompress an existing thn file (use adoxas decompressor as it is bug free)
-> i would suggest you start working with existing files and just edit them
folllow this tutorial
QuoteDisplay More
The Basic THN File.
A Menu Screen THN will always start with duration = #. # is the amount of time (in seconds) the scene will last. A duration of 3-400 is recommended for Non-Animated menu Screens. Animated ones can be anything from 500-2000. Next we will define Entities. Entities are Objects and Effects that can be placed in the file such as planets. However, Scenes and Cameras are defined by entities as well. The Start of a THN Will often look like this:
entities={
{
entity_name="Scene_Untitled",
type=SCENE,
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
}
}
},
up=Y_AXIS,
front=Z_AXIS,
ambient={
128,
128,
128
}
},
Entity Name: the nickname of the Object or FX. This is referred to in Animation or FX scripts later, so make sure it’s clear what the object is.
Type: this effectively defines what properties the object will have. Some Objects will only be placed under certain types. Commonly used Types are SCENE, LIGHT, CAMERA, COMPOUND, PSYS and MONITOR.
Template_name: this is the template, effect, or model used. Cameras, Scenes and monitors tend not to have these. For example planet_gasgrncld_5000 would spawn a large, orange Gas Giant Provided Type was set to COMPOUND and category was set to solar. (We’ll cover category and userprops later)
Lt_grp, srt_grp and usr_flag: I’m not totally sure what these do but I assume they have something to do with lighting. Include them, otherwise entities won’t spawn, but set all three values to 0.
Spatialprops: Spatialprops covers Position and Orientation. These are very basic, following XYZ values. An Entry of 0,0,0 in Pos will mean the object is placed at the centre of the scene. Note, if a camera is not included it will automatically be placed at 0,0,0.
Up, Front and Ambient: this allows you to change where objects are quickly by reconfiguring where X,Y and Z axis are. It’s a good idea to leave them because they can cause confusion later on. Ambient is a lighting value used only in SCENE Entries.
Userprops: these are settings defined by category and Type. They include Psysprops, Lightprops and cameraprops.
Psysprops
},
psysprops={
sparam=0
}
Best left at 0. This simply needs to be included at the end of an FX entry
Lightprops
},
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
}
A Typical lightprops entry looks like the one above many are self-explanatory. Make sure to leave theta at 90 unless you know what you’re doing.
Cameraprops
},
cameraprops={
fovh=30,
hvaspect=1.333333,
nearplane=1,
farplane=1000000
}
This is the default entry for any camera. Reducing Farplane can allow for a ‘fog’ Effect when moving the camera. Changing nearplane can have a similar effect.
{ }, ={ and so on
The most unpleasant aspect of creating THN files in loading them up and finding a black screen rather than the beautiful starscape you envisaged. The most common cause of this is forgetting to close an entry. Entries are opened with a { bracket and are closed with a }, Bracket. Make sure you close entries properly.
{
entity_name="Scene_Untitled",
type=SCENE,
template_name="",
lt_grp=0,
srt_grp=0,
usr_flg=0,
spatialprops={
pos={
0,
0,
0
},
The Brackets in Red are required at the end of an entry. Note that the actual entry for the entity, and any userprops it may have such as rotation are separate. Therefore.
orient={
{
1,
0,
0
},
{
0,
1,
0
},
{
0,
0,
1
}
}
},
The Brackets in Red are required for orient, whilst the ones in blue are empty. I tend to include these out of habit, and have never had any issues with them.
={ is used to declare props or a new section. These brackets do not need to be closed For Example:
entities={
{
entity_name="Scene_Untitled",
type=SCENE,
template_name="",
lt_grp=0,
srt_grp=0,
usr_flg=0,
spatialprops={
pos={
0,
0,
0
},
The text in red is Always required at the start of a scene after duration, otherwise entities will not spawn.
Category List
Prop: Starspheres, Water
Solar: Planets, Most Stations
Psys: Effects, such as Sun FX, weapon FX and so on
Spaceship: any Ship model from Freelancer
Room: if you felt so inclined to make an indoor scene it would be possible to do so using hardpoints from the Right Folder.
Events
The events section of the file defines when, where and for how long Effects, Animation and Audio goes on for. It is headed by events={. This is where nicknames become important A Typical Events entry looks like this:
{
0,
START_PSYS,
{
"Intro_Farmoon_sun_6"
},
{
duration=360
}
},
The Name in brackets is the nickname of a sun I added in Entities earlier. Duration, is how long the sun FX will last, and the 0 at the top is the delay, allowing for creatively timed weapons/Beams/Etc. If you’ve placed a Camera and monitor, an entry like this is required:
{
0,
SET_CAMERA,
{
"Monitor_2",
"Camera_1"
}
},
Changing the Duration here will caused the Camera to jump from 0,0,0 to wherever the monitor is placed after a set amount of time.
Finally, attaching entities is important. It allows you to put engines on ships, or a glow effect on the end of a weapon. This will be covered in Advanced THN.
Tutoeials don't really help, but I'll try to follow it. Thanks for the help!
Try contacting THN master, Ruppetthemuppet over at the *port.
Yeah...... Got IP-Banned again.... Those suckers ban my IP every once-a-week, so I can enter it only 1 day a week randomly.
why dont you simply leave them alone?
The personal crap over there is in no way constructive.
Gotta admit that its pretty fun abusing them... Well, don't you worry about me OP, youre not my father are you?
Now, where were we? Right, THNs...
I dont worry, but ive pretty much experience with this personal crap aswell. It distracts from the actual work.