# Questions about fmodstudioL.dll **URL:** \ **Category:** Unity\ **Tags:** unity\ **Created:** [January 12, 2023, 10:37am UTC](https://qa.fmod.com/t/questions-about-fmodstudiol-dll/19728 "2023-01-12T10:37:30Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![TomaszRobot](https://avatars.discourse-cdn.com/v4/letter/t/41988e/32.png) [@TomaszRobot](https://qa.fmod.com/u/TomaszRobot)\ **Post date:** [January 12, 2023, 10:37am UTC](https://qa.fmod.com/t/questions-about-fmodstudiol-dll/19728/1 "2023-01-12T10:37:30Z")
Hello, I have some questions about this dll as I previously had some issues with it and I saw on forum that I wasn’t the only one. Most of my problems were connected to Mac OS version of the game and as I have to prepare one again, my questions arise. When I am preparing a MacOS build, it looks like fmodstudioL.bundle is not included and I can’t find it in GAME.app/Contents/Plugins folder. When I select fmodstudioL.bundle in Unity inspector I can set it to include Standalone in Include Platforms and then I can select Any CPU as the CPU for Mac OS X. However after building, I can see FMOD: Selected binaries for platform StandaloneOSX: - Enabled Assets/Plugins/FMOD/lib/mac/fmodstudio.bundle - Disabled Assets/Plugins/FMOD/lib/mac/fmodstudioL.bundle in Console and also I can see that CPU for Mac OS X is switched to None. I remember that previously I had some DLLNotFoundException issues when I launched the game because fmodstudioL.bundle was not included in build and I somehow managed to fix it but I don’t remember how. So my questions are: 1. What is the actual purpose of that dll? 2. Should it be included in Mac OS builds? Or any builds at all? 3. Why was it disabled for platform StandaloneOSX as visible in console and why import settings were changed. 4. If it should be included in build, I guess I have to try to reinstall FMOD to fix this issue? (based on comments from different posts on this forum) I am using Unity 2020.3.43 and FMOD 2.01.11 ---
**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:** [January 15, 2023, 11:53pm UTC](https://qa.fmod.com/t/questions-about-fmodstudiol-dll/19728/2 "2023-01-15T23:53:47Z")
Hi, > [@TomaszRobot](#): > > What is the actual purpose of that dll? the `fmodstudioL.bundle` is a Release binary with logging enabled for development > [@TomaszRobot](#): > > Should it be included in Mac OS builds? Or any builds at all? It is for development builds to aid in debugging issues. > [@TomaszRobot](#): > > Why was it disabled for platform StandaloneOSX as visible in console and why import settings were changed. Whether or not the `Development Build` option is selected in the `Build` options ![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/b/b890a93c7c039d8f04531d53950280af9e64a97d.png) Will dictate if the `L.bundle` is included in the build, the import options are changed during runtime to make sure that all the appropriate libs are being used. > [@TomaszRobot](#): > > If it should be included in build, I guess I have to try to reinstall FMOD to fix this issue? (based on comments from different posts on this forum) Could I see a screenshot of your `Plugins -> FMOD -> platforms -> mac -> lib`, this is the location of the `.bundles` when the integration is installed, while looking at it from the `Package Manager` they might be in different locations. ![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/6/693b1ba9dc674f924205b375e5932b2f85aac606.png) When building for Mac OS are you using Version Control to work on that platform? ---
**Author:** ![TomaszRobot](https://avatars.discourse-cdn.com/v4/letter/t/41988e/32.png) [@TomaszRobot](https://qa.fmod.com/u/TomaszRobot)\ **Post date:** [January 17, 2023, 2:02pm UTC](https://qa.fmod.com/t/questions-about-fmodstudiol-dll/19728/3 "2023-01-17T14:02:55Z")
First of all, thank you very much for the time you took to precisely answer my questions, I really appreciate it. If I understand correctly, fmodstudioL.bundle is only for development builds and it is a correct behaviour that it is not included in Release builds that are not Development builds. So I guess I don’t have to do anything as the build I am preparing is not a development build, it is a release one. Just to answet your questions: The only folder in my Plugins/FMOD/platforms/mac/lib is src folder. All .bundle files are placed in Plugins/FMOD/lib/mac. I am using version control (Plastic SCM) and I often jump from branch to branch, but I prepare mac build manually, not from some automated builds system that use version control, ---
**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:** [January 18, 2023, 5:46am UTC](https://qa.fmod.com/t/questions-about-fmodstudiol-dll/19728/4 "2023-01-18T05:46:25Z")
> [@TomaszRobot](#): > > First of all, thank you very much for the time you took to precisely answer my questions, I really appreciate it. No worries! > [@TomaszRobot](#): > > If I understand correctly, fmodstudioL.bundle is only for development builds and it is a correct behaviour that it is not included in Release builds that are not Development builds. Yes, that is correct. > [@TomaszRobot](#): > > All .bundle files are placed in Plugins/FMOD/lib/mac. > I am using version control (Plastic SCM) and I often jump from branch to branch, but I prepare mac build manually, not from some automated builds system that use version control, Could I see your ignore file for your version control as that might be causing issues. When dealing with version control, reimporting the plugin can help. Though the location of your files is a bit strange.