Hello, and can I be of service?

[thelusiv]

So far I understand it to create/edit the roads.trk, track.txt, and possibly the objects/list.txt.

Spot on.

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.

By the way, did you see Joe's reply to you on the wiki? http://wiki.vdrift.net/Talk:Track_files_and_formats

That would require an overhead/3d movable rendering of the surface and some point selection - not too hard.

In the new PyGTK track editor, the 3D surface rendering is done. That's about it, however...

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).

Correct. This file is in the VDrift CONFIGFILE format, even though it doesn't have a .config extension (that should get fixed...)

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.