Fmod studio

December 18, 2024, 2:58am 1 I’m compiling the FMOD GDextension plugin for Godot for web. While this plugin compiles fine for all other platforms, it fails when building for web.wasm-ld: error: ../fmod/api/studio/lib/upstream/w32/fmodstudioL_bindings.a(fmod_os_js_api.o): relocation R_WASM_MEMORY_ADDR_SLEB cannot be used against symbol `JSFMOD::gSystemMap`; recompile with -fPICwasm-ld: error: ../fmod/api/studio/lib/upstream/w32/fmodstudioL_bindings.a(fmod_os_js_api.o): relocation R_WASM_MEMORY_ADDR_SLEB cannot be used against symbol `JSFMOD::gSystemMap`; recompile with -fPICwasm-ld: error: ../fmod/api/studio/lib/upstream/w32/fmodstudioL_bindings.a(fmod_os_js_api.o): relocation R_WASM_MEMORY_ADDR_SLEB cannot be used against symbol `JSFMOD::gSystemMap`; recompile with -fPICwasm-ld: error: ../fmod/api/studio/lib/upstream/w32/fmodstudioL_bindings.a(fmod_os_js_api.o): relocation R_WASM_MEMORY_ADDR_SLEB cannot be used against symbol `.L.str.160`; recompile with -fPICwasm-ld: error: ../fmod/api/studio/lib/upstream/w32/fmodstudioL_bindings.a(fmod_os_js_api.o): relocation R_WASM_MEMORY_ADDR_SLEB cannot be used against symbol `.L.str.160`; recompile with -fPICwasm-ld: error: ../fmod/api/studio/lib/upstream/w32/fmodstudioL_bindings.a(fmod_os_js_api.o): relocation R_WASM_MEMORY_ADDR_SLEB cannot be used against symbol `.L.str.161`; recompile with -fPICwasm-ld: error: ../fmod/api/studio/lib/upstream/w32/fmodstudioL_bindings.a(fmod_os_js_api.o): relocation R_WASM_MEMORY_ADDR_SLEB cannot be used against symbol `.L.str.161`; recompile with -fPICwasm-ld: error: ../fmod/api/studio/lib/upstream/w32/fmodstudioL_bindings.a(fmod_os_js_api.o): relocation R_WASM_MEMORY_ADDR_SLEB cannot be used against symbol `.L.str.161`; recompile with -fPICwasm-ld: error: ../fmod/api/studio/lib/upstream/w32/fmodstudioL_bindings.a(fmod_os_js_api.o): relocation R_WASM_MEMORY_ADDR_SLEB cannot be used against symbol `.L.str.161`; recompile with -fPICwasm-ld: error: ../fmod/api/studio/lib/upstream/w32/fmodstudioL_bindings.a(fmod_os_js_api.o): relocation R_WASM_MEMORY_ADDR_SLEB cannot be used against symbol `JSFMOD::gSoundMap`; recompile with -fPICwasm-ld: error: ../fmod/api/studio/lib/upstream/w32/fmodstudioL_bindings.a(fmod_os_js_api.o): relocation R_WASM_MEMORY_ADDR_SLEB cannot be used against symbol `JSFMOD::gSoundMap`; recompile with -fPICwasm-ld: error: ../fmod/api/studio/lib/upstream/w32/fmodstudioL_bindings.a(fmod_os_js_api.o): relocation R_WASM_MEMORY_ADDR_SLEB cannot be used against symbol `JSFMOD::gSoundMap`; recompile with -fPICwasm-ld: error: ../fmod/api/studio/lib/upstream/w32/fmodstudioL_bindings.a(fmod_os_js_api.o): relocation R_WASM_MEMORY_ADDR_SLEB cannot be used against symbol `.L.str.160`; recompile with -fPICwasm-ld: error: ../fmod/api/studio/lib/upstream/w32/fmodstudioL_bindings.a(fmod_os_js_api.o): relocation R_WASM_MEMORY_ADDR_SLEB cannot be used against symbol `.L.str.160`; recompile with -fPICwasm-ld: error: ../fmod/api/studio/lib/upstream/w32/fmodstudioL_bindings.a(fmod_os_js_api.o): relocation R_WASM_MEMORY_ADDR_SLEB cannot be used against symbol `.L.str.161`; recompile with -fPICwasm-ld: error: ../fmod/api/studio/lib/upstream/w32/fmodstudioL_bindings.a(fmod_os_js_api.o): relocation R_WASM_MEMORY_ADDR_SLEB cannot be used against symbol `.L.str.161`; recompile with -fPICwasm-ld: error: ../fmod/api/studio/lib/upstream/w32/fmodstudioL_bindings.a(fmod_os_js_api.o): relocation R_WASM_MEMORY_ADDR_SLEB cannot be used against symbol `JSFMOD::gChannelMap`; recompile with -fPICwasm-ld: error: ../fmod/api/studio/lib/upstream/w32/fmodstudioL_bindings.a(fmod_os_js_api.o): relocation R_WASM_MEMORY_ADDR_SLEB cannot be used against symbol `JSFMOD::gChannelMap`; recompile with -fPICwasm-ld: error: ../fmod/api/studio/lib/upstream/w32/fmodstudioL_bindings.a(fmod_os_js_api.o): relocation R_WASM_MEMORY_ADDR_SLEB cannot be used against symbol `JSFMOD::gChannelMap`; recompile with -fPICwasm-ld: error: ../fmod/api/studio/lib/upstream/w32/fmodstudioL_bindings.a(fmod_os_js_api.o): relocation R_WASM_MEMORY_ADDR_SLEB cannot be used against symbol `.L.str.160`; recompile with -fPICwasm-ld: error: too many errors emitted, stopping now (use -error-limit=0 to see all errors)em++: error: 'D:/Users/pmdevita/Downloads/fmod-gdextension/emsdk/upstream/bin\wasm-ld.exe -o demo\addons\fmod\libs\web\libGodotFmod.web.template_debug.wasm32.wasm --whole-archive -s ../fmod/api/studio/lib/upstream/w32/fmodstudioL_bindings.a src\fmod_cache.o src\fmod_server.o src\fmod_string_names.o src\register_types.o src\callback\event_callbacks.o src\callback\file_callbacks.o src\core\fmod_file.o src\core\fmod_sound.o src\data\performance_data.o src\tools\fmod_editor_export_plugin.o src\tools\fmod_editor_plugin.o src\nodes\fmod_bank_loader.o src\nodes\fmod_event_emitter_2d.o src\nodes\fmod_event_emitter_3d.o src\nodes\fmod_listener_2d.o src\nodes\fmod_listener_3d.o src\resources\fmod_dsp_settings.o src\resources\fmod_settings.o src\resources\fmod_software_format_settings.o src\resources\fmod_sound_3d_settings.o src\studio\fmod_bank.o src\studio\fmod_bus.o src\studio\fmod_event.o src\studio\fmod_event_description.o src\studio\fmod_parameter_description.o src\studio\fmod_vca.o -LD:\Users\pmdevita\Downloads\fmod-gdextension\fmod\api\studio\lib\upstream\w32 -LD:\Users\pmdevita\Downloads\fmod-gdextension\emsdk\upstream\emscripten\cache\sysroot\lib\wasm32-emscripten\pic godot-cpp\bin\libgodot-cpp.web.template_debug.wasm32.nothreads.a --no-whole-archive --keep-section=target_features -mllvm -combiner-global-alias-analysis=false -mllvm -wasm-enable-sjlj -mllvm -disable-lsr -mllvm -exception-model=wasm --import-memory

