I noticed that on UE 4.13, FMOD folder aren’t copied to package during packaging game. I added “Additional Non-Asset Directories to Package” as described here: http://www.fmod.org/documentation/#content/generated/engine_ue4/deployment.html and this folder aren’t copied to package (Tested on Android). On 4.12 I set the same settings and it worked…
I’ve just tried this with a new 4.13 blueprint project and it worked fine here. Things to try are:
1.) Make sure FMOD is set up in the “Additional Non-Asset Directories to Package” - you’ve said you have done this already, but its worth mentioning again for anybody else having issues.
2.) Make sure you have Mobile banks exported from Studio. Keep in mind that FMOD Studio “Build” will only build for the current platform, so you might not be exporting mobile as well as Desktop. Its worth checking in explorer/finder that the directory is where you expect under your game’s content directory.
Alternatively, you can use the FMOD Studio setting “Force Platform Name” to “Desktop” if you want to use one set of banks.
3.) If you aren’t hearing sound, there might be some other problem going on unrelated to banks. Check logcat for errors to see if its failing to load banks, or if there is some other Android sound problem.
4.) A common deployment problem is blueprints that initialize before the plugins load, which won’t be able to find FMOD event references. See the “Loading blueprints before plugin load” section of deployment for info about that problem.
As I understand there was a bug in Version 1.08.11 related to Android NDK and supposedly it’s been fixed in Version 1.08.12 (I haven’t tested yet, thus saying “supposedly”)
That’s strange, it seems to imply that the GameActivity.java file hasn’t had the necessary changes added to it. That should happen since FMOD references an APL xml file that says what to add.
If you look at the game activity file in
Intermediate\Android\APK\src\com\epicgames\ue4\GameActivity.java
For the development build, you should see calls to:
System.loadLibrary(“fmodL”);
System.loadLibrary(“fmodstudioL”);
As well as:
// Initialize FMOD Studio jar file
org.fmod.FMOD.init(this);
Furthermore, there should be the following files in the intermediate directory:
Intermediate\Android\APK\libs\fmod.jar
Intermediate\Android\APK\libs\armeabi-v7a\libfmodL.so
Intermediate\Android\APK\libs\armeabi-v7a\libfmodstudioL.so
Yes, these calls are exist in GameActivity.java and files in intermediate directory also…
I’m using Launcher engine version and latest FMOD plugin 1.08.11
This looks to be related to a compatibility issue with some devices that was introduced in 1.08.11 when we updated to Android NDK r12b.
This issue is fixed in the FMOD 1.08.12, which is due for release within the next few days. If you can’t wait that long, please try rolling back to FMOD 1.08.10.