Setting up Individual Propagated Sounds and Estimating Volume - Revision history

Greebo: /* Team Alert Flags */

2009-05-30T08:28:52Z

Team Alert Flags

← Older revision		Revision as of 08:28, 30 May 2009
Line 37:		Line 37:
	This is not yet implemented, and may never be. Don't worry about it. (Default is 200 ms)		This is not yet implemented, and may never be. Don't worry about it. (Default is 200 ms)

	=== Team ~~Alert~~ Flags ===		=== Team Flags ===
	For optimization reasons, ~~suspicious~~ sounds are not propagated to AI that would not care about that sound.		For optimization reasons, sounds are not propagated to AI that would not care about that sound.

	When a sound comes from an AI, the following flags describe how AI on other teams respond to this particular sound. These flags are set or unset by putting "1" or "0" in the value spot after the flag name.		When a sound comes from an AI, the following flags describe how AI on other teams respond to this particular sound. These flags are set or unset by putting "1" or "0" in the value spot after the flag name.

	* "~~alert_same~~" : Alerts the same team (eg, cry or help)		* "prop_to_same" : Alerts the same team (eg, cry or help)
	* "~~alert_friend~~" : Alerts teams that are friends with the AI/player who made the sound		* "prop_to_friend" : Alerts teams that are friends with the AI/player who made the sound
	* "~~alert_neutral~~" : Alerts teams with a neutral relationship		* "prop_to_neutral" : Alerts teams with a neutral relationship
	* "~~alert_enemy~~" : Alerts teams that are enemies of the AI/player who made the sound		* "prop_to_enemy" : Alerts teams that are enemies of the AI/player who made the sound

	The default setting is "~~alert_enemy~~" only.		The default setting is "prop_to_enemy" only.

	=== Other Flags ===		=== Other Flags ===

Fidcal: /* Team Alert Flags */

2009-04-04T16:29:24Z

Team Alert Flags

← Older revision		Revision as of 16:29, 4 April 2009
Line 42:		Line 42:
	When a sound comes from an AI, the following flags describe how AI on other teams respond to this particular sound. These flags are set or unset by putting "1" or "0" in the value spot after the flag name.		When a sound comes from an AI, the following flags describe how AI on other teams respond to this particular sound. These flags are set or unset by putting "1" or "0" in the value spot after the flag name.

	"alert_same" : Alerts the same team (eg, cry or help)		* "alert_same" : Alerts the same team (eg, cry or help)
	"alert_friend" : Alerts teams that are friends with the AI/player who made the sound		* "alert_friend" : Alerts teams that are friends with the AI/player who made the sound
	"alert_neutral" : Alerts teams with a neutral relationship		* "alert_neutral" : Alerts teams with a neutral relationship
	"alert_enemy" : Alerts teams that are enemies of the AI/player who made the sound		* "alert_enemy" : Alerts teams that are enemies of the AI/player who made the sound

	The default setting is "alert_enemy" only.		The default setting is "alert_enemy" only.

Fidcal: /* Defining Local Sounds on the Entity */

2009-04-02T19:37:38Z

Defining Local Sounds on the Entity

← Older revision		Revision as of 19:37, 2 April 2009
Line 2:		Line 2:

	= Defining Local Sounds on the Entity =		= Defining Local Sounds on the Entity =
			In this context, ''propagate'' means transmit to AI. The audible sounds that the player hears are not propagated.
	Setting up propagated sounds in the Dark Mod works very similar to setting up audible sounds in vanilla D3. Whenever D3 plays an audible sound on an entity, there must be a "local" definition of the sound in the entity def file. This take the form of "snd_<sound name>" followed by the name of a sound shader, which is defined in detail elsewhere. When TDM plays a propagated sound, it looks for a local definition on the entity "sprS_<sound name>" for suspicious sounds, and "sprE_<sound name>" for environmental sounds (not yet implemented). This is followed by a global name for the sound, which is defined in detail elsewhere (just like sound shaders).		Setting up propagated sounds in the Dark Mod works very similar to setting up audible sounds in vanilla D3. Whenever D3 plays an audible sound on an entity, there must be a "local" definition of the sound in the entity def file. This take the form of "snd_<sound name>" followed by the name of a sound shader, which is defined in detail elsewhere. When TDM plays a propagated sound, it looks for a local definition on the entity "sprS_<sound name>" for suspicious sounds, and "sprE_<sound name>" for environmental sounds (not yet implemented). This is followed by a global name for the sound, which is defined in detail elsewhere (just like sound shaders).

	'''Subject to Change:''' In the current build, only sounds that you can actually hear can be propagated. I.e., the "sprS_<soundname>" soundprop sounds are only propagated when D3 plays an "snd_<soundname>" audible sound of the same name. A script function is planned to propagate suspicious sounds directly without the need for an audible sound, if desired. (This could be useful in using soundprop to simulate gas diffusion, AI communication, and other things).		'''Subject to Change:''' In the current build, only sounds that you can actually hear can be propagated. I.e., the "sprS_<soundname>" soundprop sounds are only propagated when D3 plays an "snd_<soundname>" audible sound of the same name. A script function is planned to propagate suspicious sounds directly without the need for an audible sound, if desired. (This could be useful in using soundprop to simulate gas diffusion, AI communication, and other things).
	'''		'''

	= Defining the "Propagated Sound Shader" or global sound definition =		= Defining the "Propagated Sound Shader" or global sound definition =

