0
0

I just upgraded to the latest developer release from an FMod version that was about a month old. Code that used to work for setting up our own file system does not appear to work anymore. None of our callbacks are getting called. In order, we do:

[code:jawasa3g]

        result = m_pEventSystem->getSystemObject( &m_pSystem );
        ASSERT_TRACE(   result == FMOD_OK,
                            "Error %d detected when aquiring audio system!\n",
                            result );

        if ( result == FMOD_OK )
        {
            result = m_pSystem->setFileSystem(   ESoundSystem::FmodFileOpenCallback,
                                                            ESoundSystem::FmodFileCloseCallback,
                                                            ESoundSystem::FmodFileReadCallback,
                                                            ESoundSystem::FmodFileSeekCallback,
                                                            2048 );
            ASSERT_TRACE(   result == FMOD_OK,
                                "Error %d detected when initializing audio file system!\n",
                                result );

            result = m_pEventSystem->init( 500, FMOD_INIT_NORMAL, 0 );
            ASSERT_TRACE(   result == FMOD_OK,
                                "Error %d detected when initializing audio system!\n",
                                result );

            u32 fmodVersion;
            result = m_pEventSystem->getVersion( &fmodVersion );
            ASSERT( result == FMOD_OK );

            // Set up FMOD to use feet
            result = m_pSystem->set3DSettings(1.0f, 3.28f, 1.0f);
        }

[/code:jawasa3g]

then as the level loads, we call:

[code:jawasa3g]

    FMOD::EventProject *pProject = NULL;
    FMOD_RESULT result = m_pEventSystem->load( "global.fev", NULL, &pProject );
    ASSERT_TRACE(   result == FMOD_OK,
                        "Error %d detected when loading the FMOD project!\n",
                        result );

[/code:jawasa3g]

The result is always error 22, which is a file not found. This is correct, since the file is not in the same directory as the exe, but in the root of our file system. Any ideas on what could be going on? The documentation still reads like it did, so I am not aware of any changes.

  • You must to post comments
0
0

v39 is just uploading now which should fix this problem

  • You must to post comments
0
0

Much appreciated Brett :).

  • You must to post comments
Showing 2 results
Your Answer

Please first to submit.