UX Improvement Suggestions – First Round

  • I’ve been using and loving FMOD for a long time, but there are several UX issues that really shouldn’t exist at this point. These aren’t “nice-to-have” ideas — they are basic usability problems that actively slow down everyday workflows.

    Here are the main ones:

  • Focus should move to the selected event after clearing search

    After searching for an event, selecting it, and then clicking the X to clear the search, the focus should naturally move to that event.

    Currently, the event is only highlighted and not focused, so I have to scroll the mouse wheel multiple times to locate the event I selected.

  • Folders should remain expanded during event search

    When searching for events, folders should always remain expanded.

    Currently, folders collapse and must be manually opened each time, which makes event search inefficient.

  • Trigger conditions must be copy/pasteable between events

    Trigger conditions should be copyable and pasteable across events.

  • Automatic “Sort by Name” option
    Sorting by name currently has to be done manually each time. An option for Automatic Sort by Name should be available.

  • Prevent accidental closing of the mini event selection window
    I’m always nervous about misclicking in the mini event selection window.
    If I click on an empty area of the window (not on an event), the window closes immediately.
    Please prevent the window from closing in this case.

  • Open events directly from the Mixer routing list
    In the Mixer’s Routing list, double-clicking an event should open that event directly in the Event window.

What do you think?
For now, I’ve intentionally limited this list to features that feel essential in a modern UX.
I sincerely hope these improvements can be considered and implemented.

Thanks for the suggestions! I’ll go through each of them in turn.

I take it you mean that the browser should scroll to keep the active item visible when the browser search terms change. I can see how that would be useful, and have added this suggestion to our feature and improvement tracker.

If I’ve misunderstood what you meant, please let me know.

I’m not sure what you mean by this, as we already have that feature: Currently, the expanded/collapsed state of a folder does not change when you change the content of the search bar - and so, if a folder is expanded, it already remains expanded when you enter a new search into the search bar or clear an existing search.

Do you mean that folders should automatically expand if any of their contents matches the search term? We did try that during an early stage of FMOD Studio’s development, but because search terms are commonly keyed into the search bar one letter at a time, and any single-letter search term is likely to match a vast number of items in the project, it had the side effect of expanding nearly every folder in the project whenever a search was performed. As that seemed undesireable, we instead implemented the “Flatten” button, which removes all folders from view and displays their contents in a flat list. Combined with search, the flatten button allows you to find items without needing to expand their containing folders.

That definitely seems useful. I’ve added it to our feature and improvement tracker.

The order of items in browsers (other than the snapshots browser) are not serialised; whenever you load a project, all (non-snapshot) browser items in that project are automatically sorted by name. As such, any change you make to the order of items within a browser only persists until you close the project.

Is that existing behavior insufficient to your needs? If so, could you please describe in more detail how you’d like the behavior to be changed?

The event selection menu is intended to function like any other menu: It remains open until you click on an item to select it, or click outside the menu to close it.

Could you please clarify where you’re clicking that causes it to close? The behavior you describe could potentially be a bug.

You can already open events in the event editor from the routing browser. To do so, right-click on the event in the routing browser and select “Open event in > Event Editor” from the context menu.

That being said, I can see how being able to just double-click on them would make things faster. I’ve added this suggestion to our feature and improvement tracker.

I apologize if any part of my message sounded awkward or unnatural due to the translator.
Thank you so much for your detailed and thoughtful response, Joseph!
I really appreciate it, and I’ll be creating and uploading a few videos based on your answer.

It seems like you understood my point about “1-1. Focus should move to the selected event after clearing search” correctly, but just in case, I made a short video to illustrate it.

“1-2. Folders should remain expanded during event search”, when performing a search, all folders should be expanded regardless of their current collapsed or expanded state. This behavior aligns with modern UX standards.

Requiring users to either manually expand folders each time or repeatedly toggle the Flatten button creates unnecessary friction.

I’ve created a video to demonstrate this issue and also attached examples from other tools for comparison. I sincerely hope this feedback can be considered and reflected in future improvements.

Regarding the “Automatic Sort by Name” option, I didn’t realize at first that the events are automatically sorted when the project is restarted. That’s great.

In addition to this behavior, it would be even better if the list were immediately sorted by name when events are created, or when they are copied and pasted. That would make the workflow feel more consistent and seamless.

I’ve made a video about “Prevent accidental closing of the mini event selection window.”
I’d like the window not to close when clicking certain UI elements inside the window.


That’s all. It would be great if this could be improved.
Thank you for considering this feedback.

It definitely sounds like we’re on the same page. Thanks for the feedback!

Thanks for the clarification! I’ve added this suggestion to our feature and improvement tracker, and attached the context you provided about other applications.

Thanks, I’ll add this suggestion to our feature and improvement tracker.

Thanks for the clarification. That looks like a bug, so I’ll add it to our bug tracker.

Thank you for giving us feedback! It’s always good to know ways in which FMOD Studio could be improved. If you have more suggestions, please don’t hesitate to let us know.