Greebo: /* How the System works */

2009-04-02T18:01:04Z

How the System works

← Older revision		Revision as of 18:01, 2 April 2009
Line 54:		Line 54:

	== How the System works ==		== How the System works ==
	~~[[Image:Spawnarg setup propagated sounds.png\|800px\|right]]~~This should illustrate how the AI sound propagation code in TDM works, based on a fictional example of a moveable book:		This should illustrate how the AI sound propagation code in TDM works, based on a fictional example of a moveable book:

			[[Image:Spawnarg setup propagated sounds.png\|800px]]

	# The moveable book collides with something. The code looks up the name of the sound shader to play.		# The moveable book collides with something. The code looks up the name of the sound shader to play.

Greebo: /* Stim */

2009-04-02T17:59:54Z

Stim

← Older revision		Revision as of 17:59, 2 April 2009
Line 50:		Line 50:
	Other flags propagation flags are planned, but not yet finalized. This spot will list additional propagation flags.		Other flags propagation flags are planned, but not yet finalized. This spot will list additional propagation flags.

	== ~~Stim~~ ==		== AI Messages ==
	~~In the final system, each sound will be~~ able to ~~carry~~ a ~~stim as well, that is applies~~ to ~~any~~ AI ~~who hear~~ the ~~sound~~.		Propagated sounds are also able to deliver a "message" to other AI. This is handled by the code and cannot be directly influenced by the mapper right now.

	== How the System works ==		== How the System works ==

Greebo: /* Soundprop Shader Examples */

2009-04-02T17:59:10Z

Soundprop Shader Examples

@@ Line 52: / Line 52: @@
 == Stim ==
 In the final system, each sound will be able to carry a stim as well, that is applies to any AI who hear the sound.
 == Soundprop Shader Examples ==

Fidcal: /* Defining the "Propagated Sound Shader" or global sound definition */

2009-04-02T15:55:52Z

Defining the "Propagated Sound Shader" or global sound definition

← Older revision		Revision as of 15:55, 2 April 2009
Line 8:		Line 8:
	= Defining the "Propagated Sound Shader" or global sound definition =		= Defining the "Propagated Sound Shader" or global sound definition =

	After defining the local sound on the entity, and referencing it to a global sound ~~defintion~~, you must enter the data for the global definition. Currently, all propagated sounds are stored in <code>/def/tdm_propagated_sounds.def</code>, although like sound shaders, soundprop shaders may be distributed among many files if desired.		After defining the local sound on the entity, and referencing it to a global sound definition, you must enter the data for the global definition. Currently, all propagated sounds are stored in <code>/def/tdm_propagated_sounds.def</code>, although like sound shaders, soundprop shaders may be distributed among many files if desired.

	If you look at that file, you can see some sounds that are already ingame. The following data may be entered for a given sound:		If you look at that file, you can see some sounds that are already ingame. The following data may be entered for a given sound:

Tels: fix file name

2008-10-25T12:27:35Z

fix file name

← Older revision		Revision as of 12:27, 25 October 2008
Line 8:		Line 8:
	= Defining the "Propagated Sound Shader" or global sound definition =		= Defining the "Propagated Sound Shader" or global sound definition =

	After defining the local sound on the entity, and referencing it to a global sound defintion, you must enter the data for the global definition. Currently, all propagated sounds are stored in /def/~~propagated_sounds~~.def, although like sound shaders, soundprop shaders may be distributed among many files if desired.		After defining the local sound on the entity, and referencing it to a global sound defintion, you must enter the data for the global definition. Currently, all propagated sounds are stored in <code>/def/tdm_propagated_sounds.def</code>, although like sound shaders, soundprop shaders may be distributed among many files if desired.

	If you look at ~~/darkmod/def/propagated_sounds.def~~, you can see some sounds that are already ingame. The following data may be entered for a given sound:		If you look at that file, you can see some sounds that are already ingame. The following data may be entered for a given sound:

	== Entitydef Name ==		== Entitydef Name ==
Line 77:		Line 77:

	The offset in dB gets added to the volume of the original sound. For example, I did this with the player footstep sounds at different movement speeds:		The offset in dB gets added to the volume of the original sound. For example, I did this with the player footstep sounds at different movement speeds:
	~~In player.def:~~

	~~"sprS_footstep_walk" "footstep_default"~~		In <code>tdm_player.def</code>:
	~~"sprS_footstep_run" "footstep_default:5~~.4"
	~~"sprS_footstep_creep" "footstep_default~~:~~-7.7"~~

	~~[[Category~~:~~Sound]]~~		"sprS_footstep_walk" "footstep_default"
	~~[[Category~~:~~Tutorial]]~~		"sprS_footstep_run" "footstep_default:5.4"
			"sprS_footstep_creep" "footstep_default:-7.7"

			{{tutorial-sound}}

