Alright, I have some more information now. Here’s what the console looks like when we start in the web.
I think I was mistaken about side modules not being able to include JS, this error is being produced by some of FMOD’s inline JS so it’s definitely able to execute it. Just to be sure as well, I tested that we can create AudioContexts from a side module by inlining some JS with the EM_ASMpreprocessor. I don’t think there should be any technical limitations from emscripten.
It sounds like what you mentioned with supplying windowis what’s mentioned in the docs here and I’ve added that snippet in. It’s called during the init of the gdextension before it loads FMOD. It doesn’t seem to have changed anything though. Is there something more I should do?
Maybe the JS function that adds FMOD_JS_MixerFastpathFunctionand FMOD_JS_MixerSlowpathFunctionto Module isn’t getting called? I don’t see them on the Module by the time this error throws when I inspect with the debugger.
This is FMOD 2.03.06 and I’m currently using emcc 4.0.21