Shared Track Objects

[zimluura]

...some random results won't look good...

if you do it for the z rotation on the road cones it won't look as organized as it might otherwise. but may look more realistic.

...you want the track artist to be able to make sure what the users are going to see looks good.

well, it would be up to the track artist to use the random parameters if he sees fit.


i'm not trying to shout you down. i _don't_ think being able to have random parameters is of critical importance. the random-on-load road cone z-rotation would make very little difference.

but a more useful one would be for the trees (objects which there are tons of). and they shouldn't be different each track load. but every time the data changes.

if i were to attempt to switch out all the trees in the nurburgring for shared tree meshes, it would be nice to do it once, and not again if there are 7 more tree meshes added.

something like
[trees/indigenous/semiRandom]
position = 678.34, 121.342, 549.321
rotation = 0, 0, semiRandom
scale = 0.8 - 1.2 semiRandom

[street_utility/roadcone]
position = 3.21, 8.76, 18.94
rotation = 0, 0, randomOnLoad

everything with semiRandom would be randed from a constant seed. so it would be in the same position on each load, unless the data changes.

but again, it's not something of serious importance in the short term.