GPL Track Creating - trk23dow.cfg

From Grand Prix Legends Wiki
Revision as of 05:40, 6 May 2009 by David Fletcher (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Authored by the GPLEA


trk23dow.cfg

This file contains a few 0/1 options that let you change how much output trk23dow produces. WARNING ! If you set everything to 1, it is unlikely that you will be able to load the output file because of its size! A default trk23dow.cfg is included with the trk23dow download.


Options

1 ;slu output

0 ;trackloading

0 ;tracksaving

0 ;trackside objects

0 ;polygons

0 ;texture stuff

0 ;*serious* amount of output

0 ;groove related

0 ;grid/sf line related

0 ;extremities listings

0 ;strings

1 ;sound

0 ;lists (vertices, planes, etc.)

0 ;t15 stuff

0 ;node tree listing

slu output = section look up; this is how corners are broken into smaller pieces

trackloading = output information when loading a track.trk/.3do

tracksaving = output information when saving a track.trk/.3do

trackside objects = output information about the trackside objects referenced in <trackname>.tso, where they are placed...

polygons = information relating to the polygons generated (lots of polygons get generated!)

texture stuff = exactly as it says- textures, texture coordinates

serious amount of output = everything else, which can be quite a lot

groove related = surprisingly, this is the information relating to the racing groove (<trackname>.grv)

grid/sf line related = the sf line is created right at the end of the track, the grid boxes are created according to <trackname>.ini

extremities listing = an output of the coordinates at the extreme left and right of your track

strings = all strings used, e.g. .mip names, .3do names

sound = sadly no longer with us due to the port to windows :(  aaah, the good ol' days when trk23dow could rival a Spectrum loading symphony :-)

lists (vertices, planes, etc.) = big lists, fairly boring

t15 stuff = t15 boxes cover the entire track and are used for the trackside objects. Too many will slow your track down, too few make it look crap in the corners.

node tree listing = every polygon in your track hangs off a big tree structure (that is actually circular in places - go Papyrus! ;)


Updated 7-Jan-2001

Transferred to the wiki: 19.04.2009