I’m encountering very annoying bug in version 2.03.08. When I open profiler, turn on Live Update and then stop profiling FMOD Studio gets stuck - meaning if I try to switch to Editor and open any new event it doesn’t play and if I connect again with live update it doesn’t start profiling even though meters in the Mixer are reacting to the gameplay.
When I close all windows, I can’t open FMOD again, it’s always hanging in the Task manager, so I need to kill the process and then I can open it and profile again, but whenever I open editor or mixer window after profiling FMOD once again hangs and don’t let me do anything. If I’m only in the profiling window, I can connect again, but whenever I open any new window this issue occurs. Is there some workaround how to make this work? We really can’t update to the latest version because of different critical bug mentioned here: Transition Markers and Regions are not working as expected - #10 by joseph
I tried to turn off Live Update settings in the Interface tab, but no combination of settings really works for me unfortunately.
If I start to record a session “While recording” settings is always enabled even if I change the it in the settings. The only workaround is to create a new session manually and then start recording with “After recording” or “Never” set directly in the session. Whenever I have the tracks added automatically while recording, after the the profiling is finished, FMOD gets into the stuck state and I can’t play any event, or record a new session and need to kill it through window’s task manager.
I’m afraid I haven’t been able to reproduce this issue; when I test here, starting and stopping live update has no impact on whether I can audition events in FMOD Studio.
This sounds like the expected behavior? Starting or ending live update stops the profiler session from recording, so as to allow the profiler session to switch from between recording FMOD Studio’s internal FMOD Engine instance (used for auditioning events and the mixer) and the game’s FMOD Engine instance (used by the game).
I have been able to reproduce this issue, but only in the exact version that you’re using: 2.03.08. Earlier and later versions don’t seem to experience it. Switching to version 2.03.07 or 2.03.09 should allow you to avoid the problem.
