# FMOD Plugins on OSX, .bundle or .dylib?

**URL:** <https://qa.fmod.com/t/fmod-plugins-on-osx-bundle-or-dylib/12602>\
**Category:** Unity\
**Created:** [July 18, 2016, 10:20am UTC](https://qa.fmod.com/t/fmod-plugins-on-osx-bundle-or-dylib/12602 "2016-07-18T10:20:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rory](https://avatars.discourse-cdn.com/v4/letter/r/a183cd/32.png) [@rory](https://qa.fmod.com/u/rory)\
**Post date:** [July 18, 2016, 10:20am UTC](https://qa.fmod.com/t/fmod-plugins-on-osx-bundle-or-dylib/12602/1 "2016-07-18T10:20:53Z")

</div>

I’m having some trouble getting FMOD Unity to see custom plugins. It seems to want .bundles, but the API projects for OSX only create .dylib files. I tried adding the fmod\_noise.dylib to a folder named fmod\_noise.bundle with the following folder structure:

```
fmod_noise.bundle
               ->Contents
                       ->MacOs
                            ->fmod_noise.dylib

```

But that didn’t seem to do the trick. Any ideas? It would be nice if the plugin example projects in XCode created .bundles if that’s what the FMOD Unity Integration packages expects?

---

<div class="post-metadata">

**Author:** ![nick1](https://avatars.discourse-cdn.com/v4/letter/n/47e85d/32.png) [@nick1](https://qa.fmod.com/u/nick1)\
**Post date:** [July 22, 2016, 6:40am UTC](https://qa.fmod.com/t/fmod-plugins-on-osx-bundle-or-dylib/12602/2 "2016-07-22T06:40:55Z")

</div>

FMOD itself can load both standalone dylibs and bundles.

The issue is that Unity only recognizes and copies bundles to the standalone app.

With your bundle try removing the .dylib extension from the file.

---

<div class="post-metadata">

**Author:** ![rory](https://avatars.discourse-cdn.com/v4/letter/r/a183cd/32.png) [@rory](https://qa.fmod.com/u/rory)\
**Post date:** [July 22, 2016, 11:40am UTC](https://qa.fmod.com/t/fmod-plugins-on-osx-bundle-or-dylib/12602/3 "2016-07-22T11:40:46Z")

</div>

> [@](#):
>
> FMOD itself can load both standalone dylibs and bundles.
> 
> The issue is that Unity only recognizes and copies bundles to the standalone app.
> 
> With your bundle try removing the .dylib extension from the file.

Perfect. I haven’t had a chance to give this a full test, but Unity no longer complains about not being able to find the plugin. Thanks again.