Train-Sim.Com
MSTS Sound Design

Distance driven triggers in .sms files

Notice to all visitors and members of the Train-Sim.Com message forums:
If you plan on using a signature banner in your posts, we would like to remind you that there is a maximum size for banners. That maximum is 450 pixels wide by 120 pixels high, and not to exceed 25k. Your compliance is appreciated. FORUM RULES Problems? There are two common reasons for problems with logging in and posting messages. The first is that you are running a firewall that prevents your messages from being sent to the server. The other is that you have cookies disabled; the DCForum software requires cookies to work properly.

Previous Topic | Next Topic

Printer-friendly copy Email this topic to a friend

Reading Topic #589

Charter Member · 43 posts

Hello,
is there a way to enable a trigger by a distance driven trigger?
Take this example:Triggers ( 5
Initial_Trigger (DisableTrigger (4))
Initial_Trigger (DisableTrigger (5))
Dist_Travelled_Trigger (
Dist_Min_Max ( 50 60 )
Volume_Min_Max ( 1.0 1.0 )
EnableTrigger ( 4 )
EnableTrigger ( 5 )
PlayOneShot ( 1
File ( "oneaxle1.wav" -1 )
SelectionMethod (RandomSelection))
)
Dist_Travelled_Trigger (
Dist_Min_Max ( 20 30 )
Volume_Min_Max ( 1.0 1.0 )
PlayOneShot ( 1
File ( "oneaxle2.wav" -1 )
SelectionMethod (RandomSelection))
)
Dist_Travelled_Trigger (
Dist_Min_Max ( 38 45 )
Volume_Min_Max ( 1.0 1.0 )
DisableTrigger ( 4 )
DisableTrigger ( 5 ) ))I would like that the file of trigger 4 is always played after 20 meters of the play of the file of trigger 3, but it seems that the EnableTrigger command within trigger 3 do not work.Any suggestion?Carlo

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 257 posts

RE: Distance driven triggers in .sms files

I have never managed to get a Dist_Travelled (or Random for that) to do anything other than trigger the playing of a .wav file.To achieve what you discribe at the end though try something like the following.Dist_Travelled_Trigger (
Dist_Min_Max ( 20 20 )
Volume_Min_Max ( 1.0 1.0 )
PlayOneShot ( 4
File ( "silence.wav" -1 )
File ( "silence.wav" -1 )
File ( "oneaxle1.wav" -1 )
File ( "oneaxle2.wav" -1 )
SelectionMethod (SequentialSelection))
)where "silence.wav" is a very short (I use only 0.1sec) length of silence.This will mean that after 60m travel "oneaxle1.wav" will play, after 80m travel "oneaxle2.wav" will play, then after 140m "oneaxle1.wav" will play again and after 160m travel "oneaxle2.wav" will play again, and so on.Some points to consider though. If such a trigger is used for each of a consist of many wagons the sound from each wagon will syncronise with the others. I've never managed to find a way of de-sync'ing (within a single sms). Also if the distance travelled (in my example 20m) is travelled in a time shorter than the time length of the "oneaxle" .wav files then the sounds start to back-up.

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 43 posts

RE: Distance driven triggers in .sms files

Stuart,
I was sure it were you that would answer my question. Your suggestion is what I waited for. My objective is to have flange bump sound of wagons be nearer one each other when train runs faster, without increasing frequency of sound. I will try your suggestion and report about the result.
Thank You!Carlo

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 43 posts

RE: Distance driven triggers in .sms files

Hello Stuart,
it works (I used a 30 ms length of silence - interaxle time distance on axles in same bogie at high speed). There is only a limit of 16 .wav for every trigger, but this is not too bad.
Thanks againCarlo

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 257 posts

RE: Distance driven triggers in .sms files

Pleased to be of assistance.

Alert | IP


[ Home | MSTS Forum | MSTS FAQ | File Library ] Copyright © 2004 by Nels Anderson. All Rights Reserved.

Restored from the Train-Sim.Com archive, captured May 16, 2004. About this archive.