Table of Contents

Emitter-Listener Associations

The Advanced Profiler - Emitter-Listener tab displays information about the emitter listener associations.

Interface Element

Description

Opens a search field where standard alphanumeric entries filter out unmatching elements from the view. Learn more in Using Tables.

Click the Close icon to the left of the search icon to close the search field and remove the filter.

[Note] Note

The searches do not include elements in collapsed nodes of the List View, Query Editor, MIDI Keymap Editor, and Reference View.

Click the Configure Columns... shortcut (right-click) option from the column header band.

The Configure Columns Dialog opens. Specify which columns to display and their order.

Emitter

The game object ID, or game object name, being assigned to this Emitter-Listener association as a sound emitter. Corresponds to the first argument of the SetListeners()and SetGameObjectAuxSendValues()API calls. Can be any game object.

[Note] Note

Double-clicking a listed game object in the Emitter-Listener tab will open the Voices Graph tab filtered by that game object ID.

Listener

The game object ID, or game object name, being assigned to this Emitter-Listener association as a sound listener. Corresponds to the second argument of the SetListeners()and SetGameObjectAuxSendValues()API calls. Can be any game object.

[Note] Note

Double-clicking a listed game object in the Emitter-Listener tab will open the Voices Graph tab filtered by that game object ID.

Bus

The name of the Bus associated with this object.

Level

The percentage of the send values being applied to the game object. This relates to the send volume.

Routing Type

"User-defined": associations established via the SetListeners()API call. Refers to all direct output and user-defined sends within the project. User associations can apply to any node in the voice graph.

"Game-defined": associations set using the SetGameObjectAuxSendValues()API call. Relates to the game defined sends, fully qualified tuples of GameObjectID and AuxBusID are defined entirely through the API call regardless of project settings.