0
0

I’ve got a project in Vsiual studio 2005 that we’d like to integrate the FMOD high level API into.

I’ve already managed to get the low level(fmodex_vc.lib) to link and work correctly with our engine. I can play sounds and don’t run into any issues.

I’ve brought the high level engine into our projects(fmod_event.lib) everything links and compiles correctly. When I try and call FMOD::EventSystem::Init(50, FMOD_INIT_NORMAL, NULL) I get an assert down in the CRT:

"R6034 An application has made an attempt to load the C runtime library incorrectly".

I traced down into the stack and it appears that the CRT is having a problem finding the manifest in the executable. We are currently working on licensing the source for FMOD and I assume building the DLL in 2005 should fix this since it will generate a manifest to tell it which CRT to use. In the meantime is there any known workaround with using Visual Studio 2005 and the Designer API?

  • You must to post comments
0
0

Found the issue that was causing it but not sure why it’s happening.

It turns out that msvcr80.dll is in the same directory as our executable. Because it’s in the directory when the dll is loaded the crt looks for a manifest in the dll. Normally the dll is loaded from the windows system directory and searching for the manifest is skipped. However since the dll is being loaded from a different directory it goes and looks for a manifest and fails.

I know our projects is accessing that dll as well so I’m not sure why it only occurs with FMod.

  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.