Greebo at 06:51, 11 September 2006

2006-09-11T06:51:35Z

← Older revision		Revision as of 06:51, 11 September 2006
Line 84:		Line 84:

	[[Category:Sound]]		[[Category:Sound]]
			[[Category:Tutorial]]

Greebo at 06:36, 11 September 2006

2006-09-11T06:36:12Z

New page

{{Original_Reference|Ishtvan|3271}}

= Defining Local Sounds on the Entity =
Setting up propagated sounds in the Dark Mod works very similar to setting up audible sounds in vanilla D3. Whenever D3 plays an audible sound on an entity, there must be a "local" definition of the sound in the entity def file. This take the form of "snd_<sound name>" followed by the name of a sound shader, which is defined in detail elsewhere. When TDM plays a propagated sound, it looks for a local definition on the entity "sprS_<sound name>" for suspicious sounds, and "sprE_<sound name>" for environmental sounds (not yet implemented). This is followed by a global name for the sound, which is defined in detail elsewhere (just like sound shaders).

'''Subject to Change:''' In the current build, only sounds that you can actually hear can be propagated. I.e., the "sprS_<soundname>" soundprop sounds are only propagated when D3 plays an "snd_<soundname>" audible sound of the same name. A script function is planned to propagate suspicious sounds directly without the need for an audible sound, if desired. (This could be useful in using soundprop to simulate gas diffusion, AI communication, and other things).
'''
= Defining the "Propagated Sound Shader" or global sound definition =

After defining the local sound on the entity, and referencing it to a global sound defintion, you must enter the data for the global definition. Currently, all propagated sounds are stored in /def/propagated_sounds.def, although like sound shaders, soundprop shaders may be distributed among many files if desired.

If you look at /darkmod/def/propagated_sounds.def, you can see some sounds that are already ingame. The following data may be entered for a given sound:

== Entitydef Name ==
Soundprop shaders are regular entity defs that are recognized as sounds by the prefix in the name, which must be exactly this: "sprGS_<soundname>" for suspicious sounds.
For example:
entityDef sprGS_footstep_default

=== Inheritance ===
key: "inherit"
value: Name of another soundprop shader

Soundprop shader defs are treated like any other entitydef in Doom3, so a soundprop shader can inherit other soundprop shaders.

=== Volume ===
Key: "vol"
value: SWL [dB]

For these sounds to have any meaning to the AI, you must enter a volume. See below for an in-depth discussion on choosing an appropriate volume.

=== Duration ===
Key: "dur"
value: time in milliseconds

This is not yet implemented, and may never be. Don't worry about it. (Default is 200 ms)

=== Team Alert Flags ===
For optimization reasons, suspicious sounds are not propagated to AI that would not care about that sound.

When a sound comes from an AI, the following flags describe how AI on other teams respond to this particular sound. These flags are set or unset by putting "1" or "0" in the value spot after the flag name.

"alert_same" : Alerts the same team (eg, cry or help)
"alert_friend" : Alerts teams that are friends with the AI/player who made the sound
"alert_neutral" : Alerts teams with a neutral relationship
"alert_enemy" : Alerts teams that are enemies of the AI/player who made the sound

The default setting is "alert_enemy" only.

=== Other Flags ===
Other flags propagation flags are planned, but not yet finalized. This spot will list additional propagation flags.

== Stim ==
In the final system, each sound will be able to carry a stim as well, that is applies to any AI who hear the sound.

== Soundprop Shader Examples ==
In propagated_sounds.def:

\\ footstep sound
\\ note I don't need to put "alert_enemy" "1" here because that's the default.
entityDef sprGS_footstep_default
{
"vol" "42.6"
}

\\ this is a battle cry when entering combat. Should alert friends
entityDef sprGS_prelate_combat
{
"vol" "75"

"alert_friend" "1"
}

== Advanced Usage: Volume Modifier in the Local Sound Def ==
Suppose you want to add a bunch of sounds at slightly different volumes, but you don't want to create a whole new soundprop shader for each of these sounds. It's possible to use the same soundprop shader but modify the volume in your local sound definition (i.e., the sound on the entity def file). The syntax is:
* '''key''': "sprS_<local sound name>"
* '''value''': "<soundprop shader>:<volume offset in dB>"

The offset in dB gets added to the volume of the original sound. For example, I did this with the player footstep sounds at different movement speeds:
In player.def:

"sprS_footstep_walk" "footstep_default"
"sprS_footstep_run" "footstep_default:5.4"
"sprS_footstep_creep" "footstep_default:-7.7"

[[Category:Sound]]