This was discussed on the forum recently. (We heard that the techniques used in some countries may lead to a reduced "chuff" rather than no "chuff".)
- MSTS hushes the "chuff" sound when the throttle is closed in a moving steam loco and OR does not.
- OR works differently and plays whatever is in the sound file as modified by the Variable2, which reflects the work done by the loco.
We should, of course, hush the chuff when coasting but there are opposing ways to resolve this:
We have faced this sort of dilemma several times before, with strongly-held views on both sides of the debate. The modellers naturally want to protect their investment in MSTS-compatible models whilst the coders want to keep the code free from MSTS quirks. Previous examples of this dilemma include:
B. the detailed behaviour of activities
Carlo provided us with a way through this dilemma for B: activities with a new checkbox - Enhanced compatibility with MSTS activities.
This allows MSTS users to put off making OR-specific changes to their models and marks MSTS-specific code as separate from the mainstream.
I recommend that we adopt Carlo's solution and rename this checkbox as just "Enhanced compatiblity with MSTS" and extend it to hush the chuff
(and possibly limit the smoke too). I shall add a comment to the bug report for this.