I don’t really know how it calculates it, but I’ve always found decent values with trying. Atleast it should not be the distance between spline points. It’s not very hard to tweak when you use replace function. It’s worth to try. And I understood your splines are perfectly smooth when you check it with the spline tool in radiant?
rail gun train
isbowhten
(isbowhten)
#42
i never used wait values !
what a un-necessary thing…
i always script mvers like that.
m1 (= movement 1, is like run0, run1 etc)
{
say that this routine is used with an accum
follow the spline and wait til it reached the spline( this is what it does without wait value, just “wait”)
say that the movement is over and set the accum controlling which spline is next
}
so i never understood why to use wait values, anybody has a nice reason for?
SSF-Sage
(-SSF-Sage)
#43
[QUOTE=isbowhten;185499]i never used wait values !
what a un-necessary thing…
i always script mvers like that.
m1 (= movement 1, is like run0, run1 etc)
{
say that this routine is used with an accum
follow the spline and wait til it reached the spline( this is what it does without wait value, just “wait”)
say that the movement is over and set the accum controlling which spline is next
}
so i never understood why to use wait values, anybody has a nice reason for?[/QUOTE]
What are you saying?? Only clever wait for spline system is that wait in the followspline command. Who did say anything about a wait command? No it’s not very useful with vehicle scripting, since it tends to break the vehicle if the wait command is in the same scriptblock.
You can’t set a wait value into followspline command, it can only be wait till finish spline or wait none. We talked about lenght xxx value in the followspline command, which is there to smooth out the movement.