Version 0.1 4.26.00
Information herewithin obtained by using N3Def V1.6 on NL tracks
-Larry Currie April '00

Nascar Legends File Formats Document

***Track.trk

Surfaces
46	Asphault (Like at Greenville-Pickens)
54	White Line Seperating track from Apron (Like at Greenville-Pickens)
6	Grass -Seems to be used as Dirt at Riverside though
30	White Line (Atl,Bris)
38	A different traction, seen as apron/pitlane at most tracks.
22	Kerbing Grass (Bowman)

Wall Type
0	Sets boundary for Outside of the Track
4	Sets boundary for Inside of Racing Track
6	Lower "Step over" style Pitwall (Though it may be used as some sort of pitlane indicator as 4 is used at the start & end of Pitroad)
Have seen 6-0 on the turn-straight section for turns and 0-0 combos in turns completely surrounded by other turns
In General, however, use 0 for the outside (non-pit) side of the track and 4 for the inside wals.

***Track.txt
TTYPE - For some reason the standards here are a bit muddy.  Shorttracks and Roadcourses are defined yet midsized tracks have type 1 & 2 while 2.5mi Ontario also takes 2 yet 2mi Michigan gets a 3 like Talladega.  This bizarre phonenom is repeated in N3.  The only noticable diff. between Tally and the other T3's is the SPDWY 1 for Tally&Daytona, 0 for others

	0 Shorttrack (Bristol)		No Wings
	1 Intermediate (only @ Rocking)	Wings
	2 Midsize (Atlanta,Ontario)	Wings
	3 Superspeedway (Talladega,MI)	Wings
	4 Roadcourse			Wings
		However, TTYPE has no effect on Wings.
		Furthermore, TTYPE 1&2 appear interchangable

Based on a preponderance of evidence I must concur that the superbird wing-enable feature is defined somewhere in the track.3do files as the track.txt files do not impact the cars in a noticable way; even going as far as to replace greenvile with talladega txt's. The TRK files may play a part but I've yet to see any variance from Atlanta to Greenville.


***Bugs noticed in N3Def V1.6

Cleanup Often doesn't work.
Often dir must be set to dat file B4 it'll unpack though there is a seperate unpack dialog