-
Senior Member
Weird Impulse Trigger problem
http://xboxdvr.com/gamer/Core2TOM/video/19910839
hmm im not sure how to describe the problem (and i realized my console was set to german after i uploaded the video, oops) nvm
i got 3 curved datasources here. on the left the datasource [150] is the speed. for each curve i multiply the speed with 1, 2 or 3, because i set a new start value in the curve... thats not really important.
150 ticks is the duration for curve1 and then i need this value x3 and need to set a new start value for the curve, so i used the ticks in the datasource on the impulse trigger for offset and duration. (kinda the same for curve2) now the weird thing is when i restart the track once its broken: it takes at least twice as long for the impulse trigger to send an impulse even if values are all correct. when i press restart twice its working again
any idea whats the problem? i think im using 4 or 5 impulse triggers total
-
Trials Developer
Not sure what's actually going on in there, but I'll have a look when I've got time.
-
Senior Member
hi mutetus,
i already found another solution. now im using just 1 impulse trigger for everything + some impulse delay filters and it seems to work.
hmm maybe the problem was the same value for offset and duration on the impulse trigger and the tickcount wasnt reset correctly after restarting the track once (?) im not sure, i couldnt recreate the problem in a new track.