255
edits
Changes
Jump to navigation
Jump to search
* It is not recommended to combine events of different banks for the engine sound.
→Event (remote/)"engine"
* The engine sound is integrated into one event (usually remote / engine). Including exhaust and turbo sounds.
* Due to the performance, the sound for the remote truck needs to be significantly simplified.
=== Event "(remote/)"engine" ===
Event "engine" plays sound of the engine of remote truck.<br>
* load<br>the value is in the range <0 - 1><br>value represents the motor load<br>value < 0.05 means idle engine sound
* rpm<br>the value is in the range <0 - 3000><br>the value represents the number of engine revs per second
* engine/turbo<br>the value is in the range <0 - 1> and represents the action of the turbo system == Remote Engine Sound Configuration == The sound configuration of the engine sounds is stored in the "accessory_engine_data" data.<br>There is array "sounds" which contents specification for the mandatory events of the engine.<br>That means that each type of the engine can have assigned its own sound bank.<br>The item "remote" has been added for the remote engine sound (since version 1.42)<br>Example:<br>There are configuration files of engines for the "Peterbilt 579" at the folder "\def\vehicle\truck\peterbilt.579\engine".<br>Each engine include ''@include "sound.sui" '' file which contents indirect definition of the events:<pre> sounds: 5 sounds[]: "engine|/def/vehicle/truck/peterbilt.579/engine/sound_engine.soundref" ... sounds[]: "remote|/def/vehicle/truck/peterbilt.579/engine/sound_engine_rm.soundref"</pre>There are .soundref file (for each event) to specify bank end FMOD event of the sound. Content of the sound_engine_rm.soundref is:<pre>"source="/sound/truck/peterbilt_579_rm.bank#remote/engine"</pre> == Engine Sound Example == Visit the [[Documentation/Engine/Sound/Downloads|Downloads]] section to get template project or sound examples.
