Table of Contents

Using Profiler Filter Expressions

Most of the profiling views include a filter toolbar, which includes a text field. The specified text is used to filter the content, reducing the amount of information shown in the view and making it easier to find what you're looking for. The text filter can be used by simply typing text in it, and can also be used with advanced expressions, to better control the data filtered.

Refer to Filtering the Capture Log to learn more about filtering.

Below are examples of expressions that can be used in the text field:

Synopsis Description

TEXT

Matches the beginning of words found in the source content. The matches are not case sensistive.

The source content is matched to words with non alpha numeric characters and case changes.

For example, TEXT would match:

  • TEXT

  • This is some TEXT

  • textual

  • object_text

  • ObjectText

  • some1text

  • Texture

TEXT would not match:

  • context

TEXT1 TEXT2

TEXT1 TEXT2 TEXT3

As above, but all of the words specified in the filter toolbar must match in the source content.

For example, TEXT1 TEXT2 would match:

  • text1 hello text2

  • text2 hello text1

  • text1_text2

It would not match:

  • text1

*TEXT

TE*XT

Wildcard case-insensitive match. Each wildcard can match 0 to n characters. It can be used to match end characters of words, or to match the beginning and end at the same time.

For example, *TEXT would match:

  • context

  • text

*TEXT would not match:

  • text1

"TEXT"

Case-insensitive match, if and only if the source content matches exactly with the fiter criteria.

"TEXT" would match:

  • TEXT

  • text

"TEXT" would not match:

  • Some text

  • textual

  • context

!TEXT

-TEXT

Excludes the specified matching source content from the results.

This option can be used with any of the other expressions in this table.

These filter criteria would omit the following source content from the results:

  • text

  • textual

  • some text

This can be combined to other filter expressions, by simply adding ! or - in front of the expression.

{67C4FB5B-764A-40CC-A754-1448D2B6E286} Matches the specified GUID with source content objects.

Prefixes Description
sound:TEXT

Matches the beginning of words found in the source content, for Sound names. This match is not case sensitive.

bus:TEXT

Matches the beginning of words found in the source content, for Bus and Aux Bus names. This match is not case sensitive.

target:TEXT

Matches the beginning of words found in the source content, for Event's Target object names. This match is not case sensitive.

event:TEXT

Matches the beginning of words found in the source content, for Event names. This match is not case sensitive.

go:TEXT

Matches the beginning of words found in the source content, for Game Object names. This match is not case sensitive.

fx:TEXT

Matches the beginning of words found in the source content, for Effect names. This match is not case sensitive.

rtpc:TEXT

Matches the beginning of words found in the source content, for RTPC driver names. RTPC drivers include Game Parameters, LFO, Envelopes, Time Modulators and MIDI parameters. This match is not case sensitive.

PREFIX:*TEXT

PREFIX:"TEXT"

!PREFIX:TEXT

PREFIX:{67C4FB5B-764A-40CC-A754-1448D2B6E286}

"PREFIX" can be combined to the other filter expressions listed above.