info_train_spline_control not really working for me

(pazur) #1

I’m tweaking the path of the tank in my map and added info_train_spline_control entities. The path looks really smooth in GtkRadiant, but in the game the tank makes fast “epileptic” movements. I’m using one control entity per main entity. Any idea? Anyone seen that before? Do I need two control entities for each main entity?

(-SSF-Sage) #2

This is actually what happens when you don’t give the followspline command a length parameter. 32, 64 and 128 are good values for most of the vehicles. I’ve used 32 or 64 on straight path and 128 on bigger curves, altho I will not guarantee the difference. You only need control when you want to smooth down the curves, and when you have a bumby road.

(pazur) #3

Cool. The scripting reference says:

followspline <direction|accum <buffer_index>|globalaccum <buffer_index>> <targetname> <speed> [wait] [length <value>] [roll <start_angle> <end_angle>]

My triggers look the following:

trigger run_8
{
	trigger self tracks_forward
	accum 1 bitset 2
	followspline 0 spln8 80 wait
	accum 1 bitreset 2

	trigger self run_continue
}

Is the correct use: “followspline 0 spln8 80 wait length 64” ?

(pazur) #4

I just tried it out… length 64 makes the tank movement look really nice. Thanks a million Sage!

(-SSF-Sage) #5

You’re welcome. Glad that It helped. I had a war against it too until I found the reason.

(isbowhten) #6

i do not think that this was the mistake…
if he has a wait it is supposed to wait until it reached the spline…
when i had the problem i used accums to prevent the same movement to be triggered again or prevent the next movement to start… that fixed the problem.
actually wait x does the same in this case…
but i think that you dont need a specific wait

(-SSF-Sage) #7

[QUOTE=isbowhten;178122]i do not think that this was the mistake…
if he has a wait it is supposed to wait until it reached the spline…
when i had the problem i used accums to prevent the same movement to be triggered again or prevent the next movement to start… that fixed the problem.
actually wait x does the same in this case…
but i think that you dont need a specific wait[/QUOTE]

Erm it is. Seems to me that you didn’t understood the real problem. And yes, it will read the rest of the command even when it has a wait. It will just wait until it hits the next line. The problem was it goes like almost whole turn without turning, then all suddenly it turns all instantly. The lenght makes it turn for whole turn slowly and smoothly.

Edit and the wait is almost must, as ppl will adjust the b_moverscale, resulting the tank going faster/slower.

(isbowhten) #8

hm… i never used a wait x only a wait +nothing command after followspline and my movers move fine

(-SSF-Sage) #9

They move with the wait and it will wait executing the NEXT LINE until it hits the destination. The lengt <value> is there to smoothing out on the curves or something like that.

(Flippy) #10

The length parameter is probably the number of times the mover checks it’s position in relation to the spline. If you have a length of 1 it will only check it’s position once and not turn properly. If you have a length of 50 it will check it’s position 50 times and re-align itself with the spline 50 times --> a smoother turn.

(I think! Seems most obvious)

(pazur) #11

The tank is turning really smooth with the value of 64. Looks really kind of “realistic” :wink: