When building banks using the FMod Plugin places files in the Contents/FMOD/Desktop/ directory causing UEditor to crash. When removing the Banks from said directory the FMod folder is still not visible in the contents browser though plugin seems to be enable and loaded in the Project Preferences.
When you say building banks using the FMOD plugin, you do mean through the actual FMOD Studio correct?
Could you provide me with your system specifications?
Could you also possibly provide me with some reproducible steps to get the crash to occur in a new blank project?
These steps would include how you are creating your Banks within the Studio plugin, as well as how you are associated the directory within the project.
My specs are: win 7 64-bit, SP1, i5 CPU M480 @2.67GHz, 6.0GB RAM, ATI Mobility Radeon HD 5650
Yes, I have built some banks in the Fmod Studio.
I will write in a little more detail for other users.
Create a project, and launch FMOD Studio, in preferences>builds make sure that build destination is set to UE4 project folder>Content>FMOD. In Fmod go to preferences and in the output settings, set the audio to Stereo (or what you are working on), and in the UE4, you can check that by going into UE4>Edit>Project Preferences>Fmod and set it also to Stereo. After creating a folder with an audio event in Fmod, save project and press build.
In that instance Fmod creates .bank extensions in the UE4 project folder/Content/FMOD/Desktop
And then UE4 crashes, tried building and then opening the editor - still the same result. All destinations seem to be set correctly on both ends.
I may have good news for you! I had the same crash so I talked to the FMOD developers and they found the source of this bug.
It seems that the current version of FMOD Studio (1.05.13) has a bug which confuses the UE4 plugin of fmod and makes it crash UE4. They will fix it in the next FMOD Studio release in a couple of weeks. But if you don’t want to wait, you may as well use FMOD Studio 1.05.12 which works fine (Note: You just need to “downgrade” your FMOD Studio application, NOT the UE4 plugin).
Thank you for taking the time to look into this issue and update this post. We always appreciate users going out of their way to help others, and from the looks of this bug, we could have spent a good while attempting to find the source of the error on our end.
If anyone is experiencing this issue and manages to work around the crash using Dalon’s suggestion please let me know.