Hello, and can I be of service?

[joevenzon]

roads.txt is a list of 4x4 bezier patches making up the circuit as it's intended to be driven - I presume the 'x' and 'y' coordinates are supplied (in pairs) by the user tracing the map and the 'z' (terrain-height) values from the intersection with the surface of the track model at that point.

I'm sure you meant to type roads.trk. Also, I think the Z coordinate for each point is supplied in this file as well, as my file seems to have triples, not pairs. Otherwise I think you understand it well.

Yes, the X, Y, and Z coordinates are all supplied by the user tracing the map. When the user traces the track, they do it by selecting vertices from the existing world geometry. In every track I've seen there is explicit geometry for the left and right edge of the road surface, so this approach seems to work well (makes tracing easy because the cursor snaps to vertices) and allows for some amount of auto-tracing.

list.txt gives the models and collidablity etc. of every model that makes up the track, I'm not sure what defines their positions or whether these models are moveable or not (like a cone that can be hit and moved, a track marker or hay bale).

Correct again. Right now objects are not movable. The current track editor doesn't actually write this file, listedit does.

To elaborate a bit more, right now the blender exporter (if you run the export-all version) generates a list.txt with default properties for each object. The user then has to use listedit to set properties (for example, set all objects with grass textures to be bumpy). In a new track editor I think it'd be ideal for the user to be able to set properties from within the editor, so they never have to use listedit. The way I'd image it would work is that you can select multiple objects in the editor, either by clicking on them or by doing a "select by property" (so you could select all objects with a certain texture, for example), and then do a set property operation on the selected objects.

track.txt just defines some simple positions for start positions and some other values for the track (I expect there's more to be added here).

The lap sequence values here (example from monza):

Code:

lap sequence 0 = 0.000000,0.000000,0.000000
lap sequence 1 = 1.000000,688.000000,0.000000

Mean that for the car to complete a lap it has to pass over road 0 segment 0 and then road 1 segment 688 and then road 0 segment 0 again. The third value is ignored.