Community Q&A

Welcome to Audiokinetic’s community-driven Q&A forum. This is the place where Wwise and Strata users help each other out. For direct help from our team, please use the Support Tickets page. To report a bug, use the Bug Report option in the Audiokinetic Launcher. (Note that Bug Reports submitted to the Q&A forum will be rejected. Using our dedicated Bug Report system ensures your report is seen by the right people and has the best chance of being fixed.)

To get the best answers quickly, follow these tips when posting a question:

  • Be Specific: What are you trying to achieve, or what specific issue are you running into?
  • Include Key Details: Include details like your Wwise and game engine versions, operating system, etc.
  • Explain What You've Tried: Let others know what troubleshooting steps you've already taken.
  • Focus on the Facts: Describe the technical facts of your issue. Focusing on the problem helps others find a solution quickly.

Unreal Engine 4.15 integration "IO Device error" and "Bank Load Failed"

0 votes

We are encountering the following problem at the moment (using Unreal Engine 4.15.1 and the latest integration):

Some sound banks (not always the same ones, also not dependent upon size it seems) fail to load with the following messages:

LogAkAudio:Error: IO device error
LogAkAudio:Error: Bank Load Failed

In a development build, this lead to the sounds simply not working. A shipping build even crashes with the following log:

[2017.04.13-10.49.09:787][340]LogWindows:Error: === Critical error: ===
[2017.04.13-10.49.09:787][340]LogWindows:Error: 
[2017.04.13-10.49.09:787][340]LogWindows:Error: Fatal error!
[2017.04.13-10.49.09:787][340]LogWindows:Error: 
[2017.04.13-10.49.09:787][340]LogWindows:Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION writing address 0x812c8000
[2017.04.13-10.49.09:787][340]LogWindows:Error: 
[2017.04.13-10.49.09:787][340]LogWindows:Error: VCRUNTIME140.dll!0x00000000FA22C387
[2017.04.13-10.49.09:787][340]LogWindows:Error: ShooterGame-Win64-Test.exe!FAsyncBufferedFileReaderWindows::Read() [f:\stable\engine\source\runtime\core\private\windows\windowsplatformfile.cpp:390]
[2017.04.13-10.49.09:787][340]LogWindows:Error: ShooterGame-Win64-Test.exe!FGenericReadRequest::PerformRequest() [f:\stable\engine\source\runtime\core\private\genericplatform\genericplatformfile.cpp:175]
[2017.04.13-10.49.09:787][340]LogWindows:Error: ShooterGame-Win64-Test.exe!FAsyncTask<FGenericReadRequestWorker>::Abandon() [f:\stable\engine\source\runtime\core\public\async\asyncwork.h:305]
[2017.04.13-10.49.09:787][340]LogWindows:Error: ShooterGame-Win64-Test.exe!FQueuedThread::Run() [f:\stable\engine\source\runtime\core\private\hal\threadingbase.cpp:442]
[2017.04.13-10.49.09:787][340]LogWindows:Error: ShooterGame-Win64-Test.exe!FRunnableThreadWin::Run() [f:\stable\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:76]
[2017.04.13-10.49.09:787][340]LogWindows:Error: ShooterGame-Win64-Test.exe!FRunnableThreadWin::GuardedRun() [f:\stable\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:33]
[2017.04.13-10.49.09:787][340]LogWindows:Error: KERNEL32.DLL!0x000000002E2F8364
[2017.04.13-10.49.09:787][340]LogWindows:Error: ntdll.dll!0x0000000030C170D1
[2017.04.13-10.49.09:787][340]LogWindows:Error: ntdll.dll!0x0000000030C170D1
[2017.04.13-10.49.09:787][340]LogWindows:Error: 
[2017.04.13-10.49.09:787][340]LogWindows:Error: Crash in runnable thread PoolThread 5

What we tried so far:

  • Regenerating sound banks
  • Decreasing sound bank size (thinking it was a memory problem)
  • Disabling async loading
  • Increasing the default pool size for sound banks

We would be very grateful for any hints on how to proceed with this problem.

in General Discussion by Thomas S. (150 points)

1 Answer

+1 vote
 
Best answer
We are seeing a crash with "Event Driven Loading" enabled, have you tried disabling that?
by Brock H. (510 points)
selected by Thomas S.
Thanks a lot, this was in fact the solution for us. It seems like Epic has already seen errors with the system since they disable it in the 4.15.2 hotfix by default.
by Thomas S. (150 points)
Powered by Question2Answer
...