Hey there, I’ve got a few feature requests for the profiler in FMOD Studio:
Ability to filter events by name in the Tracks view. Our game might have 30-50 events running at once, and it gets difficult to find the ones we want to see in the profiler.
Set and keep default height of all tracks. Would be great to be able to set the track height for all tracks to a specific value, and have that act as a default for all future profiler sessions in the same project, instead of having to shift-select all of them and set it every time.
Would love to be able to view the API calls and the Tracks view at the same time, either stacked or with the API calls as a separate window.
Would be nice to be able to view parameter changes over time as line graphs in the Tracks view.
Search for events with a particular name in the events browser, then click and drag those events from the browser onto a profiler session to make the profiler session display tracks for those events. (You may also want to hide the profiler tracks of all other events first by right-clicking on one of them and selecting “Remove All Tracks” from the context menu.)
Alternatively, switch the profiler to the “table” view, use the search bar to filter the view to the specific events you want to see, then use the eye-shaped toggle buttons on each line of the table to choose which events should or shouldn’t be visible in the tracks view.
However, these workarounds are not as convenient as having a search bar in the tracks view would be. I’ve therefore added you to the list of people who’ve requested “tracks view search bar” as a new feature.
We already have this feature.
To set the heights of all tracks in a profiler session without having to Shift+select all of them, select the profiler session, then select “View > Set Track Height” and select the track height you’d like the profiler session to use.
To set the default track height to be used for future profiler sessions, select “View > Set Standard Track Height,” and select the track height you’d like future profiler sessons to use. Do note, however, that the standard track height also applies to the tracks of events, not just tracks of profiler sessions.
I can see how that would be useful. I’ll add this suggestion to our feature and improvement tracker.
We already have this feature. To view the parameter values of an event instance as line graphs in the profiler, select the event instance (either in the lifespans view, the radar widget of the overview pane, or the radar widget that appears in the deck when the event’s track is selected in the profiler) so that its parameters are displayed as dials in the deck, then right-click on the relevant parameter’s dial and select “Show Graph” from the context menu.
You can also select “Show Graph for All Instances” from the context menu to see a graph of the the parameter’s value for all instances of the event, but this may result in significant visual clutter if many instances of the event were played during the recording of the session.