Skip to content Navigation Menu GitHub Copilot Write better code with AI Security Find and fix vulnerabilities Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes Discussions Collaborate outside of code Code Search Find more, search less Explore Learning Pathways Events & Webinars Ebooks & Whitepapers Customer Stories Partners Executive Insights GitHub Sponsors Fund open source developers The ReadME Project GitHub community articles Enterprise platform AI-powered developer platform Pricing Provide feedback Saved searches Use saved searches to filter your results more quickly ;ref_cta:Sign up;ref_loc:header logged out"}"> Sign up Developers of FMOD Studio Overview Repositories Packages People Pinned Loading FMOD Studio integration with Unity. C# 189 40 FMOD Studio integration with Unreal. C++ 217 86 Repositories --> Type Select type All Public Sources Forks Archived Mirrors Templates Language Select language All C# C++ Sort Select order Last updated Name Stars Showing 4 of 4 repositories fmod/fmod-for-unity’s past year of commit activity C# 189 MIT 40 3 0 Updated Feb 11, 2025 fmod/fmod-for-unreal’s past year of commit activity C++ 217 MIT 86 1 6 Updated Feb 11, 2025 unity-html5-demo Public Demonstration of the correct way to load banks for HTML5 within Unity using the FMOD For Unity integration. fmod/unity-html5-demo’s past year of commit activity C# 11 MIT 2 0 0 Updated Oct 24, 2024 unity-feature-demo Public Demonstration of FMOD Studio features within Unity using the FMOD For Unity integration. fmod/unity-feature-demo’s past year of commit activity C# 5 MIT 4 0 0 Updated Oct 24, 2024 People This organization has no public members. You must be a member to see who’s a part of this organization. Most used topics Loading…

