0
0

I am using the full DLL/Lib so I don’t have to manage plugin loading etc… but it seems like FMOD still tries and loads every DLL in my folder with my executable..

Is this a bug or is there a way to keep it from looking for additional files

  • You must to post comments
0
0

This post might fix what you’re seeing?
[url:plqfstay]http://www.fmod.org/forum/viewtopic.php?t=6061[/url:plqfstay]

  • You must to post comments
0
0

fmodex.dll simply will not try to load other fmod plugins, it is not possible because the code is ifdef’ed out.

if you use fmodexp.dll then yes, it will try to load the plugins, if you are talking about other dlls like winmm.dll msvcrt.dll etc it will do that as part of a dependency tree and is unavoidable.

  • You must to post comments
0
0

I’ve had the same issue:
http://52.88.2.202/forum/viewtopic.php?t=7501

So far, setting the plugin path to NULL seems to have stopped it from trying to load these DLLs. Maybe you need to look at the code a little closer Brett.

  • You must to post comments
0
0

Yep, both of those posts look right along with what I needed

  • You must to post comments
0
0

Sorry but this is incorrect. I have already looked at the code and it is possible you have a lib or dll mixup somewhere. There is no way the standard fmod dll loads plugins.

I’ve even put a breakpoint in the plugin loader in fmod’s source and it never hits. The code is definitely set up to #ifdef out the plugin loading if you use fmodex.dll and to load all plugins if you use fmodexp.dll.
This is the way it has always been, has never changed, and is the way it is behaving on all tests I am doing now.

  • You must to post comments
Showing 5 results
Your Answer

Please first to submit.