Traces are not needed (and they are quite slow)
The simplest Method is
to create a "trail" in Med as a simple string
of vertecies.
(Or know the important vertecies in a more complex trail
model)
And then read out the position of the vertecies by code.
Once the player enters the trail (touching the trailobject), he is "locked" to
it. (the movement code goes into "slide on trail" mode)
The playerposition during the movement can be interpolated along
the vertecies of the trailobject.
You just need to be shure wich vertexnumbers to
use from the model.
Another method would be to export the trailobject to
a textfile, and use this textfile as basis
for the trailpositions.
he is asking if it is a possible to have a system that dynamically detects grindable angles. and yes traces are slow but your main character does 6 traces a frame, thats not that bad at all. especially in a skate game where there isnt a massive amount of other traces going on at a time.
@ OP: where did you ever get that you can only do one trace? trace 45 degrees down, if its not there, go from that point and trace downwards a few quants, do it at different angles to try to detect a curve.