Hey there!I’m currently trying to test out the FMOD 2.0 integration in a blank Unity 2018.3.11f1 Switch project but am getting the following error:Plugin ‘libfmodstudio.so’ is used from several locations:Assets/Plugins/FMOD/lib/android/armeabi-v7a/libfmodstudio.so would be copied to /libfmodstudio.soAssets/Plugins/FMOD/lib/android/x86/libfmodstudio.so would be copied to /libfmodstudio.soPlugin ‘libfmod.so’ is used from several locations:Assets/Plugins/FMOD/lib/android/armeabi-v7a/libfmod.so would be copied to /libfmod.soAssets/Plugins/FMOD/lib/android/x86/libfmod.so would be copied to /libfmod.soPlease fix plugin settings and try again.Deleting the armeabi-v7a plugin folder allows me to make a successful build, but leads to the following issue when playing any FMOD event in the build:SystemNotInitializedException: [FMOD] Initialization failed : FMOD.Debug.Initialize : ERR_UNSUPPORTED : A command issued was not supported by this object. Possibly a plugin without certain callbacks specified. This issue was caused by a conflict in meta files and has been fixed for the next release.Are you able to provide more information on this error? Awesome, thanks for the info!Once I successfully get a Switch build to compile and deploy, the InitializedException error floods the EDEV kit debug log at runtime and none of the FMOD sounds play. I’ve tried making both a fresh Unity 2018.3.11 project (plus Switch plugins) and a fresh FMOD studio 2.0 project but neither seem to resolve the issue.I’m not sure if this might have something to do with how I’ve gotten around the first issue I mentioned? I’ve tried both deleting the whole unity Android plugin folder and just unchecking the Switch platform option for the conflicting plugins. I’ve also tried making both multiplatform and individual Switch builds from Studio with no luck.I haven’t gotten to try checking with Unity 2019.1 since I’d have to create a whole new SDK configuration, but I’m wondering if that might be a factor? It looks like this may be caused by the Integration linking to the non-logging (release) lib and the RuntimeManager calling Debug_Initialize in a development build.We currently use statically linked libs for Switch, so we cannot automatically change the libs used for it, this has to be done manually in the Unity editor. I will also get this step added to the docs as it doesn’t appear to be mentioned in there.