# (Unity) Linux Player looking for libresonanceaudio.so in incorrect directory

**URL:** <https://qa.fmod.com/t/unity-linux-player-looking-for-libresonanceaudio-so-in-incorrect-directory/24318>\
**Category:** Unity\
**Tags:** unity\
**Created:** [June 5, 2026, 11:11am UTC](https://qa.fmod.com/t/unity-linux-player-looking-for-libresonanceaudio-so-in-incorrect-directory/24318 "2026-06-05T11:11:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![BeefyAndTheDucks](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@BeefyAndTheDucks](https://qa.fmod.com/u/BeefyAndTheDucks)\
**Post date:** [June 5, 2026, 11:11am UTC](https://qa.fmod.com/t/unity-linux-player-looking-for-libresonanceaudio-so-in-incorrect-directory/24318/1 "2026-06-05T11:11:41Z")

</div>

So I’m developing my game for Linux using FMOD and Resonance Audio.  
After building my game (for Linux) and hitting play, I get an issue loading the `libresonanceaudio.so` file. FMOD seems to be looking in (relative to the build directory) `Whatever_Data/Plugins/` instead of `Whatever_Data/Plugins/x86_64` on Linux.  
A current workaround is in `PlatformLinux.cs`, changing out the `GetPluginPath(...)` function (line 82-85) to this:

```cs
internal override string GetPluginPath(string pluginName)
{
    return string.Format("{0}/{1}/lib{2}.so", GetPluginBasePath(), RuntimeUtils.GetPluginArchitectureFolder(), pluginName);
}

```

Note that it’s now also looking inside the `Whatever_Data/Plugins/{RuntimeUtils.GetPluginArchitectureFolder()}/`, instead of directly inside `Whatever_Data/Plugins/`.

---

<div class="post-metadata">

**Author:** ![Connor\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/connor_fmod/32/3685_2.png) [@Connor\_FMOD](https://qa.fmod.com/u/Connor_FMOD)\
**Post date:** [June 7, 2026, 11:44pm UTC](https://qa.fmod.com/t/unity-linux-player-looking-for-libresonanceaudio-so-in-incorrect-directory/24318/2 "2026-06-07T23:44:47Z")

</div>

Hi,

Thanks for bringing this to our attention and sharing your workaround.

I could not reproduce the issue testing Unity 6.3 and FMOD Integration 2.03.14. I checked the resonance plugin was found in:

```auto
/UNITY_PROJECT/UNITY_PROJECT_Data/Plugins/libresonanceaudio.so

```

This is with the default player settings, have you made any changes to the project to make it build to an `x86_64` folder? Would it be possible to share the full build logs as well?

---

<div class="post-metadata">

**Author:** ![BeefyAndTheDucks](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@BeefyAndTheDucks](https://qa.fmod.com/u/BeefyAndTheDucks)\
**Post date:** [June 8, 2026, 6:37pm UTC](https://qa.fmod.com/t/unity-linux-player-looking-for-libresonanceaudio-so-in-incorrect-directory/24318/3 "2026-06-08T18:37:46Z")

</div>

Hi, thanks for the response 🙂  
I was getting the error with Unity 6.4 (I’ve since upgraded to Unity 6.5), using FMOD 2.03.13 (Unity Verified).  
I seem to have failed to mention that I’m running the Unity Editor on Linux, sorry about that 😅.  
I haven’t made any changes to settings to save to a platform-specific folder.

I’ve noticed that `PlatformWindows`’s GetPluginPath is very similar to the one I’ve provided.

> ```cs
> internal override string GetPluginPath(string pluginName)
> {
> #if UNITY_STANDALONE_WIN
> return string.Format("{0}/{1}/{2}.dll", GetPluginBasePath(), RuntimeUtils.GetPluginArchitectureFolder(), pluginName);
> #else // UNITY_WSA
> return string.Format("{0}.dll", pluginName);
> #endif
> }
> 
> ```
> 
> `PlatformWindows.cs`

I can’t share full build logs (I can only find Editor.log) since it’s 2.9MiB and I can’t as a new user upload attachments, and Pastebin won’t accept it.

---

<div class="post-metadata">

**Author:** ![Connor\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/connor_fmod/32/3685_2.png) [@Connor\_FMOD](https://qa.fmod.com/u/Connor_FMOD)\
**Post date:** [June 9, 2026, 3:49am UTC](https://qa.fmod.com/t/unity-linux-player-looking-for-libresonanceaudio-so-in-incorrect-directory/24318/4 "2026-06-09T03:49:45Z")

</div>

Hi,

Thanks for the info, I was also testing on Linux `Ubuntu 24.04.4 LTS`, the missing link was Unity `6.4` I was able to reproduce the issue.  
I will make a task to add your workaround. Thank you for bringing this to our attention.