Track system

[zorbulator]

Currently, the tracks are distinguished by their name, which has a few problems:

• Track/location names should have capitalization, filenames, and be long, but file names should not have those things so if they have to match one of them must be incorrect
• Track metadata such as checkpoints, textures, etc. is hard to store because there would have to be a separate table to store this based on the names that would be updated

To fix this and make the code simpler, there should be an array of objects for the locations, each containing at least a name and array of track objects, which each would have checkpoints, ONE model, textures, maybe a name, etc. This way we could more easily edit and add tracks, and the track selection system could use it in order to make the track selector automatically add new tracks.

[zorbulator]

This is important because we are adding tracks now and it will be easier to make a track system before we set up the tracks with a bad system

[zorbulator]

The way we have it now works fine, this is still something we could do but it's not super important. We could at least have the name of the track be for example San_Francisco and then have it get the file sanfrancisco.obj and display San Francisco by changing the string a little