[Csantucci]

True, however after Peter's words I would suggest to start implementing echo (if possible) or at least an increased sound volume in tunnels. That shouldn't be too difficult maybe. When I had only one type of motor sound for the Bernina trainsets, I added a speed-related motor sound to the track sound within the Bernina route tunnel MSTS sound regions, and the effect was quite nice. (But developing further motor sounds I had to remove this feature...). When OR will extend MSTS file formats, maybe one could think to insert into sound regions some echo-related parameter. This way no complicated computations should be performed to understand if there are nearby vertical surfaces or not.

[disc]

why don't you just make the sound file itself echoed?

[Csantucci]

Because e.g. the horn has to be normally not echoed, and has to be echoed when the surroundings provide an echo. So, how can you select which horn (echoed or non-echoed) to play, if there is no provision within the game to decide where to echo and where not to echo?
I e.g. have created some echoed sound for station announcements, because they are static sounds, that are always echoed. But a horn is a moving sound...

[Shay 5]

It would sound really weird to be right next to the engine and it sounds like your in a canyon. :sign_thanks: Plus, Putting an echo on the end of the horn/whistle files will decrease the ability to have a nice short blast when doing the grade crossings, or the various signaling blasts.The echo needs to be affected by distance and land features.

[gpz]

jantonio, on 06 March 2014 - 02:16 PM, said:

Will be the echo available in next experimental version?

Of course not. It needs some development work to implement, and I haven't even started it.

[That Genset Foamer]

Echo can be created by adding a PlayOneShot trigger at the end of the horn effect. Gallo Locomotive Works does this with a number of experimental soundsets. I'll talk with the "head honcho" and see if he's chill with me doing aftermarket soundset upgrades on a case-by-case basis.

As for the ORTS echo function, could that be achieved by detecting collision objects or terrain objects within a certain azimuth of the locomotive? In theory it could be bundled with a quill upgrade. Here's how it could work:

> outside .sms file calls a file "*****.wav", for the sake of this example it is called called "x_K5LA.wav".
> When Spacebar is pressed, "x_K5LA.wav" is played for duration of press.
> When ALT + Spacebar is pressed, "x_K5LA_alt.wav" is played. This can be a quill blast, a "backup horn", or a lower-tone horn depending on what the user wishes. CTRL and Shift could also have bindings.
> When a collision object or terrain object's hitbox is in the hemisphere above the train, it plays a file titled "x_K5LA_echo.wav" when the loop is released.

This would solve the problem of the "sander quill", and as opposed to the 2-key quill system in Railworks which chews up a key binding that could be reserved for a different function.