Shared Track Objects

[zimluura]

cars, carparts, tracks, trackparts sounds really good. further thought: could probably make each reference more concise by removing the data/trackparts, because everything in that list would be from that directory, so just: [street_utility/road_cone]

i'd thought allot about the randomness. ideally i could see having one that is randomized with every track load. the road cone's z rotation, for instance (then again i don't know maybe the track staff drop them with only a +/-5 degree variation in their rotation)

but then there's another possible situation where we'd be better off having a seeded random number that is consistent between level loads:
for the nurburgring we'd want to use shared indigenous tree meshes. but we'd start with maybe only 3 different pine tree meshes. so for every pine tree we'd want to randomly select a pine tree from those available, but also have that selection hold for any other time we load that track. and only if the amount of selectable trees increases would the results be different. something like srand(0), then each semi-random instance is rand() % number_of_trees_to_choose_from. so if we add more later they all propagate automatically through the rest of the ring with an even distribution. tree mesh z-rotaion would want to be that way as well. x and y rotation on trees mostly would want very slight variations. and maybe only by the artist's hand.

that was sorta wordy, did i write out that thought well?