When build for UWP Plattform having Debugging and development build settings active FMOD initialization fails with error:
SystemNotInitializedException: [FMOD] Initialization failed : FMOD.Debug.Initialize : ERR_UNSUPPORTED
Build Command used:
BuildPipeline.BuildPlayer(Scenes, “Build/uwp”, BuildTarget.WSAPlayer, BuildOptions.CompressWithLz4HC | BuildOptions.Development | BuildOptions.AllowDebugging);
Searching for this issue using Google point me, that fmod.dll is used instead of fmodL.dll. I tried to fix this in the fmod.cs by adding an #elif for development build on line 38 like:
#elif (UNITY_STANDALONE_OSX || UNITY_STANDALONE_WIN)
public const string dll = “fmodstudio”;
public const string dll = “fmodL”;
public const string dll = “fmod”;
It seems that it then uses (in my perspective the correct) fmodL.dll. But init still failes with issue ERR_INVALID HANDLE during FMOD.system.setOutput.
Searching in fmod.cs it seems that UWP or WSAPlayer is not handled specificly.
Non Development builds are working!