Answered
0
0

My output log on UE 4.14.3 has a lot of the same warning messages:

LogFMOD:Warning:
c:\jk\workspace\Build__1.8__UE4Libs_Win\studio_api\src\fmod_playback_timeline.cpp(1689) – 101 instantaneous transitions encountered; bailing out to avoid scheduler hang (last transition was to ‘Silent’)
LogFMOD:Warning: c:\jk\workspace\Build__1.8__UE4Libs_Win\studio_api\src\fmod_playback_timeline.cpp(1689) – 101 instantaneous transitions encountered; bailing out to avoid scheduler hang (last transition was to ‘Start’)

The only FMOD event I have with a transition named ‘Silent’ is my runStep event. I’m wondering what the warning message means and how to make it go away.

  • The Revera Corporation

    Having a very similar issue atm. :/

    [2017.03.07-02.22.36:292][ 0]LogFMOD:Warning: e:\jk\workspace\1. build_ue4_1.9_libs\studio_api\src\fmod_objectlookup.h(115) – Lookup failed for EventModel: {0045d5a3-9d16-41e2-83da-c1fe9346ce9c}

    [2017.03.07-02.22.36:292][ 0]LogFMOD:Warning: e:\jk\workspace\1. build_ue4_1.9_libs\studio_api\src\fmod_objectlookup.h(115) – Lookup failed for EventModel: {00ede36b-0c2b-4ddd-b7e4-235b5a6f3087}

    [2017.03.07-02.22.36:292][ 0]LogFMOD:Warning: e:\jk\workspace\1. build_ue4_1.9_libs\studio_api\src\fmod_objectlookup.h(115) – Lookup failed for EventModel: {010c072c-fe1d-4cf6-a20c-188265c029a8}

    [2017.03.07-02.22.36:292][ 0]LogFMOD:Warning: e:\jk\workspace\1. build_ue4_1.9_libs\studio_api\src\fmod_objectlookup.h(115) – Lookup failed for EventModel: {01ea9fb3-e88d-44aa-9c1c-c970fe3d2746}

    and many many more

  • Scott Rosenkrantz

    Have you read through this post about event lookup failed?

    http://www.fmod.org/questions/question/lookup-failed-for-eventmodel/

    They appear to be harmless warning messages when the project is opened due to an assets tag refresh before UE4 can load the FMOD banks.

  • You must to post comments
Best Answer
0
0

It looks like you may be using a transition and a marker in the exact same place on the timeline, as the warning says, it will end up bailing out to avoid the scheduler hanging and locking everything up.

The easiest way around that would be to use a loop and/or transition region with an instant send, rather than just a single transition point.

  • Scott Rosenkrantz

    Thank you!

    Update for any other spirit warriors out there who encounter this issue: The ‘Start’ and ‘Silent’ in the warning messages made me incorrectly think that the trouble-causing event contained markers named ‘Silent’ and ‘Start’. However, I noticed that I was getting the same warning messages in another level on play and discovered an event where I’m using more than one transition and marker in the same place. As a check, I removed the event from the Master Bank and those warning messages stopped!

  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.