[QJ-6811]

For your information, the CTN site [ "https://www.coalstonewcastle.com.au/physics/sounds/"] describes a section on "Sound and xxxxx.SMS file capabilities", aimed at use in OR.
The main aim is to understand how the various settings work in a xxxxx.SMS file, in order to be able to make and change sounds yourself, and certainly to be able to detect errors.
I also hope that some examples clarify it a bit.
(Page is still "under construction")

The table with "overview discrete_triggers" has been updated to the latest status in OR.

As an example, the steam locomotive "H6a Consolidation" on the CTN site [ "https://www.coalstonewcastle.com.au/physics/stock/"] has been modified, concerns xxxxx.SMS file and sounds.
Special attention is paid to:
> (New) Boiler Blowdown function and sounds. (key_Shift-C) (OR rel. 2020-04-19_0821 upwards)
> (New) AI or Manual firing: Possibility of "automatic firing and injector sounds" with AI firing. (OR rel. 2020-06-13_1526 upwards)
> Example of "automatic blower sounds" normally controlled by the stoker.
> Cylinder cock sounds, synchronous with wheel revolutions. (key_C)
> Chuff sounds, as an extensive and alternative example with:
. - More variation chuff sounds for better synchronization with wheel revolutions
. - With 3 Streams and Chuff sound variations for a "dynamic sound according to power" (low-normal-heavy chuffs)


> And also various examples, as explanation of the CTN sound page.


For those who want to use it, have fun!
Roger

(Post was moved to other forum)

[Robo_TR]

Hello,

what happened with sound triggers 66+67 for pantograph No. 2 ?
I see in manuals triggers for panto 1+3+4, 2 is missing.
I use a last testing version.

Thank you for the answers.

[QJ-6811]

 Robo_TR, on 24 August 2020 - 07:34 AM, said:

Hello,

what happened with sound triggers 66+67 for pantograph No. 2 ?
I see in manuals triggers for panto 1+3+4, 2 is missing.
I use a last testing version.

Thank you for the answers.

Hi,

Pantograph No. 2, Sound_triggers 66 + 67 still exist, see also the table on the CTN site. ( https://www.coalston...r-sound-events/ )

Regards, Roger

[Csantucci]

Triggers 66 and 67 aren't explicitly mentioned in the manual, however following sentence is present:
"Moreover, OR manages the extended set of discrete triggers provided by MSTSbin."
Such triggers are part of the MSTSbin extended set.

[Robo_TR]

Hi,

Table is not up to date. These triggers were working maybe at last stabilized version.
I checked it again on new testing version 218.
Triggers 45+46 are working, 67+67 not.

BR
Robert

[Robo_TR]

 Csantucci, on 24 August 2020 - 11:23 PM, said:

Triggers 66 and 67 aren't explicitly mentioned in the manual, however following sentence is present:
"Moreover, OR manages the extended set of discrete triggers provided by MSTSbin."
Such triggers are part of the MSTSbin extended set.

Hello, I am sure, in previous version, maybe 2-3 years ago, 66+67 were active without MSTS compatibility.

[QJ-6811]

Strange? Just tested in release 20200712-2351 and latest release 20200825-0806, discreate_triggers 66 + 67 work "as normal".
(Is your .SMS file OK? First check the OR log file for errors (such as "missing streams", etc.) or try as test changing the Stream with 45+46 to 66+67)

[Robo_TR]

Streams are ok, the same. Only number of trigges are changed from 45+46 to 66+67, so mistake is not in sms.
Log seems be ok too, no informations about missing or incorect trigges.
Testing version: X1.3.1-218-g984b19812.

[QJ-6811]

Also tested now in Testing version: X1.3.1-218-g984b19812, here too the discrete_triggers 66 + 67 work "as normal".

To be sure, the sounds with the Stream with discrete_trigger 45 + 46 work with pantograph_1 (Key P) and if I adjust it with discrete_triggers 66 + 67 the sound works with pantograph_2 (Key Shift-P)
Also when I create both Streams in the SMS (so 45+46 and 66+67) both work independently, so "as normal".

Don't you have the error in the .SMS file that "STREAMS" (numbers of all Stream's) has an incorrect value? (last Stream's are then not audible).
And at OR you only have 1 "Scalabiltygroup" that is used! With an "older MSTS" .SMS file this is by default "ScalabiltyGroup (5" which you must use. (For OR only you can delete the rest ....)
You had no errors in the OR-log file, but often the ")" [closing characters] are also often a problem, if they were not correct?

If the above is all right, unfortunately I don't know?

[Robo_TR]

I don't know too.
The same stream with triggers 45+46 works without any problems.
Log doesn' t report any error inside sms.
Scal. Group is of course only one, No. 5.
Brackets are also ok, see bellow.

Stream (
Skip( **** pantograf predni **** )
Priority ( 6 )
Volume (0.7)
Triggers ( 2
Discrete_Trigger ( 66 PlayOneShot ( 1 File ( "x_362_zberac_h_3kV.wav" -1 ) SelectionMethod (SequentialSelection) ) )
Discrete_Trigger ( 67 PlayOneShot ( 1 File ( "x_362_zberac_d_3kV.wav" -1 ) SelectionMethod (SequentialSelection) ) )
)
FrequencyCurve(
Variable1Controlled
CurvePoints ( 2
0.0 22050
1.0 22050
)
Granularity ( 100 )
)
VolumeCurve(
DistanceControlled
CurvePoints ( 5
0.000 1.00
12.000 0.75
20.000 0.25
28.000 0.10
33.000 0.00
)
Granularity ( 0.05 )
)
)

I think, ORTS in actual code ignorantes this two triggers.